-
Notifications
You must be signed in to change notification settings - Fork 29.6k
[Cache Components] Less cache warming in dev if runtime prefetch not enabled #84996
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: canary
Are you sure you want to change the base?
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. |
Hi there 👋 It looks like this PR introduces broken links to the docs, please take a moment to fix them before merging:
Thank you 🙏 |
Failing test suitesCommit: 997ac1e | About building and testing Next.js
Expand output● app dir - prefetching › should immediately render the loading state for a dynamic segment when fetched from higher up in the tree
Expand output● app-dir - server source maps › sourcemaps errors during module evaluation
Expand output● segment cache (search params) › when fetching with PPR, does not include search params in the cache key
Expand output● segment cache (staleness) › expires runtime prefetches when their stale time has elapsed
|
If we're not going to be validating a prefetch (which is yet to be implemented), we don't to warm caches that aren't reachable in the static stage (i.e. in a static prerender).