Deno More on reddit.com

The node runtime is based off v8 which is Google's javascript engine that chrome uses. So it's not exactly the same as every browsers engine but close to it. More on reddit.com

If you want Nodejs native way of doing this, I suggest you look into building a V8 snapshot via https://nodejs.org/api/cli.html#--build-snapshot (Node.js v18), which could immensly speed up application startup, if the initial JIT is the bottleneck. With Nodejs v22, you can also bundle application with the snapshot into a single executable applications: https://nodejs.org/api/single-executable-applications.html Minor warning: snapshot is architecture and CPU dependant. If you create a snapshot on Apple silicon (e.g. ARM MacBook), and then run this on a different CPU (e.g. Graviton2/3 on AWS), snapshot might not be compatible. More on reddit.com

You dont even gave to do that. Many compilers can be compiled to wasm and run directly in the browser, including c++, rust, zig, c#, and typescript is already JavaScript.

Using in memory file systems and js interop wasm can read right virtual in memory files that you then put in index db.

You can build an interactive development environment with builds that runs entirely in the browser on the user's hardware with no backing server and nothing but a content delivery network or static file web server.

However, executing the code would require a server. For that I would design a desktop environment that uses podman containers or something that users can download and work with the environment. Id design that as an electron app so its always up to date when opened.

More on reddit.com