Hey guys, I'm very sorry for the issues. It appears that some people were inadvertently affected by the rollout of http://devcenter.heroku.com/articles/nodejs-versions
If you had "node" specified at any 0.6 release in your engines section and were not specifying npm, you would have gotten the default version of npm (1.0.94). This older npm is not compatible with Node.js 0.6 and you would have seen an issue like those mentioned here. The default npm for the Node.js buildpack has now been updated to 1.0.106 which is compatible with Node.js 0.6. All should be well now. Please try pushing again and file a support request if you still run into any problems. Thanks, David On Thu, Feb 23, 2012 at 7:34 PM, visnu pitiyanuvath <[email protected]>wrote: > I'm running into the same problem today. I've successfully deployed the > other day. with no changes to my package.json, new deploys are blocked by > this. > > -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/heroku/-/jwugbedhpPwJ. > > 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. > -- 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.
