nvm + execa = nvexeca.

Execa improves
child processes execution with a
promise interface, cross-platform support, local binaries, interleaved output,
and more.

nvexeca is a thin wrapper around Execa to run any file or command using any
Node.js version.

Unlike nvm exec
it:

- is run programmatically
- does not need a separate installation step for each Node version
- can run the major release's latest minor/patch version automatically
- does not require Bash
- is installed as a Node module
- works on Windows. No need to run as Administrator.

nvexeca 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.

Example

``js
import nvexeca from 'nvexeca'

const { childProcess, versionRange, version } = await nvexeca('8', 'node', [
'--version',
])
console.log(Node ${versionRange} (${version})) // Node 8 (8.16.2)
const { exitCode, stdout, stderr } = await childProcess
console.log(Exit code: ${exitCode}) // 0
console.log(stdout) // v8.16.2
`

Install

`bash
npm install nvexeca
`

node >=18.18.0 must be installed. However the command run by nvexeca can use
any Node version (providing it is compatible with it).

This package is an ES module and must be loaded using
an import or import() statement,
not require(). If TypeScript is used, it must be configured to
output ES modules,
not CommonJS.

To use this as a CLI instead, please check
nve.

Usage

nvexeca(versionRange, command, args?, options?)

Executes command ...args with a specific Node.js versionRange.

$3

#### versionRange

_Type_: string

This can be:

- any version range such as 12, 12.6.0
or <12
- latest: Latest available Node version
- lts: Latest LTS Node version
- global: Global Node version
- Using the home directory .nvmrc or
package.json (engines.node field)
- Some similar files
used by other Node.js version managers are also searched for
- If nothing is found, defaults to the current process's Node version
- local: Current directory's Node version
- Using the current directory or parent directories
.nvmrc,
package.json (engines.node field)
or
similar files
- Defaults to the global version
- a file path towards a .nvmrc,
package.json (engines.node field)
or
similar files

#### command

_Type_: string

File or command to execute. Both global and local binaries can be executed.

Must be compatible with the specific Node versionRange. For example npm is
only compatible with Node >=6.

#### args

_Type_: string[]?

Arguments to pass to the command.

$3

_Type_: object?

All Execa options are available. Please refer to Execa for the list of
possible options.

The
preferLocal option
is always true.

The following options are also available.

#### dry

_Type_: boolean\
_Default_: false

Do not execute the command. This can be used to cache the initial Node.js binary
download.

#### progress

_Type_: boolean\
_Default_: false

Whether to show a progress bar when the Node binary is downloading.

#### mirror

_Type_: string\
_Default_: https://nodejs.org/dist

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

_Type_: boolean\
_Default_: undefined

The list of available Node.js versions is cached for one hour by default. If the
fetch option is:

- true: the cache will not be used
- false: the cache will be used even if it's older than one hour

#### arch

_Type_: string\
_Default_: process.arch

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.

#### cwd

_Type_: string | URL\
_Default_: process.cwd()

Current working directory of the child process.

When using the local alias, this
also starts looking for a Node.js version file from this directory.

$3

_Type_: Promise