Node Executable Path

FDNODE_INP_NODE_EXE_PATH

No

An absolute path to a Node executable or its parent directory. If not given, node in path will be considered.

Nodejs Version

FDNODE_INP_NODE_VERSION

No

Nodejs version. Installs node with the provided version. This input will be ignored if the input FDNODE_INP_NODE_EXE_PATH is also provided. @Since 7.0.0.3

Working Directory

FDNODE_INP_WORKING_DIRECTORY

No

The working directory where the node commands will be executed. This path can be absolute or relative. If relative the path will be relative to the temp directory. If not provided directory containing package.json will be used.

Node Commands

FDNODE_INP_NODE_COMMANDS

Yes

The script of commands to be executed with the specified installation of Node JS.

Artifacts to Save

FDNODE_INP_ARTIFACTS_TO_SAVE

No

This path will be relative to working directory. Use '.' notation to save the entire working directory. If no value is provided no artifacts will be saved. If produces artifacts is false, no artifacts will be created.

.npmrc

FDNODE_INP_NPMRC

No

npm configurations entered as list of key = value parameters (e.g. loglevel=notice), one key value pair per line. @Since 7.0.0.3

All default npmrc configurations are listed when the command “npm config list -l” is run.

Some examples are-

1.registry=https://registry.npmjs.org/ (Specifies the URL of the npm registry)

2.strict-ssl=false (Controls SSL certificate validation during HTTPS requests.)

3.proxy=http://your-proxy-url:port
https-proxy=http://your-https-proxy-url:port (Specifies the URL of the proxy server.)

4.loglevel=verbose (Sets the logging level for npm output (e.g., silent, error, warn, info, verbose, debug).)

5.production=true (Instructs npm to skip installation of devDependencies.)

For more details, refer npm-config | npm Docs

Also, when multiple .npmrc files are available, npm follows a specific hierarchy for merging these configurations. Such as Project-Specific > User-Specific >Global.

For more details, refer npmrc | npm Docs