I’ll get back to you in a couple of days. I’m in Turkey and Discord is blocked here 🙄

Let’s talk. It might not be necessary :)

🍻

Obviously the main server can also act as middleware: intercepting/modifying the request before proxying it to the auxiliary and/or modifying the auxiliary's response before returning to the client.

So, there will be a main server in front of any number of auxiliary servers, each potentially running on a different runtime/cloud provider etc. Main will handle some routes itself while proxying others to the auxiliaries. We have a working POC even w/o then envs API. It will be much better with it.

There are a few for specific things like the multipart parser¹ but nothing comprehensive yet.

Last I checked, it was faster than Express as is and equaled Fastify when used with uWebSockets + whatwg-node/fetch.

¹ github.com/cyco130/mult... (might be outdated, haven't touched it in a while!)

- Pre-1.0 (even pre-0.1.0!).
- No website, no real docs.
- More geared towards being used as a backend for frameworks (Rakkas and to a lesser extent Vike) than standalone. It's perfectly usable standalone but our main focus hasn't been that yet.
- Hono filled the same niche pretty well.

All tuned in 👀

Nope! All you need is to put a DNS record or serve a special file from a certain URL on a domain you control: bsky.social/about/blog/4...

I’ve been asked the same question about the Rakkas logo (a stylized dancer, not unlike this emoji: 💃🏻) even though the first dictionary definition at the bottom of the landing page defines it as “(male) dancer” 🙃

rakkasjs.org

⭐️

Unrelated but this is the first time I’ve heard about the signal option of addEventListener. Cool!

Source code: github.com/cyco130/songs

This is awesome. So much to learn!

Turkish has a comeback for "welcome" which could be roughly translated as "welfound" :) So, welfound!