-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Module not found: Error: Can't resolve 'env' #1907
Comments
Thanks for the report! This typically means that there's an unresolved import, for example something like: extern {
fn foo();
} where the default import module is |
Ran across this today and it was indeed because I was using a dependency that doesn't support WASM. Is it easy to improve this error message? |
I too am using ureq and got this error, I couldn't understand it at all - is there anything that can be done for future people beyond hopefully googling the right thing to spot this issue thread? |
Joining @sf-cg. I have this issue as well, but I have no clue from which crate. I have a working Rust lib that I compiled into wasm and I want to call its API from some JS code. Without a more informative error, I have no idea which one of the dozen crates I have there causes the issue.. |
facing same issue. Any suggestions how I can come over it ? |
Started a discussion on this issue here |
Solved, thanks to @Liamolucko ! See discussion linked above ☝️ |
Summary
A clear and concise summary of your question.
Module not found: Error: Can't resolve 'env' in 'D:\project\rust\wasm-pack-template\pkg'
Additional Details
Provide any additional details here.
when i add it to lib.rs
cargo.toml add
ureq = { version = "0.11.2", features = ["json"] }
The text was updated successfully, but these errors were encountered: