Saltar al contenido principal
Version: Próxima versión


Requisitos previos

Si no usa la secuencia de comandos independiente o @pnpm/exe para instalar pnpm, entonces necesita tener instalado Node.js (al menos v16.14) en su sistema.

Usando el script autónomo

Puede instalar pnpm incluso si no tiene instalado Node.js, utilizando los siguientes scripts.


Usando PowerShell:

iwr -useb | iex

Sistemas POSIX

curl -fsSL | sh -

Si no tiene curl instalado, puede usar wget:

wget -qO- | sh -

Puede usar pnpm env para instalar Node.js.

Usando Corepack

Desde la v16.13, Node.js está distribuyendo Corepack para administrar administradores de paquetes. Esta es una función experimental, por lo que debe habilitarla ejecutando:


Si has instalado Node.js con pnpm env Corepack no se instalará en tu sistema, tendrás que instalarlo por separado. Consultar #4029.

corepack enable pnpm

Si has instalado Node.js usando Homebrew, tendrás que instalar corepack por separado:

brew install corepack

This will automatically install pnpm on your system.

You can pin the version of pnpm used on your project using the following command:

corepack use pnpm@latest

This will add a "packageManager" field in your local package.json which will instruct Corepack to always use a specific version on that project. This can be useful if you want reproducability, as all developers who are using Corepack will use the same version as you. When a new version of pnpm is released, you can re-run the above command.

Usando pnpm

We provide two packages of pnpm CLI, pnpm and @pnpm/exe.

  • pnpm es una versión ordinaria de pnpm, que necesita Node.js para ejecutarse.
  • @pnpm/exe se empaqueta con Node.js en un ejecutable, por lo que se puede utilizar en un sistema sin Node.js instalado.
npm install -g pnpm


npm install -g @pnpm/exe

Do you wanna use pnpm on CI servers? See: Continuous Integration.


Here is a list of past pnpm versions with respective Node.js version support.

Node.jspnpm 7pnpm 8pnpm 9
Node.js 12
Node.js 14✔️
Node.js 16✔️✔️
Node.js 18✔️✔️✔️
Node.js 20✔️✔️✔️

Resolución de problemas

If pnpm is broken and you cannot fix it by reinstalling, you might need to remove it manually from the PATH.

Let's assume you have the following error when running pnpm install:

C:\src>pnpm install
throw err;

Error: Cannot find module 'C:\Users\Bence\AppData\Roaming\npm\pnpm-global\4\node_modules\pnpm\bin\pnpm.js'
←[90m at Function.Module._resolveFilename (internal/modules/cjs/loader.js:880:15)←[39m
←[90m at Function.Module._load (internal/modules/cjs/loader.js:725:27)←[39m
←[90m at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:72:12)←[39m
←[90m at internal/main/run_main_module.js:17:47←[39m {
code: ←[32m'MODULE_NOT_FOUND'←[39m,
requireStack: []

First, try to find the location of pnpm by running: which pnpm. If you're on Windows, run this command in Git Bash. You'll get the location of the pnpm command, for instance:

$ which pnpm
/c/Program Files/nodejs/pnpm

Now that you know where the pnpm CLI is, open that directory and remove any pnpm-related files (pnpm.cmd, pnpx.cmd, pnpm, etc). Once done, install pnpm again and it should work as expected.

Usando un alias más corto

pnpm might be hard to type, so you may use a shorter alias like pn instead.

Agregar un alias permanente en los sistemas POSIX

Just put the following line to your .bashrc, .zshrc, or

alias pn=pnpm

Agregar un alias permanente en Powershell (Windows):

In a Powershell window with admin rights, execute:

notepad $profile.AllUsersAllHosts

In the profile.ps1 file that opens, put:

set-alias -name pn -value pnpm

Save the file and close the window. You may need to close any open Powershell window in order for the alias to take effect.

Desinstalando pnpm

If you need to remove the pnpm CLI from your system and any files it has written to your disk, see Uninstalling pnpm.