TanStack Markdown + Highlight 1.0 🏝️
Ship only the syntax, languages, and features users need with balanced flexibility, power and speed. Small enough to ship to the client and 1 less reason for server components 🤷♂️
Enjoy!
tanstack.com/markdown
tanstack.com/highlight
Ship only the syntax, languages, and features users need with balanced flexibility, power and speed. Small enough to ship to the client and 1 less reason for server components 🤷♂️
Enjoy!
tanstack.com/markdown
tanstack.com/highlight
Oct 1, 2026 · 6:46 AM UTC
13
32
407
24,889
@tan_stack Congrats on Launch. Parse once, ship only the languages the page actually uses.
0
0
3
348
if you could rewrite history,
what would you do?
call off D-Day as Eisenhower?
push the button in the Cuban Missile Crisis?
WorldOS lets you actually do it.
every move has consequences.
play it free → worldos.cc
what would you do?
call off D-Day as Eisenhower?
push the button in the Cuban Missile Crisis?
WorldOS lets you actually do it.
every move has consequences.
play it free → worldos.cc
136
50
1,709
1,715,489
@tan_stack Markdownの構文を必要な分だけ載せられるの、かなり嬉しいです。クライアント側で使うときにサイズを気にせず選べるのは助かります。
0
0
1
142
@tan_stack Markdown plus Highlight 1.0 small enough for the client is the useful ship. One less reason to hide syntax coloring behind a server component.
0
0
1
37
@tan_stack Shipping only the languages a page uses matters most on docs sites with many code blocks, where a full grammar bundle quietly dominates the client JS.
0
0
1
195
@tan_stack how do you decide which languages to prioritize for user needs in this?
1
0
1
213
@tan_stack The size is the less interesting number. What's moving back to the client is everything that never needed a credential. Server-side keeps the parts that touch secrets, and that line, not bundle weight, is what decides what can ever be shipped to a browser.
0
0
0
2