You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On WSL Ubuntu, I'm trying to run this in Chrome 108.0.5359.125 (Official Build) (64-bit) (cohort: Stable).
Uncaught (in promise) DOMException: Failed to execute 'atob' on 'Window': The string to be decoded is not correctly encoded.
at decodeWasmBinary (http://localhost:3000/static/js/bundle.js:1598:18)
at http://localhost:3000/static/js/bundle.js:1591:16
I was getting the same error, so I dug into the issue and found out it was because the bundler I was using, bun, by default generates the wasm file in the final bundle and resolves it to its filename, however this package expects the file to be embedded into the code as a base64 string.
Unfortunately bun does not support such thing out of the box, but luckily it's pretty trivial to create a plugin that does that.
TL;DR, that error means this package couldn't load the wasm file, probably because it's not loaded the way it expects. Check your bundler's documentation on how to embed wasm files as base64 strings.
On WSL Ubuntu, I'm trying to run this in Chrome
108.0.5359.125 (Official Build) (64-bit) (cohort: Stable)
.My code is just the example code:
Some of the code in question is below:
requirements from package.json:
The text was updated successfully, but these errors were encountered: