I move things forward and make things better

Menu

NodeJS

Today I just noticed that I’m still using the old version of Node, v0.10.36 to be precise. So, I head over to Node blog to see what is happening. It seems to be there is an update for the v0.10.x contained a fix for CVE-2015-0278. I can just update the Node installed on my laptop to v0.10.37 and at the same time I’m curious what if I move forward to Node v0.12.0. I don’t really get into the Node v0.12.0 stuff, so I decided to update it to those version. At this point I’m not quite sure what changes that brought to the Node v0.12.0. There is a few great a places to start digging what’s new in Node v0.12:

Over the last year, TJ Fontaine has become absolutely essential to the Node.js project. He’s been building releases, managing the test bots, fixing nasty bugs and making decisions for the project with constant focus on the needs of our users. He was responsible for an update to MDB to support running ::findjsobjects on Linux core dumps, and is working on a shim layer that will provide a stable C interface for Node binary addons. In partnership with Joyent and The Node Firm, he’s helped to create a path forward for scalable issue triaging. He’s become the primary point of contact keeping us all driving the project forward together.

Anyone who’s been close to the core project knows that he’s been effectively leading the project for a while now, so we’re making it official. Effective immediately, TJ Fontaine is the Node.js project lead. I will remain a Node core committer, and expect to continue to contribute to the project in that role. My primary focus, however, will be npm.

How to Enable it

I believe every developers needs to work productively when using npm by enable the tab-completion so that we can use the npm without too much typing to complete the commands we want to use . Here are the command I used to enable the npm completion on my Ubuntu box:

Credits

There’s been a lot of debates, theories, and requests about Node’s core API patterns on this list lately. I’d like to clarify the actual plans of the project on these points.

Callbacks will remain the de facto way to implement asynchrony. Generators and Promises are interesting and will remain a userland option.

…

…

There will be no changes to the module system. None. It’s finished. It’s been finished for over a year. Any proposed changes must come with a clear reproducible bug that cannot be worked around or addressed with documentation.

…

…

We are done making breaking changes at the Node.js layer. If your program runs today, we’re doing everything we can to make sure that it will run next year, albeit faster and more reliably.

This is not a democracy. However, there’s plenty of room for everyone’s opinion. If you want to make exciting dramatic breaking changes to node-core, and you can’t find satisfaction by writing userland npm modules, then please fork joyent/node, give it a new name and logo, and go as completely crazy as you want.

Today’s interesting questions is how can I bump the package version on package.json automatically without have to write my own script to do it. We can do it manually by editing the package.json or write a script to do it, but I wonder if npm having this built-in command.