Skip to content
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

fix loading issue when navigating to page with async metadata #61687

Merged
merged 6 commits into from Feb 6, 2024

Conversation

ztanner
Copy link
Member

@ztanner ztanner commented Feb 5, 2024

What

Client-side transitioning to a page that triggered a loading boundary with async metadata would cause the transition to stall, potentially getting stuck in a refetch loop.

Why

In layout-router, we trigger a "lazy fetch" when we encounter a segment that we don't have cache nodes for. This calls out to the server and suspends until the data fetch is resolved, and applied to the router tree. However after suspending but before updating the client router, we set childNode.lazyData to null. When we unsuspend from the server patch action, childNode.rsc might still be missing and clearing lazyData means we've blown away the reference to the fetch we already had pending, triggering a refetch loop.

How

This removes the logic that mutates the cache node in render, as this is not concurrent safe, and doesn't appear to be needed for anything.

Fixes #61117
Fixes #61336
Closes NEXT-2361

Copy link
Member Author

ztanner commented Feb 5, 2024

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @ztanner and the rest of your teammates on Graphite Graphite

@ztanner ztanner force-pushed the 02-05-Don_t_suspend_on_server_patch_actions branch from a74ecfb to 63bb460 Compare February 5, 2024 19:05
@ijjk
Copy link
Member

ijjk commented Feb 5, 2024

Tests Passed

@ijjk
Copy link
Member

ijjk commented Feb 5, 2024

Stats from current PR

Default Build
General
vercel/next.js canary vercel/next.js 02-05-Don_t_suspend_on_server_patch_actions Change
buildDuration 11.8s 11.8s N/A
buildDurationCached 6s 5s N/A
nodeModulesSize 200 MB 200 MB N/A
nextStartRea..uration (ms) 411ms 406ms N/A
Client Bundles (main, webpack)
vercel/next.js canary vercel/next.js 02-05-Don_t_suspend_on_server_patch_actions Change
3f784ff6-HASH.js gzip 53.4 kB 53.4 kB
423.HASH.js gzip 185 B 181 B N/A
68-HASH.js gzip 29.8 kB 29.8 kB N/A
framework-HASH.js gzip 45.2 kB 45.2 kB
main-app-HASH.js gzip 238 B 240 B N/A
main-HASH.js gzip 31.8 kB 31.8 kB N/A
webpack-HASH.js gzip 1.7 kB 1.7 kB
Overall change 100 kB 100 kB
Legacy Client Bundles (polyfills)
vercel/next.js canary vercel/next.js 02-05-Don_t_suspend_on_server_patch_actions Change
polyfills-HASH.js gzip 31 kB 31 kB
Overall change 31 kB 31 kB
Client Pages
vercel/next.js canary vercel/next.js 02-05-Don_t_suspend_on_server_patch_actions Change
_app-HASH.js gzip 194 B 195 B N/A
_error-HASH.js gzip 182 B 181 B N/A
amp-HASH.js gzip 502 B 501 B N/A
css-HASH.js gzip 320 B 322 B N/A
dynamic-HASH.js gzip 2.5 kB 2.5 kB N/A
edge-ssr-HASH.js gzip 255 B 256 B N/A
head-HASH.js gzip 350 B 349 B N/A
hooks-HASH.js gzip 368 B 369 B N/A
image-HASH.js gzip 4.19 kB 4.18 kB N/A
index-HASH.js gzip 257 B 256 B N/A
link-HASH.js gzip 2.61 kB 2.61 kB N/A
routerDirect..HASH.js gzip 310 B 311 B N/A
script-HASH.js gzip 384 B 383 B N/A
withRouter-HASH.js gzip 306 B 308 B N/A
1afbb74e6ecf..834.css gzip 106 B 106 B
Overall change 106 B 106 B
Client Build Manifests
vercel/next.js canary vercel/next.js 02-05-Don_t_suspend_on_server_patch_actions Change
_buildManifest.js gzip 483 B 484 B N/A
Overall change 0 B 0 B
Rendered Page Sizes
vercel/next.js canary vercel/next.js 02-05-Don_t_suspend_on_server_patch_actions Change
index.html gzip 528 B 528 B
link.html gzip 539 B 538 B N/A
withRouter.html gzip 523 B 523 B
Overall change 1.05 kB 1.05 kB
Edge SSR bundle Size
vercel/next.js canary vercel/next.js 02-05-Don_t_suspend_on_server_patch_actions Change
edge-ssr.js gzip 94 kB 94.1 kB N/A
page.js gzip 150 kB 150 kB N/A
Overall change 0 B 0 B
Middleware size
vercel/next.js canary vercel/next.js 02-05-Don_t_suspend_on_server_patch_actions Change
middleware-b..fest.js gzip 622 B 624 B N/A
middleware-r..fest.js gzip 151 B 149 B N/A
middleware.js gzip 37.7 kB 37.7 kB N/A
edge-runtime..pack.js gzip 1.92 kB 1.92 kB
Overall change 1.92 kB 1.92 kB
Next Runtimes
vercel/next.js canary vercel/next.js 02-05-Don_t_suspend_on_server_patch_actions Change
app-page-exp...dev.js gzip 170 kB 170 kB
app-page-exp..prod.js gzip 95.8 kB 95.8 kB
app-page-tur..prod.js gzip 96.4 kB 96.4 kB
app-page-tur..prod.js gzip 91 kB 91 kB
app-page.run...dev.js gzip 142 kB 142 kB
app-page.run..prod.js gzip 90.3 kB 90.3 kB
app-route-ex...dev.js gzip 22.2 kB 22.2 kB
app-route-ex..prod.js gzip 14.9 kB 14.9 kB
app-route-tu..prod.js gzip 14.9 kB 14.9 kB
app-route-tu..prod.js gzip 14.5 kB 14.5 kB
app-route.ru...dev.js gzip 21.7 kB 21.7 kB
app-route.ru..prod.js gzip 14.5 kB 14.5 kB
pages-api-tu..prod.js gzip 9.43 kB 9.43 kB
pages-api.ru...dev.js gzip 9.7 kB 9.7 kB
pages-api.ru..prod.js gzip 9.43 kB 9.43 kB
pages-turbo...prod.js gzip 22 kB 22 kB
pages.runtim...dev.js gzip 22.7 kB 22.7 kB
pages.runtim..prod.js gzip 22 kB 22 kB
server.runti..prod.js gzip 49.7 kB 49.7 kB
Overall change 933 kB 933 kB
Diff details
Diff for page.js

Diff too large to display

Diff for 68-HASH.js

Diff too large to display

Commit: 8e93c13

@ztanner ztanner force-pushed the 02-05-Don_t_suspend_on_server_patch_actions branch from e9e832f to 8e93c13 Compare February 5, 2024 22:09
@ztanner ztanner marked this pull request as ready for review February 5, 2024 22:36
@ztanner ztanner merged commit da842e1 into canary Feb 6, 2024
69 checks passed
@ztanner ztanner deleted the 02-05-Don_t_suspend_on_server_patch_actions branch February 6, 2024 15:10
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 21, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
4 participants