Node Executable Path

FDNG_INP_NODE_EXE_PATH

No

An absolute path to a Node executable or its parent directory. If not provided, Node.js must be on PATH. See installNodeJS to install Node.js.

If not provided node must be on PATH, or new node can be installed by providing the version in the input 'Nodejs Version'.

Nodejs Version

FDNG_INP_NODE_VERSION

No

Nodejs version. Installs node with the provided version. This input will be ignored if the input 'Node Executable Path' is also provided. @Since 7.0.0.3

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 7.0.0.3

.npmrc Configuration Content

FDNG_INP_NPMRC_CONFIGURATION_CONTENT

No

npm configurations entered as list of key = value parameters(e.g. loglevel=notice).All the configurations are written to .npmrc file in the internal directory to be used during execution. @Since 7.0.0.3

All default npmrc configurations are listed when the command “npm config list -l” is run. For more details, refer https://docs.npmjs.com/cli/v10/commands/npm-config