[jderochervlk]

What this tests

• Moves the landing-page example highlighting into the existing React Router loader.
• Uses Shiki with the JavaScript regex engine, the bundled JavaScript grammar, and the official ReScript TextMate grammar.
• Vendors the ReScript grammar from rescript-vscode at commit 76d30468cb05401c10dd1e9dcf5a2993f8fc7140.
• Keeps the existing <pre><code> structure while passing highlighted inner HTML into the component.
• Updates landing-page test fixtures to use the same highlighter.

Scope

This is deliberately a spike for the current SSR/prerender pipeline. The docs app does not have React Server Components enabled yet, so this PR does not establish RSC compatibility.

It also does not replace highlight.js across documentation pages. The homepage is a small test surface for evaluating the grammar, output, bundle boundary, and visual result.

Findings

• The production build prerenders Shiki token markup for both ReScript and JavaScript.
• Shiki, its theme, and the ReScript grammar are present in the server build and absent from client assets.
• The loader therefore avoids shipping the highlighter to the browser on this route.

Validation

• ReScript compiler: passed
• Production React Router build and full prerender: passed
• Direct ReScript grammar smoke test: passed
• Prerendered homepage markup assertions: passed
• Client bundle scan for Shiki/grammar code: passed
• Browser test suite: not run locally because the checkout had no Playwright Chromium binary and the browser download timed out
• Visual baselines: intentionally not updated in this draft

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	guide	1959ed9	Commit Preview URL Branch Preview URL	Sep 19 2026, 07:16 PM

[github-actions]

Docs preview

[fhammerschmidt]

Closing this exploratory draft. Homepage code highlighting now runs in the route loader through #1364, with the current Highlight.js implementation keeping that preparation out of the browser.

We are retaining that implementation and archiving this Shiki spike. The Shiki-specific findings remain recorded in this PR; a future highlighter replacement can build on them in a focused proposal against the current rendering pipeline.