Repository navigation
Conversation
Contributor
Stats from current PR🔴 3 regressions, 1 improvement
📊 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
Build Cache
📦 WebpackClient Main Bundles
Polyfills
Pages
Server Edge SSR
Middleware
Build DetailsBuild Manifests
Build Cache
🔄 Shared (bundler-independent)Runtimes
📝 Changed Files (20 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.jsfailed to diffapp-page-tur..time.prod.jsDiff too large to display app-page.runtime.dev.jsfailed to diffapp-page.runtime.prod.jsDiff too large to display app-route-ex..ntime.dev.jsDiff too large to display app-route-ex..time.prod.jsDiff too large to display app-route-tu..ntime.dev.jsDiff too large to display app-route-tu..time.prod.jsDiff too large to display app-route-tu..ntime.dev.jsDiff too large to display app-route-tu..time.prod.jsDiff too large to display app-route.runtime.dev.jsDiff too large to display app-route.ru..time.prod.jsDiff too large to display use-cache-pr..ntime.dev.jsDiff too large to display use-cache-pr..ntime.dev.jsDiff too large to display use-cache-pr..ntime.dev.jsDiff too large to display use-cache-pr..ntime.dev.jsDiff too large to display 📎 Tarball URLCommit: 71f1fc9 |
Contributor
Tests PassedCommit: 71f1fc9 |
ztanner
marked this pull request as ready for review
August 4, 2026 21:14
gnoff
approved these changes
Aug 4, 2026
ztanner
force-pushed
the
ztanner/separate-app-page-render-pipelines
branch
from
August 5, 2026 00:16
6068371 to
da1655d
Compare
ztanner
force-pushed
the
ztanner/separate-app-page-render-pipelines
branch
from
August 5, 2026 00:28
da1655d to
e6f8e0a
Compare
ztanner
force-pushed
the
ztanner/separate-app-page-render-pipelines
branch
from
August 5, 2026 00:55
e6f8e0a to
71f1fc9
Compare
m-kawafuji
pushed a commit
to m-kawafuji/next.js
that referenced
this pull request
Aug 8, 2026
## Summary App Page rendering currently shares a single implementation that uses the Work Store execution mode to choose between the request and prerender pipelines. This change: - Extracts mode-neutral App Page preparation into a shared step. - Gives request rendering and prerendering separate top-level implementations. - Moves Work Store creation into the corresponding entrypoint. - Makes each path call `renderToStream` or `prerenderToStream` directly, removing the execution-mode dispatch between them. This moves the rendering decision to the App Page boundary and creates a clearer path toward removing execution mode from the Work Store entirely.
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
App Page rendering currently shares a single implementation that uses the Work Store execution mode to choose between the request and prerender pipelines.
This change:
renderToStreamorprerenderToStreamdirectly, removing the execution-mode dispatch between them.This moves the rendering decision to the App Page boundary and creates a clearer path toward removing execution mode from the Work Store entirely.