-
-
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
Error resolving module specifier “env” #2570
Comments
Forgive me, I did a search of the issues beforehand but somehow didn't find #2215 . Looking there now... |
Some debugging notes:
|
It turns out that chrono = { version = "0.4", features = ["wasmbind"] } However, adding that actually reintroduces the env issue 😞 |
cc @MartinKavik , I will keep updating here with results of my experiments. |
Reproducing the bug: https://github.com/fosskers/env-bug-test My current hypothesis is that the source of the issue must be within the call tree of |
Two avenues of exploration in the call stack of let issued = chrono::Utc::now().timestamp(); as well as a call to let rng = ring::rand::SystemRandom::new();
|
For the record, using
|
EmbarkStudios/tame-oauth#37 solves my personal issue (it pulls out |
This is effecting me Pure Rust building with wasm-pack. |
This issue happens to be the highest result on google for |
Describe the Bug
I am working on a Seed application. Adding the following code...
... results in this line being added to the top of my
package.js
(the JS shim portion of the output ofwasm-pack
):Usually this line isn't present, nor have I seen it in any other WASM project of mine. When I try to run my WASM code in the usual way, the app fails entirely and I'm told this in my console:
Indeed there is no
env
folder or file around (if that's what thatimport
means), so I'm not sure what it's trying to do here.Forgive me if this is the wrong place to have reported this. I chose this repo due to the
wbg
in the import line.Steps to Reproduce
Unfortunately the rest of the code is closed-source, but I can at least say that I'm trying to test the
tame-oauth
crate. I'm not convinced that's the culprit though, as I have other code (in the same files) using that crate's functions and symbols without issue.Expected Behavior
The app loads as normal.
Actual Behavior
I see a blank screen and the console complains to me as shown above.
Additional Context
I'm on the latest versions of
wasm-bindgen
etc.See also:
The text was updated successfully, but these errors were encountered: