nvmis for modifying individual shell sessions to use the version you want.
naveis for launching subshells with the version you want loaded. n is for switching a single system-wide version of node.
.nvmrcfile, which like
.ruby-version, contains the version-ish string X you'd normally couple with
nvm use Xor
nvm install X.
nvm installby itself will locate the
.nvmrcfile, as will simply sourcing
nvmupon opening a new shell.
.navercfile, but I'm not too familiar with its usage.
ndoesn't appear to support any such config, but as it's system-wide, it doesn't really make as much sense to do so.
.node-versionand attempts to provide automatic version switching by hooking into
nvmdecided that was too invasive a behavior to include.
Node.js version management: no subshells, no profile setup, no convoluted API, just simple.
Super easy but system wide.
List installed version
0.8.14 ο 0.8.17 0.9.6
Change the active version by selecting the line and hit space bar.
Install desired node version with
n <version> ex
Possible issue with
npm command will output this :
npm WARN lifecycle npm is using /home/<HOME_DIR>/n/bin/node but there is no node binary in the current PATH. Use the `--scripts-prepend-node-path` option to include the path for the node binary npm was executed with.
Fixed by adding a .npmrc file in the project root dir containing :
- DRY sur le config projet (eslint, code quality, etc ...)
- automatisation des conventions
- 12 factors
- unit / functionnal testing
- CI (circle & jenkins)
- health checking
- métriques métiers
- Synchronous vs Asynchronous
- Open a File
- Get File Information
- Writing a File
- Reading a File
- Closing a File
- Truncate a File
- Delete a File
- Create a Directory
- Read a Directory
- Remove a Directory