Перейти до основного змісту
Версія: 9.x

Коди помилок

ERR_PNPM_UNEXPECTED_STORE​

Тека модулів присутня і повʼязана з іншою текою сховища.

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

ERR_PNPM_NO_MATCHING_VERSION_INSIDE_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.

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 the pnpm.peerDependencyRules.ignoreMissing and pnpm.peerDependencyRules.allowedVersions fields in package.json.

ERR_PNPM_OUTDATED_LOCKFILE​

Ця помилка виникає, коли встановлення не може бути виконано без внесення змін до файлу блокування. This might happen in a CI environment if someone has changed a package.json file in the repository without running pnpm install afterwards. Або хтось забув зафіксувати зміни у файлі блокування.

To fix this error, just run pnpm 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 run pnpm 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 field use-node-version defines a release channel different from version suffix.

Наприклад:

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

Щоб виправити цю помилку, видаліть префікс каналу випуску або виправте суфікс версії.

Note that it is not allowed to specify node versions like lts/Jod. Правильний синтаксис для стабільного випуску – строго X.Y.Z або випуск/X.Y.Z.

ERR_PNPM_INVALID_NODE_VERSION​

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

Below are the valid forms of use-node-version:

  • Стабільні випуски:
    • X.Y.Z (X, Y, Z are integers)
    • release/X.Y.Z (X, Y, Z are integers)
  • Випуск RC:
    • X.Y.Z-rc.W (X, Y, Z, W are integers)
    • rc/X.Y.Z-rc.W (X, Y, Z, W are integers)