allow for loading wasm without unsafe wasm execution #1793
Reference in New Issue
Block a user
No description provided.
Delete Branch "cramt/wasm_unsafe_eval_fix"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
fixes #1767, by allowed you to not bundle the wasm as a base64 encoded string which is dynamically loaded at eval time
The latest updates on your projects. Learn more about Vercel for Git ↗︎
Could we avoid duplicating the bits here that are not different?
From what I learned in the other threads,
DYNAMIC_EXECUTION=0
might be making the bindings quite a bit slower, if we still end up using it anyways.Might be worth removing this argument from the base64 variant, or seeing what happens if we add
EMBIND_AOT
to both (might require bumping emsdk here1b7d2c8d48/javascript/just.config.cjs (L140)
)Thanks for digging into this issue!
I've been a little bit weary towards wanting many flavors. E.g. some folks have wanted CommonJS, others have wanted an ASM.js version, not to mention the sync compile vs async compile delineation we have right now. But it seems like this issue is pretty commonly hit, so this makes sense to me.
When we did have multiple flavors though, for sanity, we ran Jest tests against each of them. That would be great to add back here (some of it was in the before state for)
ef1d772447
I haven't thought about it closely, but I almost wonder if it might make sense to have different packages for these.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.