Content of `MODULE.bazel` in the BCR

[bazelbuild]

Content of `MODULE.bazel` in the BCR

[meteorcloudy]

Dev dependencies are ignored during dependency resolution for all modules except for the root module. So there is no functional difference between those two approaches.

In addition, you can use --ignore_dev_dependency to disable dev dependencies of the root module, so that you can test the targets you want to expose to downstream will still work without fetching dev dependencies.

There is also --check_direct_dependencies flag which let you fail the dependency resolution when the resolved dependency is not what you declared in your MODULE.bazel file.

(Just realized I should probably name the first one as --ignore_dev_dependencies 😅)

[fmeum]

In that case I'll probably keep the dev dependencies at the end of my repo's MODULE.bazel and strip them from the copy I check in to the BCR. Thanks!