Node Executable Path

FDNG_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

FDNG_INP_NODE_VERSION

No

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

Save Artifacts

FDNG_INP_SAVE_ARTIFACTS

Yes

If checked, artifacts will be saved to the Artifacts folder automatically. If you need to perform additional steps on the output, then set this to false and use a copyArtifacts step later in the workflow.

Set to true by default

Output Folder Directory

FDNG_INP_OUTPUT_FILE_LOCATION

No

Specify the output path relative to the project location. By default, the "dist" folder will be used. 

Production Build

FDNG_INP_PRODUCTION

Yes

Should the ng build command be appended with the "--prod" flag. Defaults to true. Leave this as true if this build will eventually be served in a production environment. 

Additional Options

FDNG_INP_ADDITIONAL_OPTIONS

No

Provide any additional arguments to the ng build command. For example --stats-json

NPM Install Arguments

FDNG_INP_NPM_INSTALL_ARGUMENTS

No

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

.npmrc

FDNG_INP_NPMRC

No

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

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