Oh nice to see this here! I’m the author of this little amalgamation, happy to answer any questions :-)<p>I just love small (for certain definitions of small) C libraries and got hooked to QuickJS the moment I tried it. After a few weekends of tinkering I had “quv” which was just QuickJS running on the libuv event loop. Later on I integrated curl and implemented xmlhttprequest on top of it. The last large change I made was to embed wasm3 as the WASM / WASI runtime.<p>I haven’t had the time to continue working on it for a while, seeing this here might be the encouragement I needed! :-)
Oh, goody. Last time I tried QuickJS it didn't have support for asynchronous generators and proxies.<p>Thank you, Mr. Bellard and whoever is working on this runtime. Your work is appreciated
Since it's presented as a "tiny" runtime, I'd like a size comparaison between this and Node in the readme. Same thing with the use cases (learning projects or "just for fun" are very valid use cases!).
For other small JS engines similar to QuickJS see Hermes: <a href="https://github.com/facebook/hermes" rel="nofollow">https://github.com/facebook/hermes</a>
So how does this compare to Espruino exactly -- which uses between 100K to 200K depending on which features you compile it with, has an excellent ecosystem, drivers for most hardware and acts alot like Node.