DownloadNode.js version management: no subshells, no profile setup, no convoluted API, just simple. n is not supported natively on Windows. There are a variety of ways of specifying the target Node.js version for n commands. Most commands use the latest matching version, and n ls-remote lists multiple matching versions. n downloads a prebuilt Node.js package and installs to a single prefix (e.g. /usr/local). This overwrites the previous version. The bin folder in this location should be in your PATH (e.g. /usr/local/bin). The downloads are kept in a cache folder to be used for reinstalls. The downloads are also available for limited use using n which and n run and n exec. The global npm packages are not changed by the install, with the exception of npm itself which is part of the Node.js install.
Features
- Execute n on its own to view your downloaded versions, and install the selected version
- There are a variety of ways of specifying the target Node.js version for n commands
- There are three commands for working directly with your downloaded versions of Node.js, without reinstalling
- By default n picks the binaries matching your system architecture
- The n command downloads and installs to /usr/local by default
- You can be explicit to get the desired behaviour whatever the environment variable
Project Samples
