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 from yarn to npm #7194

Open
jniles opened this issue Aug 12, 2023 · 0 comments
Open

Switch from yarn to npm #7194

jniles opened this issue Aug 12, 2023 · 0 comments

Comments

@jniles
Copy link
Contributor

jniles commented Aug 12, 2023

When BHIMA started, we needed lockfiles to give predictive deployments, and yarn had them before npm. Now, npm has them and so much more! Additionally, yarn and npm have diverged in their handling of plug and play modules, and you need npm to install the latest yarn.

I don't see a need to yarn anymore. It adds additional complexity (one more thing to install and maintain) and provides little added value if any. I propose that we migrate from yarn to npm by:

  1. Removing yarn.lock and committing package-lock.json
  2. Updating our documentation that refers to yarn.
  3. Updating our tests to only install npm and not yarn.
  4. Updating our installation + release process to use npm instead of yarn.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant