Repository navigation
Pass lazy response lifecycle capabilities into App rendering - #100395
Merged
Merged
Conversation
kassens
added this pull request to stack #100328
October 19, 2026 13:23
Contributor
Failing CI jobsCommit: a24c2c9 | About building and testing Next.js |
kassens
removed this pull request from stack #100328
October 19, 2026 17:13
kassens
force-pushed
the
kassens/render-response-lifecycle
branch
from
October 19, 2026 17:13
fb328a4 to
0814895
Compare
Base automatically changed from
kassens/render-interception-flag
to
kassens/render-request-headers
October 19, 2026 17:13
kassens
added this pull request to stack #100411
October 19, 2026 17:16
kassens
force-pushed
the
kassens/render-response-lifecycle
branch
from
October 19, 2026 18:08
0814895 to
2a8864b
Compare
kassens
force-pushed
the
kassens/render-response-lifecycle
branch
3 times, most recently
from
October 19, 2026 21:36
f2f5d22 to
a908fb5
Compare
kassens
force-pushed
the
kassens/render-response-lifecycle
branch
3 times, most recently
from
October 20, 2026 02:16
3a7f697 to
8a64f9f
Compare
kassens
force-pushed
the
kassens/render-response-lifecycle
branch
from
October 20, 2026 13:04
8a64f9f to
f3bfca9
Compare
lubieowoce
approved these changes
Oct 22, 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
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
Continue decoupling App Router rendering from HTTP responses by binding lazy development response capabilities at the route-module boundary. HMR cancellation, validation scheduling, and worker snapshots use these capabilities instead of accessing
originalResponsein the renderer.Preserves listener registration timing, abort reasons, live completion state, and the response wrapper's preview-cookie synchronization. Adds unit coverage for these behaviors and scoped import restrictions to keep response lifecycle access at the adapter boundary.
Verification
38 test executions passed:
test-dev-turbo: HMR cancellation, validation scheduling, and worker source maps: 11; 9 snapshots.__NEXT_CACHE_COMPONENTS=true test-dev-turbo: HMR cancellation and static-shell validation: 8; 1 snapshot.test-dev-webpack: HMR cancellation and validation scheduling: 6.test-start-webpack: standalone Node/Edge bundling: 2.