v0.27.0
Better node 4+ support!
- Separate code paths for "merged" node
- Clearer error messages
- Sort
nvm ls-remoteoutput 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 prefixis set to something outsidenvm, thatnvm userefuses to work (#606)
Other Enhancements
- Allow
--silentoption tonvm useto be in any position - Print the
npmversion when usingnvm execornvm run. - Add support for
--silenttonvm runandnvm exec(#842)
Fixes
- Use
NVM_VERSIONinstead ofVERSIONwhen sourcing to be a bit less intrusive (#820) - When no
io.jsversions are installed, showN/A, notio.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
grepto avoiddnvm.shconflicts (#838)
Documentation
- Add
nvm helpdocumentation fornvm exec