BUILD file not found in directory 'modfile' of external repository @org_golang_x_mod. about bazel-gazelle HOT 4 CLOSED

Gazelle brings in this repo via its gazelle_dependencies macro. Since you call gazelle_dependencies in your WORKSPACE file after you instantiate your own version of org_golang_x_mod, but without a load statement in between, Gazelle's definition wins and your definition is ignored.

Could you try moving the load statement for gazelle_dependencies further down?

The true fix for these problems is adopting Bzlmod.

from bazel-gazelle.

Turns out, I had to uncomment my use of @org_golang_x_mod to make everything work. Moving the declarations around did nothing, the two uses were simply conflicting.
(now I also need to figure out how to persuade gazelle not to reinsert the repo onrepo-update)

As for bzlmod, how do I effectively use it when there are only about 150 packages that have their bzlmod declared? What of all the other deps that haven't migrated yet?

from bazel-gazelle.

Sure, if a dep hasn't migrated yet, it would need to be added to the registry first. But is there any particular dep that you are missing? Based on a quick look at your repo, it looks like all the deps are there.

I will close this as the original issue has been resolved.

from bazel-gazelle.

Where I worry, is a dependency that wants to pull in an entire universe of other deps. It's not obvious to me how one can easily migrate to bazel modules. This is especially true for projects that already resort to magical dances to ensure that conflicting dependencies are resolved.

from bazel-gazelle.