You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using pnpm with corepack, the pnpm version is taken from package,json, which is currently 7.17.0. This is causing an issue because the lockfileVersion is 6.0 and this lockfile version is supported only by pnpm 8+.
Steps to reproduce
$ docker run -it ubuntu bash
$ apt-get update && apt-get install -y curl git
$ curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.3/install.sh | bash && source ~/.bashrc && nvm install 18
$ corepack enable && corepack prepare pnpm@latest --activate
$ git clone https://github.com/solana-labs/solana-web3.js.git
$ cd solana-web3.js/
$ pnpm -v # 7.17.0 :(
$ pnpm install
Scope: all 10 workspace projects
WARN Ignoring broken lockfile at /solana-web3.js: Lockfile /solana-web3.js/pnpm-lock.yaml not compatible with current pnpm
Description of bug
I expected pnpm version to be 8+ (probably 8.5.0), but it was 7.17.0, and could not make use of the existing pnpm-lock.yaml .
The fix is to change the package.json from the root source folder. Change this:
"packageManager": "pnpm@7.17.0",
With this:
"packageManager": "pnpm@8.5.0",
Happy to raise a pull request for this if someone can agree on the proposed fix, thanks!
The text was updated successfully, but these errors were encountered:
Because there has been no activity on this issue for 7 days since it was closed, it has been automatically locked. Please open a new issue if it requires a follow up.
Overview
When using pnpm with corepack, the pnpm version is taken from
package,json
, which is currently7.17.0
. This is causing an issue because thelockfileVersion
is6.0
and this lockfile version is supported only by pnpm 8+.Steps to reproduce
Description of bug
I expected pnpm version to be 8+ (probably
8.5.0
), but it was7.17.0
, and could not make use of the existingpnpm-lock.yaml
.The fix is to change the
package.json
from the root source folder. Change this:With this:
Happy to raise a pull request for this if someone can agree on the proposed fix, thanks!
The text was updated successfully, but these errors were encountered: