perf: hashless prerender bundles - #57
Draft
MohamedH1998 wants to merge 2 commits into
Draft
Conversation
(cherry picked from commit 3eb3a1e)
commit: |
Collaborator
Author
|
Ran a cold A/B on the Cloudflare Docs build to check the real-world win
The override works as intended — prerender chunks come back hashless — but it Looks like Rolldown has since sped up its chunk hashing, so the bottleneck this Draft PR in the Cloudflare docs: cloudflare/cloudflare-docs#32304 |
Draft
MohamedH1998
marked this pull request as draft
July 27, 2026 14:45
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What & why
Skip hashing Astro's temporary prerender bundle - shout out @ttmx for this
Speeds up large docs builds by giving Astro's throwaway prerender bundle
hashless filenames, so Rolldown skips its per-chunk hash-graph walk.
Why
Astro imports the prerender bundle to render static pages, then deletes it. On
large sites, hashing its thousands of lazy content chunks dominates the build —
Rolldown re-walks the transitive chunk graph once per hash placeholder, which is
wasted work on an intermediate that's thrown away.
Cloudflare Docs (~8.7k pages), isolated cold-build A/B:
~30% less wall time, ~57% less prerender bundling.
What
client and asset hashes are unchanged.
rolldownOptionsoutput key, not thedeprecation-track
rollupOptionsalias.Checklist
lgtm+on my issue or discussion), or I'm on the teampackages/nimbus-starter-source/, not thetemplatesbranchcreate-nimbus-docschangeset if the starter changed)pnpm typecheck,pnpm -r test, andpnpm templates:checkall greenFirst time here?
Nimbus works from issues and discussions, not drive-by PRs, so unapproved PRs from
outside the team are closed automatically. If that's you, open an
issue (bug or fix proposal)
or a discussion (feature) instead —
once a maintainer approves you there, your PRs stay open. See
CONTRIBUTING.md.