perf(homepage): prerender the highlighted code examples [Codex] - #1364
jderochervlk wants to merge 4 commits into
Conversation
jderochervlk
changed the title
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
guide | 149251f | Commit Preview URL Branch Preview URL |
Sep 20 2026, 02:45 PM |
Lighthouse baselineCompared with target branch
Download the full Lighthouse reports and baseline Commit |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f3a1b38964
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
f3a1b38 to
a2c8376
Compare
a2c8376 to
b59d3b1
Compare
b59d3b1 to
1751385
Compare
1751385 to
7a26dc4
Compare
|
Codex Review: Didn't find any major issues. Keep it up! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
c28fae8 to
7ab20d6
Compare
7ab20d6 to
f7936f1
Compare
f7936f1 to
edfe428
Compare
Generate highlighted markup and the compressed playground URL during prerendering with an isolated highlighter. Keep the hero presentational, preserve existing screenshots, verify hydration and navigation, and ratchet the initial JavaScript byte budget down.
Retain initial-script exclusions and exact prerender/hydration/navigation markup checks for PR #1355 comment 4054821928.
Move the Highlight.js core and homepage language interop into a dedicated bindings module while leaving loader behavior unchanged.
Keep prerendered highlighting and navigation coverage in the typed Cypress test suite.
edfe428 to
149251f
Compare
1 participant
The homepage renders two fixed examples but previously ran syntax highlighting and playground URL compression in the browser. This layer of #1354 prepares that content in the homepage route loader and passes three serializable strings to the existing hero.
The loader uses an isolated highlighter with only ReScript and JavaScript registered. The displayed source, highlighted tokens, dark styling, and playground link remain unchanged. The browser route no longer imports the preparation code or compression library; global language registration is intentionally left for the next layer.
Initial JavaScript falls from 997,890 to 988,509 raw bytes and from 164,222 to 161,623 gzip bytes. Serialized loader data increases initial HTML from 47,176 to 52,137 raw bytes and from 12,274 to 13,147 gzip bytes, for a net initial gzip reduction of 1,726 bytes. Client navigation gains a 3,398-byte data response (958 bytes gzip). CSS, request counts, and the 409-element homepage DOM are unchanged.
Stacked on #1363.