-
Notifications
You must be signed in to change notification settings - Fork 28.7k
Upgrade React from 7b402084-20250107
to 42687267-20250108
#74649
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
Conversation
Failing test suitesCommit: c2fee07
Expand output● create-next-app with package manager yarn › should use yarn when user-agent is yarn
● create-next-app with package manager yarn › should use yarn for --use-yarn flag with example
Read more about building and testing Next.js in contributing.md.
Expand output● create-next-app with package manager pnpm › should use pnpm when user-agent is pnpm
Read more about building and testing Next.js in contributing.md.
Expand output● Cleaning distDir › production mode › should clean up .next before build start
Read more about building and testing Next.js in contributing.md.
Expand output● app-custom-routes › works with api prefix correctly › statically generates correctly with no dynamic usage
● app-custom-routes › works with api prefix correctly › does not statically generate with dynamic usage
● app-custom-routes › works with generateStaticParams correctly › responds correctly on /static/first/data.json
● app-custom-routes › works with generateStaticParams correctly › responds correctly on /static/second/data.json
● app-custom-routes › works with generateStaticParams correctly › responds correctly on /static/three/data.json
● app-custom-routes › works with generateStaticParams correctly › revalidates correctly on /revalidate-1/first/data.json
● app-custom-routes › works with generateStaticParams correctly › revalidates correctly on /revalidate-1/second/data.json
● app-custom-routes › works with generateStaticParams correctly › revalidates correctly on /revalidate-1/three/data.json
● app-custom-routes › basic fetch request with a response › made via a GET request › responds correctly on /basic/endpoint
● app-custom-routes › basic fetch request with a response › made via a GET request › responds correctly on /basic/vercel/endpoint
● app-custom-routes › basic fetch request with a response › made via a POST request › responds correctly on /basic/endpoint
● app-custom-routes › basic fetch request with a response › made via a POST request › responds correctly on /basic/vercel/endpoint
● app-custom-routes › basic fetch request with a response › made via a PUT request › responds correctly on /basic/endpoint
● app-custom-routes › basic fetch request with a response › made via a PUT request › responds correctly on /basic/vercel/endpoint
● app-custom-routes › basic fetch request with a response › made via a DELETE request › responds correctly on /basic/endpoint
● app-custom-routes › basic fetch request with a response › made via a DELETE request › responds correctly on /basic/vercel/endpoint
● app-custom-routes › basic fetch request with a response › made via a PATCH request › responds correctly on /basic/endpoint
● app-custom-routes › basic fetch request with a response › made via a PATCH request › responds correctly on /basic/vercel/endpoint
● app-custom-routes › basic fetch request with a response › abort via a GET request › aborts without error on /basic/endpoint
● app-custom-routes › basic fetch request with a response › abort via a GET request › aborts without error on /basic/vercel/endpoint
● app-custom-routes › basic fetch request with a response › abort via a POST request › aborts without error on /basic/endpoint
● app-custom-routes › basic fetch request with a response › abort via a POST request › aborts without error on /basic/vercel/endpoint
● app-custom-routes › basic fetch request with a response › abort via a PUT request › aborts without error on /basic/endpoint
● app-custom-routes › basic fetch request with a response › abort via a PUT request › aborts without error on /basic/vercel/endpoint
● app-custom-routes › basic fetch request with a response › abort via a DELETE request › aborts without error on /basic/endpoint
● app-custom-routes › basic fetch request with a response › abort via a DELETE request › aborts without error on /basic/vercel/endpoint
● app-custom-routes › basic fetch request with a response › abort via a PATCH request › aborts without error on /basic/endpoint
● app-custom-routes › basic fetch request with a response › abort via a PATCH request › aborts without error on /basic/vercel/endpoint
● app-custom-routes › basic fetch request with a response › route groups › routes to the correct handler
● app-custom-routes › basic fetch request with a response › request › can read query parameters
● app-custom-routes › basic fetch request with a response › request › can read query parameters (edge)
● app-custom-routes › basic fetch request with a response › response › supports the NextResponse.rewrite() helper
● app-custom-routes › basic fetch request with a response › response › supports the NextResponse.redirect() helper
● app-custom-routes › basic fetch request with a response › response › supports the NextResponse.json() helper
● app-custom-routes › body › can handle handle a streaming request and streaming response
● app-custom-routes › body › can handle handle a streaming request and streaming response (edge)
● app-custom-routes › body › can read a JSON encoded body
● app-custom-routes › body › can read a JSON encoded body (edge)
● app-custom-routes › body › can read a JSON encoded body for DELETE requests
● app-custom-routes › body › can read a JSON encoded body for OPTIONS requests
● app-custom-routes › body › can read a streamed JSON encoded body
● app-custom-routes › body › can read a streamed JSON encoded body (edge)
● app-custom-routes › body › can read the text body
● app-custom-routes › body › can read the text body (edge)
● app-custom-routes › context › provides params to routes with dynamic parameters
● app-custom-routes › context › provides params to routes with catch-all routes
● app-custom-routes › context › does not provide params to routes without dynamic parameters
● app-custom-routes › hooks › headers › gets the correct values
● app-custom-routes › hooks › cookies › gets the correct values
● app-custom-routes › hooks › req.cookies › gets the correct values
● app-custom-routes › hooks › (await cookies()).has() › gets the correct values
● app-custom-routes › hooks › redirect › can respond correctly
● app-custom-routes › hooks › permanentRedirect › can respond correctly
● app-custom-routes › hooks › notFound › can respond correctly in nodejs
● app-custom-routes › hooks › notFound › can respond correctly in edge
● app-custom-routes › error conditions › responds with 400 (Bad Request) when the requested method is not a valid HTTP method
● app-custom-routes › error conditions › responds with 405 (Method Not Allowed) when method is not implemented
● app-custom-routes › error conditions › responds with 500 (Internal Server Error) when the handler throws an error
● app-custom-routes › error conditions › responds with 500 (Internal Server Error) when the handler calls NextResponse.next()
● app-custom-routes › automatic implementations › implements HEAD on routes with GET already implemented
● app-custom-routes › automatic implementations › implements OPTIONS on routes
● app-custom-routes › edge functions › returns response using edge runtime
● app-custom-routes › edge functions › returns a response when headers are accessed
● app-custom-routes › dynamic = "force-static" › strips search, headers, and domain from request
● app-custom-routes › customized metadata routes › should work if conflict with metadata routes convention
● app-custom-routes › no response returned › should print an error when no response is returned
● app-custom-routes › no bundle error › should not print bundling warning about React
● Test suite failed to run
Read more about building and testing Next.js in contributing.md.
Expand output● app-root-params - multiple roots › should have root params on dashboard pages
● app-root-params - multiple roots › should not have root params on marketing pages
● Test suite failed to run
Read more about building and testing Next.js in contributing.md.
Expand output● app-dir - custom-cache-handler - cjs-default-export › cjs default export › should have logs from cache-handler
● app-dir - custom-cache-handler - esm › esm default export › should have logs from cache-handler
Read more about building and testing Next.js in contributing.md.
Expand output● Dynamic IO Prospective Render Errors - Standard Build › should not log an error when the prospective render errors with an Error in a Page
● Dynamic IO Prospective Render Errors - Standard Build › should not log an error when the prospective render errors with a string in a Page
● Dynamic IO Prospective Render Errors - Standard Build › should not log an error when the prospective render errors with null in a Page
● Dynamic IO Prospective Render Errors - Standard Build › should not log an error when the prospective render errors with an object in a Page
● Dynamic IO Prospective Render Errors - Standard Build › should not log an error when the prospective render errors with an Error in a route
● Dynamic IO Prospective Render Errors - Standard Build › should not log an error when the prospective render errors with a string in a route
● Dynamic IO Prospective Render Errors - Standard Build › should not log an error when the prospective render errors with undefined in a route
● Dynamic IO Prospective Render Errors - Standard Build › should not log an error when the prospective render errors with an object in a route
● Test suite failed to run
Read more about building and testing Next.js in contributing.md.
Expand output● dynamic-io › should partially prerender pages that use async cookies
● dynamic-io › should partially prerender pages that use sync cookies
● dynamic-io › should be able to pass cookies as a promise to another component and trigger an intermediate Suspense boundary
● dynamic-io › should be able to access cookie properties asynchronously
● dynamic-io › should be able to access cookie properties synchronously
● Test suite failed to run
Read more about building and testing Next.js in contributing.md.
Expand output● app-dir create root layout › page.tsx › create root layout
● Test suite failed to run
Read more about building and testing Next.js in contributing.md.
Expand output● app dir - metadata dynamic routes suspense › should render metadata in head even root layout is wrapped with Suspense
● Test suite failed to run
Read more about building and testing Next.js in contributing.md.
Expand output● Basic Module Include Paths Support ({"sass": "1.54.0"}) › should render the module
● Basic Module Include Paths Support ({"sass-embedded": "1.75.0"}) › should render the module
Read more about building and testing Next.js in contributing.md.
Expand output● Good CSS Import from node_modules ({"sass-embedded": "1.75.0"}) › should render the page
● Test suite failed to run
Read more about building and testing Next.js in contributing.md.
Expand output● css-order loose › should load correct styles navigating first -> second
● css-order loose › should load correct styles navigating first -> third
● css-order loose › should load correct styles navigating first -> first-client
● css-order loose › should load correct styles navigating first -> second-client
● css-order loose › should load correct styles navigating second -> first
● css-order loose › should load correct styles navigating second -> third
● css-order loose › should load correct styles navigating second -> first-client
● css-order loose › should load correct styles navigating second -> second-client
● css-order loose › should load correct styles navigating third -> first
● css-order loose › should load correct styles navigating third -> second
● css-order loose › should load correct styles navigating third -> first-client
● css-order loose › should load correct styles navigating third -> second-client
● css-order loose › should load correct styles navigating first-client -> first
● css-order loose › should load correct styles navigating first-client -> second
● css-order loose › should load correct styles navigating first-client -> third
● css-order loose › should load correct styles navigating first-client -> second-client
● css-order loose › should load correct styles navigating second-client -> first
● css-order loose › should load correct styles navigating second-client -> second
● css-order loose › should load correct styles navigating second-client -> third
● css-order loose › should load correct styles navigating second-client -> first-client
● css-order loose › should load correct styles navigating interleaved-a -> interleaved-b
● css-order loose › should load correct styles navigating interleaved-b -> interleaved-a
● css-order loose › should load correct styles navigating big-interleaved-a -> big-interleaved-b
● css-order loose › should load correct styles navigating big-interleaved-b -> big-interleaved-a
● css-order loose › should load correct styles navigating pages-first -> pages-second
● css-order loose › should load correct styles navigating pages-first -> pages-third
● css-order loose › should load correct styles navigating pages-second -> pages-first
● css-order loose › should load correct styles navigating pages-second -> pages-third
● css-order loose › should load correct styles navigating pages-third -> pages-first
● css-order loose › should load correct styles navigating pages-third -> pages-second
● css-order loose › should load correct styles navigating pages-interleaved-a -> pages-interleaved-b
● css-order loose › should load correct styles navigating pages-interleaved-b -> pages-interleaved-a
● css-order loose › should load correct styles navigating pages-reversed-a -> pages-reversed-b
● css-order loose › should load correct styles navigating pages-reversed-b -> pages-reversed-a
● css-order loose › should load correct styles navigating pages-partial-reversed-a -> pages-partial-reversed-b
● css-order loose › should load correct styles navigating pages-partial-reversed-b -> pages-partial-reversed-a
● css-order strict › should load correct styles on first
● css-order strict › should load correct styles on second
● css-order strict › should load correct styles on third
● css-order strict › should load correct styles on first-client
● css-order strict › should load correct styles on second-client
● css-order strict › should load correct styles on interleaved-a
● css-order strict › should load correct styles on interleaved-b
● css-order strict › should load correct styles on big-interleaved-a
● css-order strict › should load correct styles on big-interleaved-b
● css-order strict › should load correct styles on reversed-a
● css-order strict › should load correct styles on reversed-b
● css-order strict › should load correct styles on partial-reversed-a
● css-order strict › should load correct styles on partial-reversed-b
● css-order strict › should load correct styles on pages-first
● css-order strict › should load correct styles on pages-second
● css-order strict › should load correct styles on pages-third
● css-order strict › should load correct styles on pages-interleaved-a
● css-order strict › should load correct styles on pages-interleaved-b
● css-order strict › should load correct styles on pages-reversed-a
● css-order strict › should load correct styles on pages-reversed-b
● css-order strict › should load correct styles on pages-partial-reversed-a
● css-order strict › should load correct styles on pages-partial-reversed-b
● css-order strict › should load correct styles on global-first
● css-order strict › should load correct styles on global-second
● css-order strict › should load correct styles on vendor
Read more about building and testing Next.js in contributing.md.
Expand output● app dir client cache semantics (experimental staleTimes) › static: 180 › should skip dev
● app dir client cache semantics (experimental staleTimes) › dynamic: 0, static: 0 › should trigger a loading state before fetching the page, followed by fresh data on every subsequent navigation
● app dir client cache semantics (experimental staleTimes) › dynamic: 0, static: 0 › without a loading boundary › should get fresh data on every subsequent navigation
Read more about building and testing Next.js in contributing.md.
Expand output● Dynamic IO Errors - With Minification › Sync Dynamic - Without Fallback - client searchParams › should error the build if dynamic IO happens in the root (outside a Suspense)
● Dynamic IO Errors - With Minification › Sync Dynamic - With Fallback - server searchParams › should not error the build when synchronously reading search params in a client component if all dynamic access is inside a Suspense boundary
● Dynamic IO Errors - Without Minification › Sync Dynamic - With Fallback - client searchParams › should not error the build when synchronously reading search params in a client component if all dynamic access is inside a Suspense boundary
● Dynamic IO Errors - Without Minification › Sync Dynamic - Without Fallback - client searchParams › should error the build if dynamic IO happens in the root (outside a Suspense)
Read more about building and testing Next.js in contributing.md.
Expand output● persistent-caching › should persistent cache loaders
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 update/react/19.1.0-canary-42687267-20250108 | Change | |
---|---|---|---|
buildDuration | 19.1s | 16s | N/A |
buildDurationCached | 15.1s | 12.5s | N/A |
nodeModulesSize | 417 MB | 417 MB | ✓ |
nextStartRea..uration (ms) | 475ms | 477ms | N/A |
Client Bundles (main, webpack)
vercel/next.js canary | vercel/next.js update/react/19.1.0-canary-42687267-20250108 | Change | |
---|---|---|---|
1187-HASH.js gzip | 52.6 kB | 52.6 kB | N/A |
8276.HASH.js gzip | 169 B | 168 B | N/A |
8377-HASH.js gzip | 5.44 kB | 5.44 kB | N/A |
bccd1874-HASH.js gzip | 53 kB | 53 kB | N/A |
framework-HASH.js gzip | 57.5 kB | 57.5 kB | N/A |
main-app-HASH.js gzip | 232 B | 234 B | N/A |
main-HASH.js gzip | 34.1 kB | 34.1 kB | N/A |
webpack-HASH.js gzip | 1.71 kB | 1.71 kB | N/A |
Overall change | 0 B | 0 B | ✓ |
Legacy Client Bundles (polyfills)
vercel/next.js canary | vercel/next.js update/react/19.1.0-canary-42687267-20250108 | 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 update/react/19.1.0-canary-42687267-20250108 | 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.57 kB | 4.57 kB | N/A |
index-HASH.js gzip | 268 B | 268 B | ✓ |
link-HASH.js gzip | 2.35 kB | 2.34 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 update/react/19.1.0-canary-42687267-20250108 | Change | |
---|---|---|---|
_buildManifest.js gzip | 749 B | 747 B | N/A |
Overall change | 0 B | 0 B | ✓ |
Rendered Page Sizes
vercel/next.js canary | vercel/next.js update/react/19.1.0-canary-42687267-20250108 | Change | |
---|---|---|---|
index.html gzip | 524 B | 524 B | ✓ |
link.html gzip | 539 B | 538 B | N/A |
withRouter.html gzip | 520 B | 521 B | N/A |
Overall change | 524 B | 524 B | ✓ |
Edge SSR bundle Size
vercel/next.js canary | vercel/next.js update/react/19.1.0-canary-42687267-20250108 | Change | |
---|---|---|---|
edge-ssr.js gzip | 128 kB | 128 kB | N/A |
page.js gzip | 206 kB | 206 kB | N/A |
Overall change | 0 B | 0 B | ✓ |
Middleware size
vercel/next.js canary | vercel/next.js update/react/19.1.0-canary-42687267-20250108 | Change | |
---|---|---|---|
middleware-b..fest.js gzip | 667 B | 667 B | ✓ |
middleware-r..fest.js gzip | 155 B | 156 B | N/A |
middleware.js gzip | 31.2 kB | 31.2 kB | N/A |
edge-runtime..pack.js gzip | 844 B | 844 B | ✓ |
Overall change | 1.51 kB | 1.51 kB | ✓ |
Next Runtimes
vercel/next.js canary | vercel/next.js update/react/19.1.0-canary-42687267-20250108 | 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 | 364 kB | 364 kB | N/A |
app-page-exp..prod.js gzip | 129 kB | 129 kB | N/A |
app-page-tur..prod.js gzip | 142 kB | 142 kB | N/A |
app-page-tur..prod.js gzip | 138 kB | 138 kB | ✓ |
app-page.run...dev.js gzip | 352 kB | 352 kB | N/A |
app-page.run..prod.js gzip | 125 kB | 125 kB | N/A |
app-route-ex...dev.js gzip | 37.5 kB | 37.5 kB | ✓ |
app-route-ex..prod.js gzip | 25.6 kB | 25.6 kB | N/A |
app-route-tu..prod.js gzip | 25.6 kB | 25.6 kB | N/A |
app-route-tu..prod.js gzip | 25.4 kB | 25.4 kB | N/A |
app-route.ru...dev.js gzip | 39.2 kB | 39.2 kB | N/A |
app-route.ru..prod.js gzip | 25.4 kB | 25.4 kB | N/A |
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.7 kB | 21.7 kB | ✓ |
pages.runtim...dev.js gzip | 27.5 kB | 27.5 kB | ✓ |
pages.runtim..prod.js gzip | 21.7 kB | 21.7 kB | ✓ |
server.runti..prod.js gzip | 916 kB | 916 kB | N/A |
Overall change | 278 kB | 278 kB | ✓ |
build cache Overall increase ⚠️
vercel/next.js canary | vercel/next.js update/react/19.1.0-canary-42687267-20250108 | Change | |
---|---|---|---|
0.pack gzip | 2.08 MB | 2.09 MB | |
index.pack gzip | 76.1 kB | 74.6 kB | N/A |
Overall change | 2.08 MB | 2.09 MB |
Diff details
Diff for main-HASH.js
Diff too large to display
Diff for app-page-exp..ntime.dev.js
failed to diff
Diff for app-page-exp..time.prod.js
Diff too large to display
Diff for app-page.runtime.dev.js
failed to diff
Diff for app-page.runtime.prod.js
Diff too large to display
Diff for server.runtime.prod.js
failed to diff
diff facebook/[email protected]
React upstream changes