The Builder installs your project dependencies using the detected package manager.
Dependencies are installed with the exact versions found in the lockfile.
Here are the commands executed, depending on the detected package manager:
You cannot customize the above commands, but you can still customize the
installation of your dependencies. Indeed, you can use an
.npmrc file or
NPM_CONFIG_ prefixed env variables to customize your package manager behavior.
To ignore peer dependencies like in npm v3 to v6, you can either:
- set the
NPM_CONFIG_LEGACY_PEER_DEPSenv variable to
The Builder supports installing private packages. To do so, you need to create an access token:
npm token create --read-only
Then, store this token in your environment variable, say
Finally, add the following to a new or existing
The Builder supports native dependencies to an extent.
- Node builtin native dependencies are supported
- Node native addons (
.nodefiles) built using node-gyp and/or node-pre-gyp should also work out of the box
Some native addons won’t work out of the box with our Builder, e.g. when the code reads some file at runtime.
Here is a non-exhaustive list of native dependencies known to work with our Builder: