emsdk can't be used with Bazel 9/10

[theoparis]

ERROR: Traceback (most recent call last):
        File "/home/theo/.cache/bazel/_bazel_theo/a51fe4523e7bd3b5d868cc54ce49e796/external/emsdk+/emscripten_toolchain/toolchain.bzl", line 1148, column 43, in <toplevel>
                emscripten_cc_toolchain_config_rule = rule(
Error in rule: at index 0 of provides, got element of type NoneType, want Provider
ERROR: /home/theo/src/skia/src/gpu/BUILD.bazel:56:16: While resolving toolchains for target //src/gpu:gpu (1c5f67e): invalid registered toolchain '//emscripten_toolchain:cc-toolchain-wasm-emscripten_linux': error loading package '@@emsdk+//emscripten_toolchain': at /home/theo/.cache/bazel/_bazel_theo/a51fe4523e7bd3b5d868cc54ce49e796/external/emsdk+/remote_emscripten_repository.bzl:4:6: initialization of module 'emscripten_toolchain/toolchain.bzl' failed
ERROR: Analysis of target '//src/gpu:gpu' failed; build aborted

Bazel 9.0 is supposed to be released later this month. It seems that this file needs to pull in CcToolchainConfigInfo via load now. This causes my WIP Bazel 9 skia PR to fail to run tests. I could make a PR if that would be helpful.

[sbc100]

Yes, please send a PR!

[sbc100]

CC @walkingeyerobot

[theoparis]

Hmm, this seems to be a prerequisite aspect-build/rules_js#2459

theo@gigatop:~/src/emsdk/bazel$ bazel build //hello-world:hello-world
WARNING: Build option --flag_alias has changed, discarding analysis cache (this can be expensive, see https://bazel.build/advanced/performance/iteration-speed).
ERROR: Traceback (most recent call last):
	File "/home/theo/.cache/bazel/_bazel_theo/34d3f6555b9dee151859c1f00cc2ad48/external/aspect_bazel_lib++toolchains+copy_directory_toolchains/defs.bzl", line 15, column 20, in <toplevel>
		resolved_toolchain = rule(
Error in rule: rule() got unexpected keyword argument 'incompatible_use_toolchain_transition'
ERROR: /home/theo/src/emsdk/bazel/hello-world/BUILD:4:10: While resolving toolchains for target //hello-world:hello-world (91e2498): invalid registered toolchain '@copy_directory_toolchains//:all': while parsing '@copy_directory_toolchains//:all': error loading package '@@aspect_bazel_lib++toolchains+copy_directory_toolchains//': initialization of module 'defs.bzl' failed
ERROR: Analysis of target '//hello-world:hello-world' failed; build aborted

[Vertexwahn]

Bazel 9.0.0 is out now.

bazel_dep(name = "aspect_rules_js", version = "1.42.0")
bazel_dep(name = "rules_nodejs", version = "6.3.2")

should be pumped to

bazel_dep(name = "aspect_rules_js", version = "2.9.2")
bazel_dep(name = "rules_nodejs", version = "6.7.3")

not sure what else need to be fixed to get it working with Bazel 9.0.0

[Vertexwahn]

Some other fixes that might be needed to support Bazel 9.0.0: #1649

[sbc100]

This seems to be effecting our CI now: https://app.circleci.com/pipelines/github/emscripten-core/emsdk/2791/workflows/d9df2bfd-19b1-46e2-a5a9-eb71c5a86cb4/jobs/19324?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-checks-link&utm_content=summary

Is there any way we can pin our CI to specific Bazel version of avoid these kinds of external breakages?