Closed harlan-zw closed 4 months ago
It is indeed strange as the current .mjs
file contains __wbg_getwithrefkey_4a92a5eca60879b9
(different suffix), and this suffix is the same as it was in 0.12.1
. Probably the file was re-generated during the release build or it has a different suffix in some glue code (indeed as suggested) which does not properly map to the actual function name. I'll check it in more detail, probably some issue during the build step
Posting an update here. The published WASM module has the following import:
(import "wbg" "__wbg_getwithrefkey_edc2c8960f0f1191" (func (;6;) (type 1)))
However, the published JS wrapper refers to:
imports.wbg.__wbg_getwithrefkey_4a92a5eca60879b9
I think the issue is this - the build process creates a wasm file and moves it from wasm/dist
to wasm
. The wasm
directory already has some JS wrapper, which may be outdated.
To fix this I'll update the build process, so the JS wrapper that is getting published is regenerated as well
Hey, had some time today to debug this a bit further. It seems like since 0.13.0 an error is thrown while trying to initialise the WASM.
Broken 0.13.1: https://stackblitz.com/edit/stackblitz-starters-qqx12u?file=package.json Working 0.12.1: https://stackblitz.com/edit/stackblitz-starters-fmque5?file=package.json
I don't know what the issue could mean but this is what GitHub Copilot said, if it helps: