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

Switch "single package manager" from Yarn to pnpm #375

Closed
Josehower opened this issue Apr 11, 2023 · 0 comments · Fixed by #379
Closed

Switch "single package manager" from Yarn to pnpm #375

Josehower opened this issue Apr 11, 2023 · 0 comments · Fixed by #379
Assignees

Comments

@Josehower
Copy link
Contributor

Josehower commented Apr 11, 2023

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

@karlhorky karlhorky changed the title Update single package manager error Switch "single package manager" from Yarn to pnpm Apr 11, 2023
@Josehower Josehower changed the title Switch "single package manager" from Yarn to pnpm Switch preflight output from Yarn to pnpm Apr 11, 2023
@Josehower Josehower changed the title Switch preflight output from Yarn to pnpm Switch "single package manager" from Yarn to pnpm Apr 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants