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
Labels
Comments
jniles
added a commit
to Third-Culture-Software/bhima
that referenced
this issue
May 24, 2024
Changes documentation, commands, and procedures to work with `npm` instead of `yarn`. This should simplify our installation procedures and remove an additional dependency that is no longer required. Closes IMA-WorldHealth#7194.
jniles
added a commit
to Third-Culture-Software/bhima
that referenced
this issue
May 24, 2024
Changes documentation, commands, and procedures to work with `npm` instead of `yarn`. This should simplify our installation procedures and remove an additional dependency that is no longer required. Closes IMA-WorldHealth#7194.
jniles
added a commit
to Third-Culture-Software/bhima
that referenced
this issue
May 24, 2024
Changes documentation, commands, and procedures to work with `npm` instead of `yarn`. This should simplify our installation procedures and remove an additional dependency that is no longer required. Closes IMA-WorldHealth#7194.
jniles
added a commit
to Third-Culture-Software/bhima
that referenced
this issue
May 24, 2024
Changes documentation, commands, and procedures to work with `npm` instead of `yarn`. This should simplify our installation procedures and remove an additional dependency that is no longer required. Closes IMA-WorldHealth#7194.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When BHIMA started, we needed lockfiles to give predictive deployments, and
yarn
had them beforenpm
. 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:
The text was updated successfully, but these errors were encountered: