-
Notifications
You must be signed in to change notification settings - Fork 407
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
Migration from yarn-classic
to modern yarn
#1550
Comments
I begin to read some documentation about that and I understand that :
So maybe too soon to make that move ? 🤔 |
Looking at #1566, I came to the conclusion that probably the right way is to create standard SBOM (e.g. CycloneDX) And benefits to use yarn on small project like our demos doesn't maybe worth drawbacks : https://blog.logrocket.com/javascript-package-managers-compared/ So maybe we should consider to switch to npm instead of migrate to modern yarn ? |
I tested to migrate from yarn to npm in #1573. That sounds easy. |
There is now tooling for yarn to generate SBOM but only for modern yarn. (>v3 is required) : https://github.com/CycloneDX/cyclonedx-node-yarn |
This issue aim to track work on migration from
yarn-classic
tomodern yarn
This is part of #1492.
The text was updated successfully, but these errors were encountered: