-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error resolving module specifier “env” #218
Comments
The |
Thanks @zetanumbers for investigating and finding a fix! I've merged 24ab304 and am publishing patch releases of the affected crates. @MartinKavik can you give that a try? I'll close this for now but if this issue still isn't resolved please reply back and/or reopen the issue. |
I tried it with the new |
@MartinKavik no. The EDIT: my advice to you would be to not use atomics feature and try to replicate this issue on the current |
I've just tried it with the My idea was that |
Ah sorry I forgot. Use feature |
Hi,
a Seed app that indirectly depends on
topo
started to fail in runtime after some dependency updates.The error in the console log:
Uncaught TypeError: Error resolving module specifier “env”. Relative module specifiers must start with “./”, “../” or “/”.
After some hours of debugging I was able to track it to the
parking_lot
. This crate doesn't support Wasm on stable Rust and I wasn't able to compile it on nightly to prove that it works - see my effort in the parking_lot issue.It looks like it works with
parking_lot
<=0.10
, but the latest0.11.x
fails. Somecfg_ifs
forwasm32
have been introduced in the latestparking_lot
versions.I was also looking at
wasm-bindgen
and something like more explicit JS module handling has been introduced in recent versions according its changelog.So I guess that
wasm-bindgen
tries to link a required wasm module fromparking_lot
, but the module is "hidden" under some compilation flags inparking_lot
and linking silently fails with some mess in the initialization JS script. Then the script is invoked on the app start and immediately outputs that cryptic error to the console log and dies.The error is basically a show-stopper for most people - see the issue in wasm-bindgen.
Possible next steps:
Mutex
or use the one fromstd
if possible and fast enough.wasm-bindgen
or Rust compiler or another library - some help would be very welcome.Thank you very much!
Martin
The text was updated successfully, but these errors were encountered: