-
Notifications
You must be signed in to change notification settings - Fork 27.5k
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
[do not merge]hide observer #75160
base: canary
Are you sure you want to change the base?
[do not merge]hide observer #75160
Conversation
Failing test suitesCommit: 8e67c70
Expand output● app dir - prefetching (custom staleTime) › should not fetch again when a static page was prefetched when navigating to it twice
Read more about building and testing Next.js in contributing.md.
Expand output● app dir client cache with parallel routes › prefetch={true} › should prefetch the full page
● app dir client cache with parallel routes › prefetch={true} › should re-use the cache for the full page, only for 5 mins
Read more about building and testing Next.js in contributing.md.
Expand output● Invalid hrefs › production mode › should preload with forwardRef
● Invalid hrefs › production mode › should preload with child ref with React.createRef
● Invalid hrefs › production mode › should preload with child ref with function
● Invalid hrefs › production mode › should preload with child ref with function that returns a cleanup function
Read more about building and testing Next.js in contributing.md.
Expand output● app dir client cache semantics (experimental staleTimes) › dynamic: 0 › prefetch={true} › should re-use the cache for 5 minutes (default "static" time)
● app dir client cache semantics (experimental staleTimes) › static: 180 › prefetch={true} › should use the custom static override time (3 minutes)
● app dir client cache semantics (experimental staleTimes) › static: 180 › prefetch={undefined} - default › should re-use the loading boundary for the custom static override time (3 minutes)
Read more about building and testing Next.js in contributing.md.
Expand output● segment cache (basic tests) › navigate before any data has loaded into the prefetch cache
● segment cache (basic tests) › navigate with prefetched data
● segment cache (basic tests) › navigate to page with lazily-generated (not at build time) static param
● segment cache (basic tests) › prefetch interception route
● segment cache (basic tests) › skips dynamic request if prefetched data is fully static
● segment cache (basic tests) › skips static layouts during partially static navigation
Read more about building and testing Next.js in contributing.md.
Expand output● segment cache (revalidation) › evict client cache when Server Action calls revalidatePath
● segment cache (revalidation) › evict client cache when Server Action calls revalidateTag
Read more about building and testing Next.js in contributing.md.
Expand output● segment cache prefetch scheduling › increases the priority of a viewport-initiated prefetch on hover
● segment cache prefetch scheduling › even on mouseexit, any link that was previously hovered is prioritized over links that were never hovered at all
● segment cache prefetch scheduling › cancels a viewport-initiated prefetch if the link leaves the viewport before it finishes
● segment cache prefetch scheduling › reschedules a link's prefetch when it re-enters the viewport
Read more about building and testing Next.js in contributing.md.
Expand output● segment cache (incremental opt in) › multiple prefetches to same link are deduped › page with PPR enabled
● segment cache (incremental opt in) › multiple prefetches to same link are deduped › page with PPR enabled, and has a dynamic param
● segment cache (incremental opt in) › multiple prefetches to same link are deduped › page with PPR disabled
● segment cache (incremental opt in) › multiple prefetches to same link are deduped › page with PPR disabled, and has a loading boundary
● segment cache (incremental opt in) › prefetches a shared layout on a PPR-enabled route that was previously omitted from a non-PPR-enabled route
● segment cache (incremental opt in) › when a link is prefetched with , no dynamic request is made on navigation
● segment cache (incremental opt in) › when prefetching with prefetch=true, refetches cache entries that only contain partial data
● segment cache (incremental opt in) › when prefetching with prefetch=true, refetches partial cache entries even if there's already a pending PPR request
Read more about building and testing Next.js in contributing.md.
Expand output● segment cache memory pressure › evicts least recently used prefetch data once cache size exceeds limit
Read more about building and testing Next.js in contributing.md.
Expand output● parallel-routes-revalidation › server action revalidation › should not trigger a refresh for the page that is being redirected to
Read more about building and testing Next.js in contributing.md.
Expand output● app dir client cache semantics (default semantics) › prefetch={true} › should prefetch the full page
● app dir client cache semantics (default semantics) › prefetch={true} › should re-use the cache for the full page, only for 5 mins
● app dir client cache semantics (default semantics) › prefetch={true} › should prefetch again after 5 mins if the link is visible again
● app dir client cache semantics (default semantics) › prefetch={undefined} - default › should prefetch partially a dynamic page
Read more about building and testing Next.js in contributing.md.
Expand output● searchparams-reuse-loading › Without Middleware › should correctly return different RSC data for full prefetches with different searchParam values
● searchparams-reuse-loading › With Middleware › should correctly return different RSC data for full prefetches with different searchParam values
● searchparams-reuse-loading › should re-use loading from "full" prefetch for param-full URL when navigating to param-less route
● searchparams-reuse-loading › should re-use loading from "full" prefetch for param-less URL when navigating to param-full route
● searchparams-reuse-loading › should re-use loading from "full" prefetch for param-full URL when navigating to param-full route
Read more about building and testing Next.js in contributing.md. |
Stats from current PRDefault Build (Increase detected
|
vercel/next.js canary | vercel/next.js test/hide-observer | Change | |
---|---|---|---|
buildDuration | 18.6s | 15.7s | N/A |
buildDurationCached | 14.7s | 12.5s | N/A |
nodeModulesSize | 418 MB | 418 MB | N/A |
nextStartRea..uration (ms) | 400ms | 399ms | N/A |
Client Bundles (main, webpack)
vercel/next.js canary | vercel/next.js test/hide-observer | Change | |
---|---|---|---|
5306-HASH.js gzip | 54 kB | 53.9 kB | N/A |
8276.HASH.js gzip | 169 B | 168 B | N/A |
8377-HASH.js gzip | 5.46 kB | 5.46 kB | N/A |
bccd1874-HASH.js gzip | 52.9 kB | 52.9 kB | ✓ |
framework-HASH.js gzip | 57.5 kB | 57.5 kB | N/A |
main-app-HASH.js gzip | 240 B | 242 B | N/A |
main-HASH.js gzip | 34.4 kB | 34.4 kB | N/A |
webpack-HASH.js gzip | 1.71 kB | 1.71 kB | N/A |
Overall change | 52.9 kB | 52.9 kB | ✓ |
Legacy Client Bundles (polyfills)
vercel/next.js canary | vercel/next.js test/hide-observer | Change | |
---|---|---|---|
polyfills-HASH.js gzip | 39.4 kB | 39.4 kB | ✓ |
Overall change | 39.4 kB | 39.4 kB | ✓ |
Client Pages
vercel/next.js canary | vercel/next.js test/hide-observer | Change | |
---|---|---|---|
_app-HASH.js gzip | 193 B | 193 B | ✓ |
_error-HASH.js gzip | 193 B | 193 B | ✓ |
amp-HASH.js gzip | 512 B | 510 B | N/A |
css-HASH.js gzip | 343 B | 342 B | N/A |
dynamic-HASH.js gzip | 1.84 kB | 1.84 kB | ✓ |
edge-ssr-HASH.js gzip | 265 B | 265 B | ✓ |
head-HASH.js gzip | 363 B | 362 B | N/A |
hooks-HASH.js gzip | 393 B | 392 B | N/A |
image-HASH.js gzip | 4.59 kB | 4.58 kB | N/A |
index-HASH.js gzip | 268 B | 268 B | ✓ |
link-HASH.js gzip | 2.35 kB | 2.35 kB | N/A |
routerDirect..HASH.js gzip | 328 B | 328 B | ✓ |
script-HASH.js gzip | 397 B | 397 B | ✓ |
withRouter-HASH.js gzip | 323 B | 326 B | N/A |
1afbb74e6ecf..834.css gzip | 106 B | 106 B | ✓ |
Overall change | 3.59 kB | 3.59 kB | ✓ |
Client Build Manifests
vercel/next.js canary | vercel/next.js test/hide-observer | Change | |
---|---|---|---|
_buildManifest.js gzip | 748 B | 747 B | N/A |
Overall change | 0 B | 0 B | ✓ |
Rendered Page Sizes
vercel/next.js canary | vercel/next.js test/hide-observer | Change | |
---|---|---|---|
index.html gzip | 523 B | 523 B | ✓ |
link.html gzip | 538 B | 538 B | ✓ |
withRouter.html gzip | 519 B | 520 B | N/A |
Overall change | 1.06 kB | 1.06 kB | ✓ |
Edge SSR bundle Size
vercel/next.js canary | vercel/next.js test/hide-observer | Change | |
---|---|---|---|
edge-ssr.js gzip | 129 kB | 129 kB | N/A |
page.js gzip | 208 kB | 208 kB | N/A |
Overall change | 0 B | 0 B | ✓ |
Middleware size
vercel/next.js canary | vercel/next.js test/hide-observer | Change | |
---|---|---|---|
middleware-b..fest.js gzip | 668 B | 665 B | N/A |
middleware-r..fest.js gzip | 155 B | 156 B | N/A |
middleware.js gzip | 31.3 kB | 31.3 kB | N/A |
edge-runtime..pack.js gzip | 844 B | 844 B | ✓ |
Overall change | 844 B | 844 B | ✓ |
Next Runtimes
vercel/next.js canary | vercel/next.js test/hide-observer | Change | |
---|---|---|---|
274-experime...dev.js gzip | 322 B | 322 B | ✓ |
274.runtime.dev.js gzip | 314 B | 314 B | ✓ |
app-page-exp...dev.js gzip | 375 kB | 375 kB | ✓ |
app-page-exp..prod.js gzip | 130 kB | 130 kB | ✓ |
app-page-tur..prod.js gzip | 143 kB | 143 kB | ✓ |
app-page-tur..prod.js gzip | 139 kB | 139 kB | ✓ |
app-page.run...dev.js gzip | 363 kB | 363 kB | ✓ |
app-page.run..prod.js gzip | 126 kB | 126 kB | ✓ |
app-route-ex...dev.js gzip | 37.6 kB | 37.6 kB | ✓ |
app-route-ex..prod.js gzip | 25.6 kB | 25.6 kB | ✓ |
app-route-tu..prod.js gzip | 25.6 kB | 25.6 kB | ✓ |
app-route-tu..prod.js gzip | 25.4 kB | 25.4 kB | ✓ |
app-route.ru...dev.js gzip | 39.2 kB | 39.2 kB | ✓ |
app-route.ru..prod.js gzip | 25.4 kB | 25.4 kB | ✓ |
pages-api-tu..prod.js gzip | 9.69 kB | 9.69 kB | ✓ |
pages-api.ru...dev.js gzip | 11.6 kB | 11.6 kB | ✓ |
pages-api.ru..prod.js gzip | 9.68 kB | 9.68 kB | ✓ |
pages-turbo...prod.js gzip | 21.9 kB | 21.9 kB | ✓ |
pages.runtim...dev.js gzip | 27.7 kB | 27.7 kB | ✓ |
pages.runtim..prod.js gzip | 21.9 kB | 21.9 kB | ✓ |
server.runti..prod.js gzip | 916 kB | 916 kB | ✓ |
Overall change | 2.47 MB | 2.47 MB | ✓ |
build cache Overall increase ⚠️
vercel/next.js canary | vercel/next.js test/hide-observer | Change | |
---|---|---|---|
0.pack gzip | 2.1 MB | 2.09 MB | N/A |
index.pack gzip | 74.3 kB | 74.9 kB | |
Overall change | 74.3 kB | 74.9 kB |
Diff details
Diff for main-HASH.js
Diff too large to display
No description provided.