Node.js 4.0.0 just got released! The jump from 0.12.x to 4.0 is a huge one, especially since it incorporates lots of changes that happened over at the IO.js project. So far, I haven’t experienced a lot of issues with it, and it quickly became the one version that I use as default on my system. However, there are some hickups here and there. Here I try to collect some issues with Gulp.js and first aid solutions. There are few and they might be out of date quickly.

Segmentation fault #

If you run your Gulp build, it might happen that you experience the following output:

Segementation fault

This one leaves you with no information, but the solution is rather straightforward: Re-install your Node.js dependencies:

$ rm -rf node_modules $ npm install

And you should be ready to go again. Frederic gives more help here:

@ddprrt Yes, all native modules require recompiling against latest V8 (best using [email protected]). — Frederic Hemberger (@fhemberger) 10. September 2015

libsass bindings not found #

If you use gulp-sass with the native C++ implementation of Sass, you might end up with the following error:

Error: `libsass` bindings not found in /[PROJECT DIRECTORY]/trunk/node_modules/gulp-sass/node_modules/node-sass/vendor/linux-x64-14/binding.node. Try reinstalling `node-sass`?

There are some dependency conflicts inside libsass , which we can resolve by moving to an earlier version of Sass.

$ npm uninstall gulp-sass node-sass $ npm install [email protected] $ npm install gulp-sass

Up until now, I haven’t found anymore issues. Will keep you posted if there are more