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
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
The text was updated successfully, but these errors were encountered:
graysonhicks
changed the title
Incorrent lockfile and Node version
Incorrect lockfile and Node version
Feb 2, 2023
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:Recommendation
.nvmrc
to 18The text was updated successfully, but these errors were encountered: