Does this work for you? I got the same response when I asked for an updated node version. But when I try the custom buildpack I always get this messages on deploy:
-----> Heroku receiving push -----> Fetching custom buildpack... done -----> Node.js app detected ! Heroku push rejected, failed to compile Node.js app The app works fine when being deployed with the default 0.4.7 version and no custom buildpack. - matthias On Dec 3, 3:17 pm, ppcanodehuelva <[email protected]> wrote: > Finally, got this response from heroku team: > > We have some experimental functionality just released that will allow > you to use multipleNode.js versions in your code. To try it, do the > following: > > heroku config:add BUILDPACK_URL=http://github.com/heroku/heroku- > buildpack-nodejs.git#versions -a someapp > > Inside that app, add an "engines" section to your package.json: > > { > "name": "someapp", > "engines": { > "node": ">=0.4.7 <0.7.0", > "npm": ">=1.0.0" > > } > } > > - ppcano > > Specifyingnodeand npm are both optional. If you don't specify, > you'll get our current default. > On Dec 2, 5:46 pm, Daniel Huckstep <[email protected]> > wrote: > > > > > > > > > No doubt they will update the version ofnode, but without customization > > you can't use a "different" version than the default. Luckily, > > customization is pretty easy. > > > Pat Patterson has written up a good spiel on how to use buildpacks (kind of > > unofficial right now it seems) to run a > > newernodeversion:http://blog.superpat.com/2011/11/15/running-your-own-node-js-version-... > > > I've also done this with a custom buildpack, and I removed the bits about > > npm, since the latestnodecomes with npm bundled. > > > - Daniel -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
