[BUG]

[Lidne]

What happened?

I have an example repo which shows the problem - wasm file is not accessible from the main world. When I try to load it, js crashes with error

wasm_exec.20a6b632.js:1 Uncaught Error: Could not resolve bundle with id 8Qtd2
    at t.exports.resolve (wasm_exec.20a6b632.js:1:10441)
    at gJRBH.7a08970a1e434d7c (wasm_exec.20a6b632.js:1:9628)
    at h (wasm_exec.20a6b632.js:1:705)
    at m (wasm_exec.20a6b632.js:1:809)
    at ag3pB.raw:~/assets/wasm/main.wasm (wasm_exec.20a6b632.js:1:1392)
    at h (wasm_exec.20a6b632.js:1:705)
    at ag3pB.raw:~/assets/wasm/main.wasm (wasm_exec.20a6b632.js:1:1090)
    at wasm_exec.20a6b632.js:1:1253

This happens only in prod build, while dev version of an extension works with no issues.
Go compile:

• Windows:

$env:GOARCH="wasm"
$env:GOOS="js"
go build -o .\assets\wasm\main.wasm

• Linux:

GOOS=js GOARCH=wasm go build -o .\assets\wasm\main.wasm

I have no other options, rather than accessing wasm from the main world, so I appreciate any suggestions on how to fix this issue.

Version

Latest

What OS are you seeing the problem on?

Windows

What browsers are you seeing the problem on?

Chrome, Opera

Relevant log output

No response

(OPTIONAL) Contribution

• I would like to fix this BUG via a PR

Code of Conduct

• I agree to follow this project's Code of Conduct
• I checked the current issues for duplicate problems.