No workerHelpers.worker.js generated & ReferenceError: Window is not defined

[laurelch]

Initially, I was receiving the following error

Failed to load module script: The server responded with a non-JavaScript MIME type of "text/html". Strict MIME type checking is enforced for module scripts per HTML spec.

from the .../pkg/snippets/wasm-bindgen-rayon-[hash]/src/workerHelpers.worker.js?worker_file&type=module in the browser.

After investigating, I realized there is no workerHelpers.worker.js generated in the /pkg/snippets/wasm-bindgen-rayon-[hash]/src/ of my project. It only contained workerHelpers.js.

I attempted to compile both the demo/ and test/ directories inside the wasm-bindgen-rayon workspace, and in those cases, the workerHelpers.worker.js file was generated successfully. However, when I tried to create a standalone project, the file was not generated, even when I just copied the test/ directory outside of the workspace (and updated its dependencies).

The command I was using is $ wasm-pack build --target web, and I did not encounter any errors.

Thank you so much for any guidance!

[Jonarod]

+1 Exactly in the same situation...

[Jonarod]

Got around the error by copy-pasting this file:

https://github.com/RReverser/wasm-bindgen-rayon/blob/main/src/workerHelpers.worker.js

But I am not able to get passed await initThreadPool(navigator.hardwareConcurrency); which never resolves...

[laurelch]

Yes, seems that copy-pasting the file helped (partially), but I'm still getting both the following errors in my own project

Uncaught (in promise) RangeError: Maximum call stack size exceeded

&

ReferenceError: Window is not defined

---

I was able to reproduce the same "ReferenceError: Window is not defined error" with demo when using Vite. This error was fixed by closing and reopening the tab for demo, but this error in my own project persisted even with closing and reopening.

---

I was able to avoid the "ReferenceError: Window is not defined" in my own project by closing the DevTools window and refreshing.

[aW4KeNiNG]

Same problem here

[TheFrozenFire]

rustwasm/wasm-bindgen#4233 (comment)

Revert to wasm-bindgen 0.2.93 to fix. The current latest version 0.2.95 has a regression which breaks link_to!, as used in

wasm-bindgen-rayon/src/lib.rs

Line 59 in 09ade9b

wasm_bindgen::link_to!(module = "/src/workerHelpers.worker.js");