Oracle SaaS FSM Account

FDOVB_INP_SAAS_ACCOUNT_CODE

No

The Oracle SaaS FSM account with all the required properties like instance URL, Username, and Password.

Node Executable Path

FDOVB_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'given, node in path will be considered. @Since 6.5.0.16

Nodejs Version

FDOVB_INP_NODE_VERSION

No

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

NPM Install Arguments

FDOVB_INP_NPM_INSTALL_ARGUMENTS

No

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

.npmrc

FDOVB_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 https://docs.npmjs.com/cli/v10/commands/npm-configconfiguring-npm/npmrc