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
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:
Removing yarn.lock and committing package-lock.json
Updating our documentation that refers to yarn.
Updating our tests to only install npm and not yarn.
Updating our installation + release process to use npm instead of yarn.
The text was updated successfully, but these errors were encountered:
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: