インストール
前提条件
If you don't use the standalone script or @pnpm/exe
to install pnpm, then you need to have Node.js (at least v16.14) to be installed on your system.
スタンドアロンスクリプトを使用する
Node.js がインストールされていない場合でも、次のスクリプトを使用して pnpm をインストールできます。
Windows の場合
PowerShell を使用:
iwr https://get.pnpm.io/install.ps1 -useb | iex
POSIX システムの場合
curl -fsSL https://get.pnpm.io/install.sh | sh -
curlがインストールされていない場合は、wgetを使用します。
wget -qO- https://get.pnpm.io/install.sh | sh -
You may use the pnpm env command then to install Node.js.
Corepack を使用する
Since v16.13, Node.js is shipping Corepack for managing package managers. これは実験的な機能であるため、次のコマンドを実行して有効にする必要があります。
If you have installed Node.js with pnpm env
Corepack won't be installed on your system, you will need to install it separately. See #4029.
corepack enable pnpm
Homebrew を使用して Node.js をインストールした場合は、Corepack を個別にインストールする必要があります。
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.
npm を使用する
We provide two packages of pnpm CLI, pnpm
and @pnpm/exe
.
pnpm
is a ordinary version of pnpm, which needs Node.js to run.@pnpm/exe
is packaged with Node.js into an executable, so it may be used on a system with no Node.js installed.
npm install -g pnpm
or
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.js | pnpm 7 | pnpm 8 | pnpm 9 |
---|---|---|---|
Node.js 12 | ❌ | ❌ | ❌ |
Node.js 14 | ✔️ | ❌ | ❌ |
Node.js 16 | ✔️ | ✔️ | ❌ |
Node.js 18 | ✔️ | ✔️ | ✔️ |
Node.js 20 | ✔️ | ✔️ | ✔️ |
トラブルシューティング
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
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 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.
短いエイリアスを使用する
pnpm
might be hard to type, so you may use a shorter alias like pn
instead.
POSIX システムでの永続的なエイリアスの追加
Just put the following line to your .bashrc
, .zshrc
, or config.fish
:
alias pn=pnpm
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.
pnpmをアンインストールする
If you need to remove the pnpm CLI from your system and any files it has written to your disk, see Uninstalling pnpm.