Matt Blair

Matt Blair

I read that you learn more from a poor example than from a correct one. I don't believe this but that means my site will be a success.

Move your Open Source work to Node 4

Move your Open Source work to Node 4

2-Minute Read

Now that Node 4 has been released, isn’t it time you upgraded your OS (Open Source) projects to use it?

Step 1 - package.json

If you’re not already using it, the engines field in your package.json allows you to specify what version of node you designed your package to run on. The engines field is not strict - you can’t force your consumers to use a preferred engine, but you can warn them if your package uses features that aren’t available in all version of node.

Most people won’t need to upgrade this to use Node 4, but it’s good to be aware of.


I use travis to build and test my open source projects. To get my OS work running on thew new version of node, I needed to update my .travis.yml files to specify the new version of node.

The first part was easy:

  - "4"

I pushed my travis change, and I was hoping for a big fat green build message. Not so fast. Errors.

Long story short - to compile native modules in Node 4, you need a C++ compiler. Luckily you can configure travis to use one.

Add the following to your .travis.yml files

  - CXX=g++-4.8
      - ubuntu-toolchain-r-test
      - g++-4.8

BOOM!!! Big green build. Hope this helps folks out there.

Recent Posts



This theme was developed for Hugo.