Install a new Node.js version
Usage: fnm install [OPTIONS] [VERSION]
Arguments:
[VERSION] A version string. Can be a partial semver or a LTS version name by the format lts/NAME
Options:
--lts
Install latest LTS
--node-dist-mirror <NODE_DIST_MIRROR>
<https://nodejs.org/dist/> mirror [env: FNM_NODE_DIST_MIRROR] [default: https://nodejs.org/dist]
--fnm-dir <BASE_DIR>
The root directory of fnm installations [env: FNM_DIR]
--latest
Install latest version
--progress <PROGRESS>
Show an interactive progress bar for the download status [default: auto] [possible values: auto, never, always]
--log-level <LOG_LEVEL>
The log level of fnm commands [env: FNM_LOGLEVEL] [default: info] [possible values: quiet, error, info]
--arch <ARCH>
Override the architecture of the installed Node binary. Defaults to arch of fnm binary [env: FNM_ARCH]
--version-file-strategy <VERSION_FILE_STRATEGY>
A strategy for how to resolve the Node version. Used whenever `fnm use` or `fnm install` is called without a version, or when `--use-on-cd` is configured on evaluation [env: FNM_VERSION_FILE_STRATEGY] [default: local] [possible values: local, recursive]
--corepack-enabled
Enable corepack support for each new installation. This will make fnm call `corepack enable` on every Node.js installation. For more information about corepack see <https://nodejs.org/api/corepack.html> [env: FNM_COREPACK_ENABLED]
--resolve-engines [<RESOLVE_ENGINES>]
Resolve `engines.node` field in `package.json` whenever a `.node-version` or `.nvmrc` file is not present.
This feature is enabled by default. To disable it, provide `--resolve-engines=false`. [env: FNM_RESOLVE_ENGINES] [possible values: true, false]
-h, --help
Print help (see more with '--help')