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#

En utilisant PowerShell:

Invoke-WebRequest https://get.pnpm.io/install.ps1 -UseBasicParsing | Invoke-Expression

On Windows, Microsoft Defender can significantly 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 :#

curl -fsSL https://get.pnpm.io/install.sh | sh -

Si vous n'avez pas installé curl, vous pouvez utiliser wget:

wget -qO- https://get.pnpm.io/install.sh | sh -

In a Docker container#

# bash
wget -qO- https://get.pnpm.io/install.sh | ENV="$HOME/.bashrc" SHELL="$(which bash)" bash -
# sh
wget -qO- https://get.pnpm.io/install.sh | ENV="$HOME/.shrc" SHELL="$(which sh)" sh -
# dash
wget -qO- https://get.pnpm.io/install.sh | ENV="$HOME/.dashrc" SHELL="$(which dash)" dash -

Installation d'une version spécifique#

Avant d'exécuter le script d'installation, vous pouvez éventuellement définir une variable d'environnement PNPM_VERSION pour installer une version spécifique de pnpm :

curl -fsSL https://get.pnpm.io/install.sh | env PNPM_VERSION=<version> sh -

Using other package managers#

En utilisant npm#

npx get-pnpm

En utilisant Homebrew#

If you have the package manager installed, you can install pnpm using the following command:

brew install pnpm

En utilisant winget#

If you have winget installed, you can install pnpm using the following command:

winget install -e --id pnpm.pnpm

En utilisant Scoop#

If you have Scoop installed, you can install pnpm using the following command:

scoop install nodejs-lts pnpm

En utilisant Choco#

If you have Chocolatey installed, you can install pnpm using the following command:

choco install pnpm

Installing the pnpm 12 RC#

Apart from a short list of differences, pnpm 12 does not change the way you use pnpm 11, so the rest of this documentation applies to both versions — see What's different in pnpm 12. Only installation differs while v12 is a release candidate: it is published under the next-12 tag on npm and as a prerelease on GitHub, so Homebrew, winget, Scoop and Chocolatey don't offer it yet.

Using pnpm#

If you already have pnpm v11.10.0 or newer, this is the easiest way to switch:

pnpm self-update next-12

pnpm links the native binary directly, so nothing else is needed. Note that inside a project that pins pnpm through the packageManager field, self-update only updates that pin instead of installing pnpm globally.

En utilisant npm#

If you don't have pnpm installed yet:

npx get-pnpm next-12

Node.js 22.13 or newer is needed to run that install script, but not to run pnpm afterwards — pnpm 12 is a native binary.

En utilisant un script autonome#

Set PNPM_VERSION to next-12, or to an exact version.

On POSIX systems:

curl -fsSL https://get.pnpm.io/install.sh | env PNPM_VERSION=next-12 sh -

On Windows, using PowerShell:

$env:PNPM_VERSION="next-12"; Invoke-WebRequest https://get.pnpm.io/install.ps1 -UseBasicParsing | Invoke-Expression

This installs pnpm without requiring Node.js, and unlike pnpm 11 it also works on Intel macOS.

Compatibility#

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

pnpm 12 only needs Node.js when it is installed from npm; the version installed by the standalone script runs without Node.js.

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.

Supposons que vous obteniez l'erreur suivante lors de l'exécution de 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: []
}

Premièrement, essayez de trouver l'emplacement de pnpm en exécutant : 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

Maintenant que vous savez où se trouve l'interface de ligne de commande pnpm, ouvrez ce répertoire et supprimez tous les fichiers liés à pnpm (pnpm.cmd, pnpx.cmd, pnpm, etc). Une fois terminé, réinstallez pnpm et cela devrait fonctionner comme prévu.

Updating pnpm#

To update pnpm, run the self-update command:

pnpm self-update

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.