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
It is up to the user to install packages into their node_modules directory, though the build tool can verify the contents.
...
In the nodejs rules, Bazel is not the package manager
My understanding is that this was true prior to the introduction of Bazel-managed dependencies, but with Bazel-managed dependencies, Bazel does manage node packages. To more accurately reflect the current status quo, this section should be updated to mention the (recommended) approach of using Bazel-managed dependencies with the workspace managed_directories attribute. Or perhaps the "Design" and "Hermeticity and reproducibility" sections should simply be deleted, since the same material is more accurately covered on the Dependencies page.
The text was updated successfully, but these errors were encountered:
Thanks for filing, that's good timing since we just launched a new docsite. I agree this content was the first thing I wrote four years ago and should just be deleted.
https://bazelbuild.github.io/rules_nodejs/ states:
My understanding is that this was true prior to the introduction of Bazel-managed dependencies, but with Bazel-managed dependencies, Bazel does manage node packages. To more accurately reflect the current status quo, this section should be updated to mention the (recommended) approach of using Bazel-managed dependencies with the workspace
managed_directories
attribute. Or perhaps the "Design" and "Hermeticity and reproducibility" sections should simply be deleted, since the same material is more accurately covered on the Dependencies page.The text was updated successfully, but these errors were encountered: