NodeJS 4.0

Node 4.0 has been released. This release is significant for a number of reasons, one of which is the merging of the NodeJS and the io.js projects in to one. The new Node (from version 4.0 and onward) will be based on the io.js repo. This should unify the Node project, which had seen some dissent in the ranks over the last year or so as some NodeJS contributors had moved over to the io.js project.

Of note, if you upgrade to v4.0 and run in to issues, you can always (and easily) roll back to prior versions.

For example, when I upgraded to v4.0, I got these errors when trying to run gulp:

    throw new Error(['`libsass` bindings not found in ', binaryPath, '. Try reinstalling `node-sass`?'].join(''));
Error: `libsass` bindings not found in ~/Sites/my-awesome-project/node_modules/gulp-sass/node_modules/node-sass/vendor/darwin-x64-46/binding.node. Try reinstalling `node-sass`?
    at Object.sass.getBinaryPath (~/Sites/my-awesome-project/node_modules/gulp-sass/node_modules/node-sass/lib/extensions.js:148:11)
    at Object.<anonymous> (~/Sites/my-awesome-project/node_modules/gulp-sass/node_modules/node-sass/lib/index.js:16:36)
    at Module._compile (module.js:434:26)
    at Object.Module._extensions..js (module.js:452:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at Object.<anonymous> (~/Sites/my-awesome-project/node_modules/gulp-sass/index.js:163:21)
    at Module._compile (module.js:434:26)

Attempting to upgrade node-sass and gulp-sass had no effect on fixing it.

So, I had to roll back to v 0.12.7, the last release before the 4.0 merge. Thankfully, once I exhausted every other attempt to fix the issue, rolling back was easy.

In case you didn’t know, you can upgrade/downgrade Node itself thru npm. Here’s how:

sudo npm cache clean -f
sudo npm install -g n
sudo n 0.12.7

“n” is a helper package that allows you to upgrade/downgrade your node instance.