Include additional prerender metadata about build-time routes#96080
Merged
Conversation
![vercel[bot]](https://avatars.githubusercontent.com/in/8329?s=60&v=4){kind=small}
gnoff
force-pushed
the
jstory/prerender-metadata
branch
from
July 22, 2026 21:02
4396e4f to
99283ba
Compare
Contributor
Stats from current PR🔴 1 regression, 2 improvements
📊 All Metrics📖 Metrics GlossaryDev Server Metrics:
Build Metrics:
Change Thresholds:
⚡ Dev Server
📦 Dev Server (Webpack) (Legacy)📦 Dev Server (Webpack)
⚡ Production Builds
📦 Production Builds (Webpack) (Legacy)📦 Production Builds (Webpack)
📦 Bundle SizesBundle Sizes⚡ TurbopackClient Main Bundles
Server Middleware
Build DetailsBuild Manifests
📦 WebpackClient Main Bundles
Polyfills
Pages
Server Edge SSR
Middleware
Build DetailsBuild Manifests
Build Cache
🔄 Shared (bundler-independent)Runtimes
📝 Changed Files (12 files)Files with changes:
View diffsapp-page-exp..ntime.dev.jsfailed to diffapp-page-exp..time.prod.jsDiff too large to display app-page-tur..ntime.dev.jsfailed to diffapp-page-tur..time.prod.jsDiff too large to display app-page-tur..ntime.dev.jsDiff too large to display app-page-tur..time.prod.jsDiff too large to display app-page.runtime.dev.jsDiff too large to display app-page.runtime.prod.jsDiff too large to display pages-api-tu..time.prod.jsDiff too large to display pages-api.runtime.dev.jsDiff too large to display pages-turbo...time.prod.jsDiff too large to display pages.runtime.dev.jsDiff too large to display 📎 Tarball URLCommit: 9ab89d3 |
Contributor
Tests PassedCommit: 9ab89d3 |
gnoff
changed the title
gnoff
force-pushed
the
jstory/prerender-metadata
branch
from
July 24, 2026 01:26
47a02db to
9ab89d3
Compare
timneutkens
approved these changes
Jul 24, 2026
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
3 participants
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.
Building on top of @agadzik work (see first commit)
Adds prerender route metadata to help downstream consumers understand the nature of build-time prerenders
We break down prerender taxonomy as follows
routeType describes what the prerender serves:
route: a non-UI endpoint, such as a Route Handler.page: a page whose route parameters are fully known.shell: a reusable PPR shell for a parameterized page.fallback: a fallback that may serve or specialize additional parameter values.response describes how complete the static response is:
complete: the prerender contains the completed response.initial: an initial response is available, but the page UI is incomplete; in practice this applies to partially prerenderable UI routes.empty: there is no initial static response to send.compute describes the request-time work required:
static: no request-time server compute is needed.resuming: request-time compute resumes from the static response.blocking: the initial response is blocked until request-time compute starts, but it may stream while that compute continues.htmlSizereports the byte size of prerendered HTML when the output has HTML.The taxonomy is included only on a prerender group’s canonical primary output—the HTML output for pages or the response output for Route Handlers—and is omitted from secondary RSC and segment-data outputs.