test: test Next.js cacheComponents in CI#1324
Merged
Conversation
With cacheComponents, pages get/stay mounted in the background on navigation, causing issues with e2e test selectors. See vercel/next.js#86577
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
franky47
added a commit
that referenced
this pull request
Feb 9, 2026
|
🎉 This PR is included in version 2.8.9 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
It requires running a codemod to comment out the
export const dynamic = 'force-dynamic'directives, and refactors e2e locators to account for Activity having both pages (source & destination) being mounted in the DOM during navigation.Prelude to making a reproduction for #1273.