Alex Eagle

Note, the example/tutorial also needs to be switched to bzlmod rather than WORKSPACE

Note for anyone else looking for this, here's a little macro to do it: ``` load("@aspect_bazel_lib//lib:copy_to_directory.bzl", "copy_to_directory") load("@aspect_bazel_lib//lib:directory_path.bzl", "make_directory_path") load("@aspect_bazel_lib//lib:write_source_files.bzl", "write_source_files") # buildifier: disable=function-docstring-args def write_go_generated_source_files(name, target, output_files): """Wrapper around...

@adam-azarchs in my testing, that is already working correctly. I suspect gazelle knows that file is an output of a rule its creating, so it doesn't try to treat it...

Ugh, the macro workaround I mentioned above is used here https://github.com/aspect-build/aspect-cli/blob/main/bazel/command_line/BUILD.bazel however that means that any bzlmod users downstream trying to depend on the Go package trip over https://github.com/bazelbuild/bazel/issues/19301 slack...

@Bencodes @ahumesky I've got an assignment from the Bazel team to upgrade the workspaces in this repo to use bzlmod, but I'm not sure if Android is ready for this...

I think it's just that js_run_devserver doesn't work on Windows. Filed https://github.com/aspect-build/rules_js/issues/1341

Sorry, I don't know the exact issue. We have so few Windows users that no one has asked for the fix. In particular I had a client who gave up...

Could you include some more context? Are you writing the prose part of the tutorial somewhere else?

Hey @Bencodes I'm just doing a maintenance pass over the repo, is that something you can help with? 🙇🏻

Which example(s) are you trying to build? Each top-level folder in this repo is an independent Bazel workspace so "repo does not build" doesn't make sense - it's not possible...