le_chuck

*Update*: Done. `kyu dev` is implemented and released :)

*Update:* I've got a draft PR for `kyu dev` with live reload.

I haven't benchmarked it yet but, guts feeling, would expect it to be (a bit?) slower. Cloudflare has likely spent quite some effort optimizing it and also runs fast machine. Kyushu uses QuickJS which adds a layer that needs to be loaded but, it's pre-initialization in memory which should mitigate the cost.

I did quite a market research to gather them ;)

Yeah I was surprised by this when I opened their website.

Your setup - Rust/WASM kernel + Service worker - sounds really sweet. If already public, please do share the link, else looking forward to your launch!

I had previous experience with QuickJS - respectively using the rquickjs crate (awesome project) - so my approach was first asserting whether it was possible to run a Wasmtime binary that both executes the JS code and handles HTTP requests and responses.

Then, the second part which was really important to me, was figuring out if I could find a way to embed the developer's JS code within the worker without requiring them to install Cargo. (thanks to Wizer it's possible, love it).

Once I had those two, the rest was basically execution (not saying it was straightforward though ;)

I was also a bit lucky: at the same time as I was developing it, Rolldown announced the version 1 of their standalone crate. So it was the perfect timing to use it as well.

As for StackBlitz WebContainers, I actually don't know much about it. They run in the browser as I understand, so fundamentally different but, feature wise I'm sure this project is way more mature and therefore offers way more features.

Thanks! It's actually the first time I started "designing" (I'm definitely not one) everything by picking the theme for the code snippets first. That's why the same colors are reused on the site and even in the logo.

Haha, glad someone noticed those testimonials ;)

Others mentioned better use cases than I could probably come with. Not sure it's a strong use case but, one thing I could maybe mention too is the fact that it ships as a standalone artifact. It's portable and, if reproducible, can provide some sort of guarantee on what's effectively running for those who care.

Thx! I thought about adding a context to the fetch handler, could be handy for local testing. Likewise, local commands (e.g. dev or watch mode) are not yet there. Those would be next on the line if the CLI starts getting used by others than me.