pnpm install
Aliases: i
pnpm install
is used to install all dependencies for a project.
En ambiente CI, la installación falla si el lockfile existe pero necesita ser actualizado.
Inside a workspace, pnpm install
installs all dependencies in all the
projects. If you want to disable this behavior, set the recursive-install
setting to false
.
TL;DR
Comando | Significado |
---|---|
pnpm i --offline | Instala modo offline desde el almacenamiento interno |
pnpm i --frozen-lockfile | pnpm-lock.yaml is not updated |
pnpm i --lockfile-only | Only pnpm-lock.yaml is updated |
Opciones
--force
Fuerza la reinstalación de las dependencias: recupera los paquetes modificados en la tienda, recrea un lockfile y/o un directorio de módulos creado por una versión no compatible de pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch).
--offline
- Default: false
- Type: Boolean
If true
, pnpm will use only packages already available in the store.
Si un paquete no se encuentra localmente, la instalación fallará.
--prefer-offline
- Default: false
- Type: Boolean
If true
, staleness checks for cached data will be bypassed, but missing data
will be requested from the server. To force full offline mode, use --offline
.
--prod, -P
- Por defecto
- If
NODE_ENV
isproduction
:true
- If
NODE_ENV
is notproduction
:false
- If
- Type: Boolean
If set, pnpm will ignore NODE_ENV
and instead use this boolean value for
determining the environment.
If true
, pnpm will not install any package listed in devDependencies
and will remove
those insofar they were already installed.
If false
, pnpm will install all packages listed in devDependencies
and dependencies
.
--dev, -D
Only devDependencies
are installed and dependencies
are removed insofar they
were already installed, regardless of the NODE_ENV
.
--no-optional
optionalDependencies
are not installed.
--lockfile-only
- Default: false
- Type: Boolean
When used, only updates pnpm-lock.yaml
and package.json
. Nothing gets written to the node_modules
directory.
--fix-lockfile
Arregla las entradas lockfile roto automaticamente.
--frozen-lockfile
- Por defecto
- For non-CI: false
- For CI: true, if a lockfile is present
- Type: Boolean
If true
, pnpm doesn't generate a lockfile and fails to install if the lockfile
is out of sync with the manifest / an update is needed or no lockfile is
present.
This setting is true
by default in CI environments. El siguiente código se utiliza para detectar entornos de CI:
exports.isCI = !!(
env.CI || // Travis CI, CircleCI, Cirrus CI, GitLab CI, Appveyor, CodeShip, dsari
env.CONTINUOUS_INTEGRATION || // Travis CI, Cirrus CI
env.BUILD_NUMBER || // Jenkins, TeamCity
env.RUN_ID || // TaskCluster, dsari
exports.name ||
false
)
--merge-git-branch-lockfiles
Merge all git branch lockfiles. Read more about git branch lockfiles.
--reporter=<name>
- Por defecto
- For TTY stdout: default
- For non-TTY stdout: append-only
- Type: default, append-only, ndjson, silent
Allows you to choose the reporter that will log debug info to the terminal about the installation progress.
- silent - no output is logged to the console, not even fatal errors
- default - the default reporter when the stdout is TTY
- append-only - the output is always appended to the end. No se realizan manipulaciones del cursor
- ndjson - the most verbose reporter. Prints all logs in ndjson format
If you want to change what type of information is printed, use the loglevel setting.
--use-store-server
- Default: false
- Type: Boolean
Starts a store server in the background. The store server will keep running
after installation is done. To stop the store server, run pnpm server stop
--shamefully-hoist
- Default: false
- Type: Boolean
Creates a flat node_modules
structure, similar to that of npm
or yarn
.
WARNING: This is highly discouraged.
--ignore-scripts
- Default: false
- Type: Boolean
Do not execute any scripts defined in the project package.json
and its
dependencies.
--filter <package_selector>
Filter currently does not work properly with v8 default config, you have to implicitly set dedupe-peer-dependents to false
to have that work. For more info and progress please refer to #6300
--resolution-only
Re-runs resolution: useful for printing out peer dependency issues.