itty

TLDR; This is what your API can look like. ...in a single kilobyte, all-in.

Key goals: 1. Remove runtime/framework edge-case collisions. No more proxies. 2. No withParams. It'll be baked in. 3. Simpler CORS using AutoRouter. 4. Simpler nesting. 5. VERY few bytes gained to achieve all this.

itty-router v6.x discussion underway to solve existing v5.x DX issues. Want to help shape the direction? Join us on the @ittydev Discord ASAP (this will be a rapid consolidation of ideas before release).

@kinngh Awww thanks!! The how is by being obsessed with the lost art of code golfing while simultaneously really really caring about how the downstream code looks when actually used! :)

Idk how they do it but @ittydev has some of the tiniest and most powerful packages in the ecosystem

@wesbos Your own example shows one of the challenges of using this. 2nd to last example, breaks "I love pizza!" into 6 words, not 3. Then there's performance...

May or may not have been inspired by @Saadeghi and DaisyUI 🫡😁 @ittydev libs do powerful, simple things... for fewer bytes than you'd write yourself.

@dvailur @dok2001 Agreed on all.

@dok2001 Cloudflare is awesome. But they are terrible at marketing their products

I’ve never been more confident in Cloudflare than I am today

@Revenode @kevinrwhitley Will check out the cost of a bypass!

@kevinrwhitley @ittydev I have a ws server that sends and recieve uint8arrays

Normally @ittydev libs end up being situationally awesome/not, depending on your use-case. NGL though, itty-sockets is shaping up to be *the* (JSON) WebSocket client. It's *only* better, easier, more powerful, and for less size than anyone would write themselves.

@ridyeamnuim Was there a question in there?

@ittydev ok i don't need useless emojis-only response

@annualizooor @blockworks Who’s losing money right now?

@blockworks Follow this list and you too can learn how to lose money!

Blockworks staff list is public. Follow the full crew to never miss a beat in crypto. x.com/i/lists/133851…

And here's a demo of using the live snippets at itty.dev, including a realtime example of itty-sockets in use :)

You can do things like this in your browser logs with itty-chroma. Check out itty.dev (open the browser console to see/play):

FUN FACT: itty.dev includes several itty scripts in the console... with examples you can copy/paste right there to play:

After several years cooking, itty-fetcher v1.x just dropped last night. This lets you make SUPER clean API calls using native fetch - for 650 bytes. npmjs.com/package/itty-f…

@wotschofsky Essentially allowed a user-configurable base class… this version only works on the old non-RPC durable objects though. The @next/RPC version is much much cleaner

Very interesting pattern in itty-durable @ittydev to extend the result of a function 👀

Which do you want in your browser log messages?

If #2, check out itty-chroma. Under 500 bytes for easy colors, effects, backgrounds, full CSS support, etc. npmjs.com/package/itty-c… Want to test it out? Open the console on itty.dev and use it there: chroma.magenta.log('hello world')

@lukewj RIP... yeah if you ask most of the AIs for any info on itty-router, they don't even seem to grasp that it support middleware (all handlers can be middleware in itty). Or they'll try to generate express-style route handlers...

Just asked Gemini 2.5 Pro to refactor my Cloudflare routing and use itty-router. Total trainwreck!

@Basix1120 @pilcrowonpaper Also 🥰

I'm getting rid of all the framework-specific examples in Lucia and replacing it with a single example. So I just need a Typescript server that serves HTML with basic templating What library/framework/setup should I use?

@Basix1120 @pilcrowonpaper Disclaimer: * itty-router can certainly handle your route matching, and serve any form of response (including HTML, etc)... but you'd need to use something for the templating part