test(e2e): Add Next.js cache component nesting scenarios - #24704
Merged
Merged
Conversation
s1gr1d
commented
Sep 24, 2026
Member
Author
There was a problem hiding this comment.
From here, all is same-same, but just with span streaming
Contributor
size-limit report 📦
|
andreiborza
approved these changes
Sep 25, 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.
Add tests for 4 different nested cache component scenarios. Currently all in a "failed" state as this is not yet implemented.
1. Cached layout in the middle
2. Dynamic Layouts, Cached Leaf
3. Mixed lifetimes: two cache links, but pointing to a different origin
4. Shared layout across sibling routes: Origin trace is different than serving (
/aand/b)Closes #24701