perf(homepage): load syntax grammars at content boundaries [Codex] - #1365
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 | f4c30a5 | 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. |
6054e84 to
c6cc546
Compare
c6cc546 to
f78be30
Compare
![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: f78be30277
ℹ️ 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".
f78be30 to
55970a8
Compare
55970a8 to
ecefa67
Compare
ecefa67 to
1fc6281
Compare
|
Codex Review: Didn't find any major issues. Nice work! 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". |
1fc6281 to
85c6b02
Compare
85c6b02 to
e610280
Compare
e610280 to
fe3b1b7
Compare
Remove runtime grammar registration from the shared root. Register content languages at a pathless layout boundary and JavaScript at the lazy playground boundary, with cold-navigation and direct-load coverage.
Keep syntax-runtime bundle exclusion and direct/cold-navigation JSON highlighting coverage for PR #1355 comment 4054821928.
Load the existing YAML grammar at the content boundary and verify YAML/yml aliases and installation-example highlighting. This removes application console errors exposed by the strict Cypress navigation tests.
Keep npm language imports in the dedicated Highlight.js binding module and leave content highlighting responsible only for registration policy.
fe3b1b7 to
f4c30a5
Compare
1 participant
The homepage renders prehighlighted examples, but the shared root still downloads Highlight.js and every content grammar. This layer in #1354 moves those runtime imports out of the homepage graph.
A pathless content layout registers the existing languages before documentation, blog, community, and package routes render. The lazy playground registers only JavaScript through the shared package, so direct visits keep highlighted compiler output without relying on an earlier documentation visit. Both boundaries preserve existing language aliases and avoid effects, loaders, and extra DOM.
Initial homepage JavaScript drops from 161,623 to 143,792 gzipped bytes in the production asset report. CSS and DOM counts are unchanged. Builds on #1364.