peko VS third-sun

I am working on a Crypto utility class for basic hashing and JWT signing with HMAC or RSA algorithms. https://github.com/sebringrose/peko/blob/crypto-update/utils/Crypto.ts

The README is a lot more descriptive with code samples and the general concepts of the library nicely illustrated: https://github.com/sebringrose/peko

I have a self made tool that covers lots of these features: peko.deno.dev

I’m actually working on a server framework in Deno called Peko! You can check it out here if you’re interested: https://peko.deno.dev

Regarding your static assets problem take a look at this code from /lib/handlers/static.ts

Regarding the build step, Peko doesn't (yet?) have a handler directly for this but I have implemented this kind of logic in the iiisun.art app here. The code is still a WIP but basically a loading screen is sent at first which triggers compilation assets, then the "/" is swapped to the index page and an event is sent to the client telling it to refresh. There might be a cool way to wrap this behaviour but part of the mantra of Peko has been to keep it lightweight and flexible so would need to find a good solution. If you have suggestions I'd love to hear them :)

Take a look at this for an example: https://github.com/sebringrose/third-sun/blob/main/routes.ts

I'm optimizing a site by progressively loading higher res images from a custom img element. The different resolutions are created at runtime by passing the source image data (Uint8Array) into a rust wasm image implementation. (using image crate)