ERR_PNPM_UNEXPECTED_STORE​

有一個已存在的模組目錄並且被連結到不同的儲藏庫目錄。

If you changed the store directory intentionally, runpnpm install and pnpm will reinstall the dependencies using the new store.

ERR_PNPM_NO_MATCHING_VERSION_INSIDE_WORKSPACE​

專案擁有工作區中不存在的工作區依賴套件。

For instance, packagefoo hasbar@1.0.0 in thedependencies:

{
"name":"foo",
"version":"1.0.0",
"dependencies":{
"bar":"workspace:1.0.0"
}
}

However, there is onlybar@2.0.0 in the workspace, sopnpm install will fail.

To fix this error, all dependencies that use theworkspace protocol should be updated to use versions of packages that are present in the workspace. This can be done either manually or using thepnpm -r update command.

ERR_PNPM_PEER_DEP_ISSUES​

pnpm install will fail if the project has unresolved peer dependencies or the peer dependencies are not matching the wanted ranges. 若要修正此問題，請安裝缺少的對等依賴套件。

You may also selectively ignore these errors using thepnpm.peerDependencyRules.ignoreMissing andpnpm.peerDependencyRules.allowedVersions fields inpackage.json.

ERR_PNPM_OUTDATED_LOCKFILE​

如果無法在不變更 lockfile 的情況下執行安裝，則會發生此錯誤。 This might happen in a CI environment if someone has changed apackage.json file in the repository without runningpnpm install afterwards. 或是有人忘記提交更改後的 lockfile。

To fix this error, just runpnpm install and commit the changes to the lockfile.

ERR_PNPM_TARBALL_INTEGRITY​

This error indicates that the downloaded package's tarball did not match the expected integrity checksum.

If you use the npm registry (registry.npmjs.org), then this probably means that the integrity in your lockfile is incorrect.This might happen if a lockfile had badly resolved merge conflicts.

If you use a registry that allows to override existing versions of a package, then it might mean that in your local metadata cache you have the integrity checksum of an older version of the package. In this case, you should runpnpm store prune. This command will remove your local metadata cache. Then you can retry the command that failed.

But also be careful and verify that the package is downloaded from the right URL. The URL should be printed in the error message.

ERR_PNPM_MISMATCHED_RELEASE_CHANNEL​

The config fielduse-node-version defines a release channel different from version suffix.

範例：

• rc/20.0.0 defines anrc channel but the version is that of a stable release.
• release/20.0.0-rc.0 defines arelease channel but the version is that of an RC release.

To fix this error, either remove the release channel prefix or correct the version suffix.

Note that it is not allowed to specify node versions likelts/Jod.The correct syntax for stable release is strictly X.Y.Z or release/X.Y.Z.

ERR_PNPM_INVALID_NODE_VERSION​

The value of config fielduse-node-version has an invalid syntax.

Below are the valid forms ofuse-node-version:

• Stable release:
  • X.Y.Z (X,Y,Z are integers)
  • release/X.Y.Z (X,Y,Z are integers)
• RC release:
  • X.Y.Z-rc.W (X,Y,Z,W are integers)
  • rc/X.Y.Z-rc.W (X,Y,Z,W are integers)