I made a smol client-side syntax highlighter that uses the CSS Custom Highlights API called MicroLighter. I’ll talk about why I made it in a bit but first I wanted to… ahem… highlight… some of the features.
- Zero-dependencies
- ~2kb minifed+gzipped
- Uses CSS ::highlight(token-name) , not spans
- Leverages Textmate’s language grammars
- Human-readable light-dark() themes
- All languages/grammars…
This is part of my Building Fluentic Style series, where I’m writing down the design decisions, tradeoffs, and small surprises from building Fluentic Style . Atomic CSS gives you a nice primitive: one CSS property/value
one generated rule
one reusable class That is great for dedupe. If two places produce the same atomic rule, the final CSS can emit that rule once and reuse it wherever needed. But…
Elegant, scroll-driven edge masking. One class. Zero
JavaScript.
By one of the creators of
tw-shimmerCSS-only shimmer effects, with 475k+ weekly npm
downloads..
The Tailwind CSS4 debate is everywhere right now. And honestly? Most people are arguing about the wrong thing. The real question isn't "inline styles vs. utility classes" — it's about where your styling decisions live and who pays the cognitive cost. Let me break down what's actually happening, with real code, real trade-offs, and a clear take at the end. What Changed in Tailwind CSS v4 Tailwind …
