nve executes a single file or command. It does not change the node nor
npm global binaries. To run a specific Node.js version for an entire project
or shell session, please use nvm,
nvm-windows,
n or nvs
instead.
Hire me
Please
reach out
if you're looking for a Node.js API or CLI engineer (11 years of experience).
Most recently I have been Netlify Build's
and Netlify Plugins'
technical lead for 2.5 years. I am available for full-time remote positions.
Examples
# Same as `node` but with Node 12
$ nve 12 node
Welcome to Node.js v12.22.12.
Type ".help"for more information.
> .exit# Same as `node file.js` but with Node 8
$ nve 8 node file.js
# Any command can be used
$ nve 12 npm test# Execute a local binary
$ nve 8 ava
# Run a specific version
$ nve 8.10.0 npm test# Use a version range
$ nve "<8" npm test# Run the latest Node.js version
$ nve latest npm test# Run the latest LTS version
$ nve lts npm test# Run the Node version from `~/.nvmrc` or the current process version
$ nve global npm test# Run the current directory's Node.js version using its `.nvmrc` or `package.json` (`engines.node` field)
$ nve local npm test# Run the Node version using a file like `.nvmrc` or `package.json`
$ nve /path/to/.nvmrc npm test# Use a different mirror for the Node binaries
$ nve --mirror=https://npmmirror.com/mirrors/node 8 npm test# Do not use the cached list of available Node.js versions
$ nve --fetch 8 npm test# Always use the cached list of available Node.js versions even if it's more# than one hour old
$ nve --no-fetch 8 npm test# Use a different CPU architecture for the Node binaries
$ nve --arch=x32 8 npm test# Chaining commands
$ nve 8 npm run build && nve 8 npm test# Cache Node 8 download
$ nve 8 node --version
Examples (multiple versions)
# Run multiple versions
$ nve 12,10,8 npm test
⬢ Node 12.22.12
105 tests passed
Finished 'test' after 3.8 s
⬢ Node 10.24.1
105 tests passed
Finished 'test' after 4.2 s
⬢ Node 8.17.0
105 tests passed
Finished 'test' after 4.5 s
# Do not abort on the first version that fails
$ nve --continue 12,10,8 npm test# Run all versions in parallel
$ nve --parallel 12,10,8 npm test# Cache multiple Node downloads
$ nve 12,10,8 node --version
Examples (list versions)
# Prints latest Node.js version
$ nve latest
20.4.0
# Prints latest Node.js 8 version
$ nve 8
8.17.0
# Prints latest Node.js 12, 10 and 8 versions
$ nve 12,10,8
12.22.12
10.24.1
8.17.0
Base URL to retrieve Node binaries. Can be overridden (for example
https://npmmirror.com/mirrors/node).
The following environment variables can also be used: NODE_MIRROR,
NVM_NODEJS_ORG_MIRROR, N_NODE_MIRROR or NODIST_NODE_MIRROR.
--fetch
Alias: -f Type: boolean Default: undefined
The list of available Node.js versions is cached for one hour by default. With:
--fetch: the cache will not be used
--no-fetch: the cache will be used even if it's older than one hour
The default value is undefined (neither of the above). When no COMMAND is
specified (only printing the Node.js version), the default value is --fetch
instead.
Node.js binary's CPU architecture. This is useful for example when you're on x64
but would like to run Node.js x32.
All the values from
process.arch are
allowed except mips and mipsel.
Initial download
The first time nve is run with a new VERSION, the Node binary is downloaded
under the hood. This initially takes few seconds. However subsequent runs are
almost instantaneous.
COMMAND can be omitted in order to cache that initial download without
executing any commands.
Difference with nvm
nve is meant for one-off command execution. Examples include:
running tests with an older Node.js version
checking if an older Node.js version supports a specific syntax or feature
The npm package nve receives a total of 2,395 weekly downloads. As such, nve popularity was classified as popular.
We found that nve demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago.It has 1 open source maintainer collaborating on the project.
Last updated on 28 Oct 2023
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
UnitedHealth Group disclosed that the ransomware attack on Change Healthcare compromised protected health information for millions in the U.S., with estimated costs to the company expected to reach $1 billion.
At Node Congress, Socket CEO Feross Aboukhadijeh uncovers the darker aspects of open source, where applications that rely heavily on third-party dependencies can be exploited in supply chain attacks.