quickjs-emscripten

One reason to use WASM to run JS, even in a browser, is to allow for interruptible execution of untrusted JS code. I built a library for this (1.2mb) that uses Emscripten to build QuickJS to WASM. I know of a company using my library to implement "plugin"/user-scripting using my library. https://github.com/justjake/quickjs-emscripten#quickjs-emscr...

Why not have a look at QuickJs. I assume your reason is to run js in the browser in an isolated environment for security reasons? I’ve found this article from figma to be an excellent starting point [0] Also useful to consider this benchmark [1] of js runtimes. We’ve found quickjs-emscripten [2] to work really well thus far. You can see my implementation of it here [3] in Lowdefy. If still has a few rough edges, so would be really keen to make it better. I’m interested to know, is spidermonkey more comparable to V8 than QuickJs? [0] - https://www.figma.com/blog/how-we-built-the-figma-plugin-sys... [1] - https://bellard.org/quickjs/bench.html [2] - https://github.com/justjake/quickjs-emscripten [3] - https://github.com/lowdefy/lowdefy/blob/main/packages/operat...

Fairly certain you don't want to be throwing `eval` in your code. I'm also building a workflow engine on the side, but don't want to see you run into security issues :) Look into the realms TC39 proposal, the SES TC39 proposal, or running (no joke) a lightweight ES6 environment in webassembly to eval your code. https://github.com/tc39/proposal-realms/#ecmascript-spec-pro... https://github.com/tc39/proposal-ses https://github.com/justjake/quickjs-emscripten