Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect lockfile and Node version #234

Open
graysonhicks opened this issue Feb 2, 2023 · 0 comments
Open

Incorrect lockfile and Node version #234

graysonhicks opened this issue Feb 2, 2023 · 0 comments

Comments

@graysonhicks
Copy link
Contributor

The lockfile is a V2 lockfile, but the Node version is 14, which generates and needs a V1 lockfile. The Node version should probably be bumped to 18. This will generate a V2 lockfile and be ready for Gatsby V5.

Without these changes installs fail without deleting the lockfile, doing nvm use, and regenerating. The error message is:

07:49:44 AM:
 ERR! msgpackr-extract-darwin-arm64 not accessible from msgpackr-extract

07:49:44 AM:
npm

07:49:44 AM:
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/gatsby/.npm/_logs/2023-02-02T15_49_44_211Z-debug.log

07:49:44 AM:
NPM ci --unsafe-perm --prefer-offline --no-audit --legacy-peer-deps failure - Command failed with exit code 1: npm ci --unsafe-perm --prefer-offline --no-audit --legacy-peer-deps --registry=https://registry.npmjs.org/
npm ERR! msgpackr-extract-darwin-arm64 not accessible from msgpackr-extract

Recommendation

  • Bump .nvmrc to 18
  • Regenerate lockfile
@graysonhicks graysonhicks changed the title Incorrent lockfile and Node version Incorrect lockfile and Node version Feb 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant