Installation
Prérequis#
If you don't use the standalone script or @pnpm/exe to install pnpm, then you need to have Node.js (at least v22) to be installed on your system.
En utilisant un script autonome#
Vous pouvez installer pnpm même si vous n'avez pas installé Node.js, en utilisant les scripts suivants.
Sur Windows#
warning
Sometimes, Windows Defender may block our executable if you install pnpm this way.
Due to this issue, we currently recommend installing pnpm using npm on Windows.
En utilisant PowerShell:
$env:PNPM_VERSION="latest-11"; Invoke-WebRequest https://get.pnpm.io/install.ps1 -UseBasicParsing | Invoke-Expression
On Windows, Microsoft Defender can slow down installation of packages. You can add pnpm to Microsoft Defender's list of excluded folders in a PowerShell window with administrator rights by executing:
Add-MpPreference -ExclusionPath $(pnpm store path)
POSIX :#
Not supported on Intel macOS and arm64 musl Linux
The standalone script and @pnpm/exe do not run on Intel Macs (darwin-x64) or on arm64 musl Linux, such as Alpine on ARM. Install the pnpm package, which runs on your system Node.js, with npm install -g pnpm@latest-11 instead. On arm64 musl Linux you can also use pnpm 12, which has a native binary for it. See #11423 and #10443 for context.
curl -fsSL https://get.pnpm.io/install.sh | env PNPM_VERSION=latest-11 sh -
Si vous n'avez pas installé curl, vous pouvez utiliser wget:
wget -qO- https://get.pnpm.io/install.sh | env PNPM_VERSION=latest-11 sh -
Linux runtime requirements
The install script picks a glibc or musl build based on your system's libc. A separate musl build is provided for Alpine and other musl-based distros on x64. The glibc build requires glibc 2.27 or newer plus libatomic.so.1. Both are present on most full distros but may be missing from minimal container images. If you see error while loading shared libraries: libatomic.so.1, install it with your distro's package manager:
- Debian/Ubuntu:
apt-get install -y libatomic1 - Fedora/RHEL:
dnf install -y libatomic
astuce
You may use the pnpm runtime command then to install Node.js.
In a Docker container#
# bash
wget -qO- https://get.pnpm.io/install.sh | env PNPM_VERSION=latest-11 ENV="$HOME/.bashrc" SHELL="$(which bash)" bash -
# sh
wget -qO- https://get.pnpm.io/install.sh | env PNPM_VERSION=latest-11 ENV="$HOME/.shrc" SHELL="$(which sh)" sh -
# dash
wget -qO- https://get.pnpm.io/install.sh | env PNPM_VERSION=latest-11 ENV="$HOME/.dashrc" SHELL="$(which dash)" dash -
Installation d'une version spécifique#
Before running the install script, you may optionally set an env variable PNPM_VERSION to install a specific version of pnpm:
curl -fsSL https://get.pnpm.io/install.sh | env PNPM_VERSION=<version> sh -
En utilisant npm#
npx get-pnpm latest-11
astuce
Voulez-vous utiliser pnpm sur des serveurs de CI ? See: Continuous Integration.
Compatibility#
Here is a list of past pnpm versions with respective Node.js version support.
| Node.js | pnpm 8 | pnpm 9 | pnpm 10 | pnpm 11 |
|---|---|---|---|---|
| Node.js 14 | ❌ | ❌ | ❌ | ❌ |
| Node.js 16 | ✔️ | ❌ | ❌ | ❌ |
| Node.js 18 | ✔️ | ✔️ | ✔️ | ❌ |
| Node.js 20 | ✔️ | ✔️ | ✔️ | ❌ |
| Node.js 22 | ✔️ | ✔️ | ✔️ | ✔️ |
| Node.js 24 | ✔️ | ✔️ | ✔️ | ✔️ |
| Node.js 26 | ✔️ | ✔️ | ✔️ | ✔️ |
Résolution de problèmes#
Si pnpm ne fonctionne plus et que vous ne pouvez pas le réparer en le réinstallant, vous devrez peut-être le retirer manuellement du PATH.
Let's assume you have the following error when running pnpm install:
C:\src>pnpm install
internal/modules/cjs/loader.js:883
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 where.exe pnpm.*.
Vous obtiendrez l'emplacement de la commande pnpm :
$ 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).
Une fois terminé, réinstallez pnpm et cela devrait fonctionner comme prévu.
Updating pnpm#
To update to the newest pnpm 11, run the self-update command with the major:
pnpm self-update 11
A bare pnpm self-update follows npm's latest tag, which now points at pnpm
12. See Installing pnpm v12 if that
is what you want.
Désinstaller pnpm#
If you need to remove the pnpm CLI from your system and any files it has written to your disk, see Uninstalling pnpm.