<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Syntax-Highlighting on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/syntax-highlighting/</link>
    <description>Recent content in Syntax-Highlighting on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 12 Aug 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/syntax-highlighting/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>highlight.js vs Prism vs Shiki in 2026: Which JavaScript Syntax Highlighter Should You Use?</title>
      <link>https://www.pistack.xyz/posts/2026-08-12-highlightjs-vs-prism-vs-shiki-syntax-highlighting-comparison/</link>
      <pubDate>Wed, 12 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-08-12-highlightjs-vs-prism-vs-shiki-syntax-highlighting-comparison/</guid>
      <description>&lt;p&gt;Your documentation site renders code blocks that look like 2012. The problem: syntax highlighting on the modern web is a fork in the road with three very different destinations. &lt;strong&gt;highlight.js (24,981 stars)&lt;/strong&gt; is the zero-config veteran that auto-detects 190+ languages and works with zero build setup. &lt;strong&gt;Prism (13,035 stars)&lt;/strong&gt; is the lightweight, plugin-extensible classic built for hand-rolled pages and static sites. &lt;strong&gt;Shiki (13,695 stars)&lt;/strong&gt; is the newcomer that reuses VS Code&amp;rsquo;s TextMate grammar engine to produce pixel-identical highlighting — but it renders on the server, async, and demands a modern build pipeline. Pick the wrong one and you either ship 400 kB of unused language grammars to every visitor, or you spend a weekend fighting a build integration that was never designed for your static site generator.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
