Itty is an ecosystem of time-saving & code-cutting libraries that weigh every single byte, so your users don't feel them.
"Bytes matter."
- @kevinrwhitley
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! :)
@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...
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.
https://t.co/M4vzgKoDxu
@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
If #2, check out itty-chroma.
Under 500 bytes for easy colors, effects, backgrounds, full CSS support, etc.
https://t.co/iPjFijRsWi
Want to test it out? Open the console on https://t.co/HNInDVmoWs 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...
@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