Skip to content

v0.27.0

Compare
Choose a tag to compare
@ljharb ljharb released this 26 Sep 17:21
· 1119 commits to master since this release

Better node 4+ support!

  • Separate code paths for "merged" node
  • Clearer error messages
  • Sort nvm ls-remote output so the order is: "pre-merged", "iojs", "post-merged".

Installing from source?

io.js and node v4.0+ still do not yet support installing from source. This isn't because it's hard to implement, it's because the tests for it time out on travis-ci. I don't want to add critical functionality without tests. I'm still trying to get this implemented and tested.

Release candidates?

io.js and node v4.0+ release candidate support is coming. It will not be enabled by default: you'll have to export an explicit environment variable to turn it on. However, this will allow node core developers, and module developers, to test upcoming releases easily on travis-ci and locally. Keep an eye out for it!

Having an npm prefix now errors out properly!

Essentially, the "prefix" option in npm breaks nvm, because global modules won't be stored within $NVM_DIR. nvm will now refuse to function if you have this set, eliminating much confusion!

  • Ensure that if npm config get prefix is set to something outside nvm, that nvm use refuses to work (#606)

Other Enhancements

  • Allow --silent option to nvm use to be in any position
  • Print the npm version when using nvm exec or nvm run.
  • Add support for --silent to nvm run and nvm exec (#842)

Fixes

  • Use NVM_VERSION instead of VERSION when sourcing to be a bit less intrusive (#820)
  • When no io.js versions are installed, show N/A, not io.js-, as the resolved default alias (#822)
  • Fix install script to not lie and claim to be auto-sourcing nvm.sh (#826, #827)
  • Use a tighter grep to avoid dnvm.sh conflicts (#838)

Documentation

  • Add nvm help documentation for nvm exec