Add support for node version manager

[pricejn2]

This is a feature request to enhance the npm and node component of the CSS feature added with BOA 3.1.2. Some incompatibilities between npm packages and certain versions of node, deem it necessary to provide node version switching capabilities.

NVM https://github.com/creationix/nvm/blob/master/README.md probably makes the most sense to accomplish this, as is parallels the current RVM approach used for Ruby.

[omega8cc]

What are the incompatibilities are you referring to?

Are they serious enough to not introduce official NPM support, yet?

[pricejn2]

I ran into one when testing out zurb_foundation's npm package dependencies where I could only getting it working properly with an older version of node 0.10. This doesn't seem like anything that should prevent the introduction of NPM support with BOA, however.

[stero]

Same issue here.

After following the instructions from here...

https://github.com/omega8cc/boa/blob/master/docs/RVM.txt

and installing Gulp and Bower in my foundation subtheme-folder...

1. Install Gulp: 'npm install -g gulp'
2. Install Bower: 'npm install -g bower'

... i try "npm start" and become this output:

---

npm ERR! Linux 3.18.11-vs2.3.7.4-beng
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "start"
npm ERR! node v4.5.0
npm ERR! npm v2.15.9
npm ERR! code ELIFECYCLE
npm ERR! STARTER@1.0.0 start: gulp
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the STARTER@1.0.0 start script 'gulp'.
npm ERR! This is most likely a problem with the STARTER package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! gulp
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs STARTER
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!
npm ERR! npm owner ls STARTER
npm ERR! There is likely additional logging output above.

---

After some googeling it seems to be a problem with an to old version of node or npm?

[omega8cc]

If anyone is willing to work on this, patches are welcome!

[pricejn2]

This has been on my radar for a while. I'll try and give it attention and submit an initial patch.

[pricejn2]

@stero your problem seems more like #1130