CLI fails with "import of `__wbg_location_*` doesn't have an adapter listed" on rust nightly-2026-08-07 (LLVM 23)
Author: emilbonnekCreated Aug 9, 2026Updated Aug 21, 2026
Since rust nightly-2026-08-07, running the wasm-bindgen CLI on our app's wasm fails with:
error: import of `__wbg_location_5d269cf0aa99107a` doesn't have an adapter listedThe same code builds fine on nightly-2026-07-27. The main difference between the two nightlies seems to be the LLVM upgrade (22.1.8 to 23.1.0), so my guess is that LLVM 23 emits code the descriptor interpreter can't follow.
What I've checked:
- Both wasm-bindgen 0.2.126 and 0.2.127 fail, each with a matching CLI, so it's not a version mismatch.
- The failing import is a plain
web_syslocationgetter. We don't usejs_namespaceor any unusual bindings. - Build profile:
wasm32-unknown-unknown, fat LTO,opt-level = "z",codegen-units = 1,panic = "abort". The app is a large Dioxus workspace app (about 450 crates), built with dioxus-cli 0.7.10. - A minimal hello-world Dioxus app does not trigger it, so it seems to depend on module size or a specific code pattern. I tried to shrink it down but haven't found the minimal trigger yet.
- Possibly related: on the same nightly, wasm-opt (binaryen 129) crashes with SIGABRT on "compile unit size was incorrect (this may be an unsupported version of DWARF)" even for the hello-world app.
I can share the failing pre-bindgen .wasm privately, run patched builds, or help bisect further. Happy to provide anything that's useful.
Source: wasm-bindgen/wasm-bindgen