CompileError: WebAssembly.instantiate(): expected magic word 00 61 73 6d
See original GitHub issueHi!
Using argon2-browser
with webpack brings up the following error message.
Uncaught (in promise) RuntimeError: abort(CompileError: WebAssembly.instantiate(): expected magic word 00 61 73 6d, found 6d 6f 64 75 @+0). Build with -s ASSERTIONS=1 for more info.
at abort (http://localhost:3000/static/js/0.chunk.js:788:9)
at http://localhost:3000/static/js/0.chunk.js:870:7
I also get the following warning before:
failed to asynchronously prepare wasm: CompileError: WebAssembly.instantiate(): expected magic word 00 61 73 6d, found 6d 6f 64 75 @+0
I would appreciate any hints.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Expected magic word 00 61 73 6d, found 21 3c 61 72 ... - GitHub
This is because you are compiling a non-main package, and thereby creating an object file, not an actual binary. It is valid for...
Read more >CompileError: WebAssembly.compile() - Stack Overflow
wasm binary which starts with the magic 00 61 73 6d a.k.a. \0asm . According to the error message you get, your file...
Read more >expected magic word 00 61 73 6d - Telerik UI for Blazor
WASM Compile Error When Hosted - expected magic word and fail to execute compile. Read more in our Blazor Knowledge Base articles.
Read more >CompileError: AsyncCompile: Wasm decoding failed
CompileError : AsyncCompile: Wasm decoding failed: expected magic word 00 61 73 6d, found 21 3c 61 72 @+0. I'm expecting to see...
Read more >WebAssembly.instantiate() - MDN Web Docs
The WebAssembly.instantiate() function allows you to compile and instantiate WebAssembly code. This function has two overloads:
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Okay…so in my minimal TypeScript Webpack example it works. It must be related to the whole react build setup than.
Indeed, because my config works. You should probably investigate what’s going wrong. If you create a minimal example without dependencies, maybe I or someone else will help with that.