Initialization error while using wasmer/bash

[Tirito6626]

Since sharrattj/bash throws runtime error while trying to call a function, I switched to wasmer/bash, as locally it worked fine, but on Konqueror (since I usually use Firefox and bash doesn't work there at all) it fails to initialize.

I'm not sure, whether it's browser or SDK issue, but it seems to fail on other browsers too (tested from other devices)

[TheNotary]

I take it you're defining a bash function in the shell and calling it and seeing that error? Please clarify if I'm mistaken.

In chrome, I don't see that error, but it does hang, failing to return after performing the work of the function.

[Tirito6626]

No, function declaration is sharrattj/bash related problem, which is most likely caused by it's code. Instead, when I'm trying to initialize wasmer/bash (await Wasmer.fromRegistry("wasmer/bash")), it fails

(this screenshot is taken from Firefox, latest version)

[TheNotary]

I see why I was confused now. So your reproduction steps are:

1. Modify index.ts to run wasmer/bash
2. Serve wasmer.sh locally with npm run dev or something
3. Navigate to the local server using Konqueror or firefox browser and you see the screenshotted errors

I'm not sure I can run Konqueror on my mac, but Chrome should work with this project. Probably Chromium will also work if you need something less brand heavy.

Firefox (144) doesn't work for me, but possibly for a different reason, a missing Access-Control-Allow-Headers: * header on the registry.wasmer.io server and/ or pulling images from the same domain as the web app.

You don't see these kinds of errors on the console on Firefox? What version are you on? Maybe the difference is our OSes.

Anyway, I've seen issues where cutting edge features stopped working in Firefox due to privacy issues where advertisers were using the same 'exploit' that legitimate engineers were using to enable desirable experiences for users. The Wasmer team doesn't seem to be spending much time maintaining wasmer-js. If Chrome is ultimately going to patch their browser and break this too, that would explain why the Wasmer team would shift their focus away from wasmer-js. It's a little speculative on my part, but I can't imagine any other reason wasm packaging for the browser wouldn't be one of their flagship pieces of infrastructure. It would be nice if someone from the team could chime in here, this packaging approach seems great for my use-case, but it's a little concerning that this repo doesn't build anymore and hasn't seen commits for 6 months.

[Tirito6626]

For Firefox I've used "CORS Everywhere" extension to bypass CORS restrictions. You can also reproduce the issue by just opening https://wasmer.sh/?package=wasmer/bash and look into the console

[TheNotary]

For Firefox I've used "CORS Everywhere" extension to bypass CORS restrictions

That is a huge relief, thanks for sharing that.

On Firefox, following https://wasmer.sh/?package=wasmer/bash , here's what I see in the console when the app attempts to load, which gives me more clues for some reason.

I guess that error is coming from within the bash wasm being loaded? If we go back 2 years in the wasmerio/wasmer repo, we can see some unwrap statements that for some reason work on Chrome, but on other browsers they crash.

There's a chance that simply doing a re-build of bash might fix the problem. I'm not sure if anyone on the wasmer team has actually compiled the bash wasm, I believe @john-sharratt did it for the sake of the adventure? I've been spending a bit of this morning poking around his repo to see if I can just build it for wasm, but I haven't had any luck yet. I'm still learning how wasi-sdk and clang work (I'm guessing that's how John built Bash 2 years ago) to compile wasm correctly and how to make sure the headers are placed in the expected location.

[Tirito6626]

You are actually right, I've tested the package on Firefox 128 and 140, while it works on 128, it throws same unwrap error on 140. Now it looks more like a SDK/browser issue, since neither of bash packages work, even wasmer/hello-world shows same error on a newer version.