wasmedge-quickjs VS download-node-nightly-executable

I'm impressed you're already leveraging the component model. I thought it wasn't quite ready for primetime yet, but it seems you're proving that wrong... I'll have to dig in more here, as I'm working embedding WebAssembly in a high performance storage engine.

Thanks for the notes! I hear you on QuickJS - I've seen approaches of folks trying to build more node compatibility on top of quickjs (ala https://github.com/second-state/wasmedge-quickjs), but have recently heard about spidermonkey in wasmtime. Do you have intuition for nodejs vs browser in terms of what people want in terms of compatibility?

"A high-performance, secure, extensible, and OCI-complaint JavaScript runtime for WasmEdge. Run JavaScript in WebAssembly" wasm-edge-quickjs

See potential problems #1 for its proposed changes https://github.com/second-state/wasmedge-quickjs/pull/82#iss...

https://github.com/second-state/wasmedge-quickjs/pull/82#iss...

Try the bot on a PR you're interested in:

I can conceptualize a way to convert JavaScript source code to WASM then convert WASM to C source code. I have considered just using WASM, however, that introduces yet another runtime to manage https://github.com/second-state/wasmedge-quickjs.

Technically you can create a C shared object and import that shared object into QuickJS, see https://github.com/rsenn/qjs-modules, also https://github.com/second-state/wasmedge-quickjs.

That was achieved with QuickJS here https://bellard.org/jslinux/vm.html?url=alpine-x86.cfg, and here https://github.com/second-state/wasmedge-quickjs.

WasmEdge provides excellent support for JavaScript, including ES6 and NPM modules, async networking, the fetch API, React SSR, and even mixing Rust code with JS code. https://github.com/second-state/wasmedge-quickjs

npm never has to get written to or installed on your machine. download-node-nightly-executable.

WHat do you mean by "contribute"? I download only the node executable using download-node-nightly-executable to run native-messaging-nodejs, servers, or whatever else I decide to experiement on - without downloading any packages.

If you only need the node executable without npm, node_modules and the rest of the folders and files shipped in Node.js download archive you can use this https://github.com/guest271314/download-node-nightly-executable.

I use DecompressionStream() to decompress the Node.js nightly release before extracting only the node executable from the tar archive https://github.com/guest271314/download-node-nightly-executable/blob/main/index.html.

Yes. I create a file called node, touch node, set the file to executable chmod u+x node, then fetch the Node.js nightly release using this https://github.com/guest271314/download-node-nightly-executable, get rid of everything except the node executable, then run that node executable from the directory I download the file to. Then afterwards truncate the node execute to a file with 0 size, as it began as with

Node.js does not publish a release containing only the node executable. That is why I wrote this https://github.com/guest271314/download-node-nightly-executable to fetch the Node.js nightly download, extract only the node executable, and get rid of everything else in the download that never reaches my file system.

If you do not already have the node executable https://github.com/guest271314/download-node-nightly-executable.

Note: You can use node executable without using npm or npx at all download-node-nightly-executable. Create package.json including {"type":"module"} then you can import local .js files, e.g. https://github.com/guest271314/jsdom-extension/blob/main/background.js

As to that point, FWIW, it is easier to download the Deno executable than the Node.js executable, because Deno only includes the executable i the download - Node.js include npm, npx, et al. That is why I wrote https://github.com/guest271314/download-node-nightly-executable to extract only the node executable for Node.js nightly download.

FWIW I wrote this https://github.com/guest271314/download-node-nightly-executable to fetch the node nightly executable from the release folder than contains npm because I have no use for npm nor packages. I just use node executable as a Native Messaging host, which does not require any dependencies, just the javaScript runtime, where I can call process.spawn() and thus execute any local JavaScript file or other application written in any programming language.