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
Since we have now switched from Yarn to pnpm, the error messages warning about package-lock.json in project should be updated:
✖ Use single package manager
› package-lock.json file committed to Git. Remove it with:
$ git rm --cached <filename>
After you've removed it, you can delete the file with: $ rm <filename> The presence of this file indicates that npm was incorrectly used in addition to Yarn (eg. an "npm install" command was run). In order to avoid issues with the state of the yarn.lock file, we suggest also forcing regeneration this file with the following command: $ yarn --force
This error messages should trigger when both package-lock.json and yarn.lock are found, and recommend pnpm commands to fix the problem
The text was updated successfully, but these errors were encountered:
Since we have now switched from Yarn to
pnpm
, the error messages warning aboutpackage-lock.json
in project should be updated:This error messages should trigger when both
package-lock.json
andyarn.lock
are found, and recommendpnpm
commands to fix the problemThe text was updated successfully, but these errors were encountered: