Why is yarn_install preferred over npm_install? #403
Labels
question/docs
Answer users question, preferably by updating docs
Comments
gregmagolan
added
the
question/docs
|
I believe the main reason is performance. The yarn_install rule will use the global yarn cache by default which makes subsequent yarn installs faster as they can fetch packages from the local cache. The option is |
|
Another reason is that yarn's lockfile semantics and correctness are a bit better than NPMs. |
|
Also this: #416 |
alexeagle
added a commit
to alexeagle/rules_nodejs
that referenced
this issue
Oct 17, 2020
- files that weren't staged after on-version.js - karma version from upstream (for local dev) - missing internal/BUILD file in the npm package Also Deprecate rules_typescript_dependencies it contains only rules_nodejs which users will have to install first anyway Closes bazelbuild#403 PiperOrigin-RevId: 232371626
alexeagle
added a commit
to alexeagle/rules_nodejs
that referenced
this issue
Oct 18, 2020
- files that weren't staged after on-version.js - karma version from upstream (for local dev) - missing internal/BUILD file in the npm package Also Deprecate rules_typescript_dependencies it contains only rules_nodejs which users will have to install first anyway Closes bazelbuild#403 PiperOrigin-RevId: 232371626
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi @gregmagolan and @alexeagle,
In the README.md#182 you wrote that
yarn_installis preferred overnpm_install. Why is that?We're migrating our repo to Bazel right now and we have some packages built with Yarn, and some with NPM. We want to just pick one, and we're currently siding with NPM, but we can choose Yarn instead if there are strong benefits on why Bazel prefers Yarn.
Thank you!
The text was updated successfully, but these errors were encountered: