you're right, it's a patch I forgot I applied to wasmtime 34.0.1 that is causing this :D
thank you, seems to be working after i fixed my issue, awesome to have wasmtime in the browser
zndvk has marked this topic as resolved.
Last updated: Jan 09 2026 at 13:15 UTC