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
Yarn provides better and faster caching on local machines.
Also I have some bad experience with package-lock.json. yarn.lock seems to handle dependencies in a bit more better way.
Also with yarn you can safe some keystrokes when using scripts. 🙂
Detailed Design
Add engines.yarn to package.json and set it to >= 1.22.4.
Also use yarn within GitHub Actions.
In addition we should commit yarn.lock to the repo so the build is more reproducible.
Documentation
Maybe we can add some script documentation into README.md (#19)
Drawbacks
Are there any?
Other contributers could not be used to yarn.
Alternatives
Stick to npm 🙁
Open Questions
Any questions.
Help Needed
No.
Frequently Asked Questions
Currently none
Related Discussions
Currently none
The text was updated successfully, but these errors were encountered:
Use yarn as default package manager
Summary
Let's use yarn as package manager instead of
npm
Motivation
Yarn provides better and faster caching on local machines.
Also I have some bad experience with
package-lock.json
.yarn.lock
seems to handle dependencies in a bit more better way.Also with
yarn
you can safe some keystrokes when using scripts. 🙂Detailed Design
Add
engines.yarn
topackage.json
and set it to>= 1.22.4
.Also use
yarn
within GitHub Actions.In addition we should commit
yarn.lock
to the repo so the build is more reproducible.Documentation
Maybe we can add some
script
documentation into README.md (#19)Drawbacks
Are there any?
Other contributers could not be used to
yarn
.Alternatives
Stick to
npm
🙁Open Questions
Any questions.
Help Needed
No.
Frequently Asked Questions
Currently none
Related Discussions
Currently none
The text was updated successfully, but these errors were encountered: