Langsung ke konten utama
Versi: Selanjutnya

Error Codes


A modules directory is present and is linked to a different store directory.

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


A project has a workspace dependency that does not exist in the workspace.

For instance, package foo has bar@1.0.0 in the dependencies:

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

However, there is only bar@2.0.0 in the workspace, so pnpm install will fail.

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


pnpm install will fail if the project has unresolved peer dependencies or the peer dependencies are not matching the wanted ranges. To fix this, install the missing peer dependencies.

You may also selectively ignore these errors using the pnpm.peerDependencyRules.ignoreMissing and pnpm.peerDependencyRules.allowedVersions fields in package.json.


This error happens when installation cannot be performed without changes to the lockfile. This might happen in a CI environment if someone has changed a package.json file in the repository without running pnpm install afterwards. Or someone forgot to commit the changes to the lockfile.

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