Skip to content
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

Open
jameshfisher opened this issue Feb 20, 2023 · 6 comments
Open

wasm-pack build hangs with no output for over 3 minutes #1231

jameshfisher opened this issue Feb 20, 2023 · 6 comments

Comments

@jameshfisher
Copy link

🐛 Bug description

I ran the following:

$ wasm-pack build

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:

$ wasm-pack build
[INFO]: 🎯  Checking for the Wasm target...
...

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

@LuminousPath
Copy link

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:
wasm-pack version: 0.11.1
rustc version: 1.60.0
windows

@drager
Copy link
Member

drager commented Jun 17, 2023

@Chronostasys
Copy link

facing same issue using v0.12.0 on macOS, with no output.

environment:
wasm-pack version: 0.12.0
rustc version: 1.69.0
macOS

@Chronostasys
Copy link

facing same issue using v0.12.0 on macOS, with no output.

environment: wasm-pack version: 0.12.0 rustc version: 1.69.0 macOS

Okey, I found that's probably a network issue. After downloading wasm32-unknown-unknown target the problem disappeared.

@ultraviolet-jordan
Copy link

I was just following this page here: https://developer.mozilla.org/en-US/docs/WebAssembly/Rust_to_Wasm

I just had wasm-pack build --target web hang on me for over 30 minutes.

I was under the impression this would take a long time because of this:
https://developer.mozilla.org/en-US/docs/WebAssembly/Rust_to_Wasm#building_the_package

I went searching and came here.
Went here and installed: https://rustwasm.github.io/wasm-pack/installer/
(I already had it installed though from the Mozilla doc I was reading)
Reinstalled it

Ran wasm-pack build --target web again and ran instantly.

OS: Windows
wasm-bindgen = "0.2.92"
rustc 1.79.0 (129f3b996 2024-06-10)

@nms-scribe
Copy link

nms-scribe commented Oct 22, 2024

I'm having this problem. I've verified that target wasm32-unknown-unknown is installed, and I tried using wasm-pack installer from the website, so the solutions in #1231 (comment) and #1231 (comment) didn't apply. I've tried disabling wasm-opt as described in #921. No amount of --verbose, or --log-level flags seem to cause it to generate any messages indicating that it's doing anything.

Arch Linux
wasm-pack 0.13.0
wasm-bindgen 0.2.95
rustup 1.27.1
rustc 1.81.0

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants