Node Executable Path

FDGRUNT_INP_NODE_EXE_PATH

No

An absolute path to a Node executable(grunt and grunt-cli package must be installed) or its parent directory. If not given, node in path will be considered.

Nodejs Version

FDGRUNT_INP_NODE_VERSION

No

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

NPM Install Arguments

FDGRUNT_INP_NPM_INSTALL_ARGUMENTS

No

Allows to enter one or more arguments to npm install command. (Ex --no-optional) @Since 7.0.0.3

Working Directory

FDGRUNT_INP_WORKING_DIRECTORY

No

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

Grunt File

FDGRUNT_INP_GRUNT_FILE

No

Absolute or relative path to Grunt file. Relative path will be considered inside working directory. If not provided this value will be defaulted to gruntfile.js.

Tasks

FDGRUNT_INP_TASKS

No

Comma separated list of grunt tasks to run. If not provided the default task will run. You can specify targets with Task:Target.

Additional Parameters

FDGRUNT_INP_ADDITIONAL_PARAMETERS

No

Additional arguments to pass to Grunt. For example, --force, --verbose, or --stack. The Grunt file parameter (--gruntfile) is not required as it is handled with Grunt File input. This input will be appended to the grunt command as it is entered.

Artifacts to Save

FDGRUNT_INP_ARTIFACTS_TO_SAVE

No

A relative path to a directory to save as an artifact. This path will be relative to the working directory. If not provided no artifacts will be saved. Use '.' notation to save the entire working directory.

.npmrc

FDGRUNT_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 https://docs.npmjs.com/cli/v10/configuring-npm/npmrc