News for hackers. Stuff that matters.
Re:Node v0.12.0 (Stable) by skeeterbug on Friday February 06, 2015 @11:38PM (#9013078)
I am just curious, what happens when people start writing ES6 io.js modules and posting them to NPM? Won't it be an issue for older versions of node? Is NPM going to start fragmenting because of this?
Re:Node v0.12.0 (Stable) by olalonde on Friday February 06, 2015 @11:52PM (#9013111)
The npm registry is already used for a bunch of stuff that it wasn't really intended for (e.g. front-end UI components, coffeescript, etc.). One solution for projects that need older versions of node would be to transpile es6 dependencies using https://github.com/esnext/es6-module-transpiler for example.
Re:Node v0.12.0 (Stable) by IsaacSchlueter on Sunday February 08, 2015 @01:45AM (#9016615)
Sure, but no worse (or even all that different) from any other Node release. The community will gradually upgrade, and it'll be fine.

You don't see many people using `node.http.cat()` any more, for example. And yet the community survived ;)