Any ideas how long it usually takes Heroku to add a new release of Node?
You can use any version at any time: https://devcenter.heroku.com/articles/nodejs-versions
Node.js v0.8.0 [stable] is out
31–40 of 60 posts
Re: Node.js v0.8.0 [stable] is out
#32Any ideas how long it usually takes Heroku to add a new release of Node?
You can use any version at any time: https://devcenter.heroku.com/articles/nodejs-versions
Not quite, I think? That page suggests that you can only use versions in this manifest: http://heroku-buildpack-nodejs.s3.amazonaws.com/manifest.nod...
...which doesn't list 0.8.
Re: Node.js v0.8.0 [stable] is out
#33The big difference is the switch from node-waf to node-gyp for native modules.
Re: Node.js v0.8.0 [stable] is out
#34:-D I actually set an alarm this afternoon to submit v0.8.0 as soon as it comes out, if you can possibly believe it ( I still can't believe I've done such a low, degenerate thing and am a little ashamed of myself )! But I'm incredibly happy about this release, specially about the 'new' cluster API[1] that has made my life a whole lot easier! So apologies for being a karma whore, but I was so glad I couldn't resist, i…
Anyone have a TLDR on what new functionality has been added to cluster? I skimmed the API and the changes didn't jump out.
Re: Node.js v0.8.0 [stable] is out
#35Congrats on the release! I'd love to take this opportunity to dive into Node, but I have yet to stumble accross an effective way of organizing medium to large Node projects. What tools do you guys/gals use?
One thing to note is that there is no standard library. Most of your code will be dealing with modules. The most important thing is to get those dependencies right. Node comes with node package manager (npm), which is a great tool for the job. Still, be aware that you might be dealing with a lot of moving parts. Any tool that helps you with this should be worth checking out.
You should also check out modules like step or async, to make your chained callbacks look nicer. This way you will avoid long code pyramids.
Use a tool such as JSHint or similar, to detect errors and potential problems in JavaScript code. Try to integrate it with your editor or your complete development environment.
Regarding editors or an IDE, well, you basically have a standard pick here.
Although there is one interesting and somewhat new player you might want to check out - Cloud9 IDE, an online development environment for js and Node (amongst others). Since the code is available on github you can also deploy it on your own machines if the hosted options don't suit you.
Re: Node.js v0.8.0 [stable] is out
#36:-D I actually set an alarm this afternoon to submit v0.8.0 as soon as it comes out, if you can possibly believe it ( I still can't believe I've done such a low, degenerate thing and am a little ashamed of myself )! But I'm incredibly happy about this release, specially about the 'new' cluster API[1] that has made my life a whole lot easier! So apologies for being a karma whore, but I was so glad I couldn't resist, i…
Anyone have a TLDR on what new functionality has been added to cluster? I skimmed the API and the changes didn't jump out.
Read the blog post. It has a TLDR
Re: Node.js v0.8.0 [stable] is out
#37:-D I actually set an alarm this afternoon to submit v0.8.0 as soon as it comes out, if you can possibly believe it ( I still can't believe I've done such a low, degenerate thing and am a little ashamed of myself )! But I'm incredibly happy about this release, specially about the 'new' cluster API[1] that has made my life a whole lot easier! So apologies for being a karma whore, but I was so glad I couldn't resist, i…
Anyone have a TLDR on what new functionality has been added to cluster? I skimmed the API and the changes didn't jump out.
If you mean changes between 0.7.15+ and 0.8.0, nothing really significant. But if you mean changes between 0.6.x and 0.8.0, well, almost everything has changed!
Sorry for the non-answer... But take a look at https://github.com/joyent/node/wiki/API-changes-between-v0.6... and https://groups.google.com/d/forum/nodejs-dev for change log (in 0.7 branch).
Re: Node.js v0.8.0 [stable] is out
#38Earlier quoted context omitted.
You can use any version at any time: https://devcenter.heroku.com/articles/nodejs-versions
Not quite, I think? That page suggests that you can only use versions in this manifest: http://heroku-buildpack-nodejs.s3.amazonaws.com/manifest.nod... ...which doesn't list 0.8.
The node.js buildpack has good instructions for how to upgrade it yourself if needed: https://github.com/heroku/heroku-buildpack-nodejs (and the buildpack docs are now public since Heroku's Cedar stack became the official default)
Re: Node.js v0.8.0 [stable] is out
#39Anyone noticed increased CPU usage?
Re: Node.js v0.8.0 [stable] is out
#40Earlier quoted context omitted.
Not quite, I think? That page suggests that you can only use versions in this manifest: http://heroku-buildpack-nodejs.s3.amazonaws.com/manifest.nod... ...which doesn't list 0.8.
The node.js buildpack has good instructions for how to upgrade it yourself if needed: https://github.com/heroku/heroku-buildpack-nodejs (and the buildpack docs are now public since Heroku's Cedar stack became the official default)
I meant when will they update it so that you can use the new version of Node without hacking the buildpack.
>To change the vendored binaries for Node.js, NPM, and SCons, use the helper scripts in the support/ subdirectory. You'll need an S3-enabled AWS account and a bucket to store your binaries in.
I don't want to mess with that, I'd rather wait for Heroku to update so I can change one line in my package.json.