-
Notifications
You must be signed in to change notification settings - Fork 409
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
wasm-pack build
hangs with no output for over 3 minutes
#1231
Comments
I'm also having this issue, but I don't even get as far as the initial [INFO], I'm getting no output whatsoever environment: |
Please try out v0.12.0 from one of the following ways: |
facing same issue using v0.12.0 on macOS, with no output. environment: |
Okey, I found that's probably a network issue. After downloading wasm32-unknown-unknown target the problem disappeared. |
I was just following this page here: https://developer.mozilla.org/en-US/docs/WebAssembly/Rust_to_Wasm I just had I was under the impression this would take a long time because of this: I went searching and came here. Ran OS: Windows |
I'm having this problem. I've verified that target Arch Linux Edit: It finally did output some information after many minutes, and did run successfully. After this first time, it starts up quickly on concurrent runs. |
🐛 Bug description
I ran the following:
It hung, and I left it for long enough to decide that it was a bug. I then ran it again and left it long enough to write out half of this bug report, before it miraculously eventually did something:
It took at least 3 minutes to print something.
🤔 Expected Behavior
It should tell me what it's doing, and give some indication that it's not stuck in an infinite loop. I imagine you're losing many first-timer users who just assume this tool is broken, Ctrl-C, and move on.
👟 Steps to reproduce
Follow the quickstart until step 5.
🌍 Your environment
Include the relevant details of your environment.
wasm-pack version: 0.10.3
rustc version: 1.67.1 (d5a82bbd2 2023-02-07)
macOS
The text was updated successfully, but these errors were encountered: