True, it's nice for streaming. But it can't reach inside a textarea, and it can't do bold or italic. Kirari's tokens already have offsets, though, so a small Highlight API adapter would be easy.

Kirari renders HTML on the server and at build time, where there's no DOM. The Highlight API needs JavaScript running in the browser, so code would show unstyled until it loads.

Good call. I will consider adding that!

Agreed. Future editors can stay minimal. Syntax highlighting for humans. Semantic tools and navigation for AI. Kirari already leans that way.

Cool, Sourceshot looks nice. Kirari should work pretty well for that. It’s DOM-free so the CLI side is straightforward, and it’s tiny. Which languages are you mostly using?

The whole library is smaller than my last commit message!

Mostly size and no WASM. Lightweight core with streaming and CSS themes.

Good idea! I’m already working on a comparison page covering Shiki and a few others.

Thanks mate! Built it specifically as a lightweight alternative to Shiki. Curious, which languages do you use most?

Kind of in between. Kirari saves checkpoints at line breaks where nothing is open (strings, comments or JSX). New chunks only rescan from the last checkpoint. If a chunk ends inside a string or comment, rescanning starts where it opened. This makes streaming much faster: 8 KB of TSX streamed character by character dropped from ~13s to 0.2s, with identical results to full tokenization. Currently supports JS, TS, JSX, TSX, JSON, JSONC and Python. Other languages still retokenize fully, but checkpoint support can be added if there's demand.

thanks mate!

Introducing Kirari ✨ A tiny, DOM-free syntax highlighter for the web. • 2.9 kB gzipped core • 48 languages • custom theme • Streaming support • Zero runtime dependencies Built to be lightweight and customizable. kirari.sh

Important clarification 👇 `satisfies` does NOT affect runtime behavior It: • Does NOT merge objects • Does NOT override values • Is purely a type-checking feature

✅ satisfies operator (TS 4.9+) ✔️ Enforces the shape ✔️ Preserves literal types ("#5a58f2") ✔️ Better autocomplete & inference

❌ Type annotation (: ThemeSchema) This narrows the object to ThemeSchema ➡️ hex becomes string ➡️ Literal types are lost ➡️ Worse inference

Been working on a Design System and ran into a great TypeScript nuance that’s easy to miss 👀 The difference between : ThemeSchema vs satisfies ThemeSchema 🧵⬇️