Use page static info collect from Turbopack when available#90516
Use page static info collect from Turbopack when available#90516mischnic wants to merge 5 commits intomischnic/cleanup-getPagesPageStaticInfofrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
bd24de0 to
8de4e5c
Compare
Merging this PR will not alter performance
Comparing Footnotes
|
Failing test suitesCommit: 4365394 | About building and testing Next.js
Expand output● Middleware can set the matcher in its config › does add the header for root request ● Middleware can set the matcher in its config › adds the header for a matched path ● Middleware can set the matcher in its config › adds the header for a matched data path (with header) ● Middleware can set the matcher in its config › adds the header for a matched data path (without header) ● Middleware can set the matcher in its config › adds the header for another matched path ● Middleware can set the matcher in its config › adds the header for another matched data path ● Middleware can set the matcher in its config › does add the header for root data request ● Middleware can set the matcher in its config › should load matches in client matchers correctly ● Middleware can set the matcher in its config › should navigate correctly with matchers ● using a single matcher › does not add the header for root request ● using a single matcher › does not add the header for root data request ● using a single matcher › adds the header for a matched path ● using a single matcher › adds the headers for a matched data path (with header) ● using a single matcher › adds the header for a matched data path (without header) ● using a single matcher › does not add the header for an unmatched path ● using root matcher › adds the header to the / ● using root matcher › adds the header to the /index ● using root matcher › adds the header for a matched data path (with header) ● using root matcher › adds the header for a matched data path (without header) ● using a single matcher with i18n › adds the header for a matched path ● using a single matcher with i18n › adds the header for a mathed root path with /index ● using a single matcher with i18n › adds the headers for a matched data path ● using a single matcher with i18n › does not add the header for an unmatched path ● using a single matcher with i18n and trailingSlash › adds the header for a matched path ● using a single matcher with i18n and trailingSlash › adds the header for a mathed root path with /index ● using a single matcher with i18n and trailingSlash › adds the headers for a matched data path ● using a single matcher with i18n and trailingSlash › does not add the header for an unmatched path ● using a single matcher with i18n and basePath › adds the header for a matched path ● using a single matcher with i18n and basePath › adds the header for a mathed root path with /index ● using a single matcher with i18n and basePath › adds the headers for a matched data path ● using a single matcher with i18n and basePath › does not add the header for an unmatched path ● using a single matcher with i18n and basePath and trailingSlash › adds the header for a matched path ● using a single matcher with i18n and basePath and trailingSlash › adds the header for a mathed root path with /index ● using a single matcher with i18n and basePath and trailingSlash › adds the headers for a matched data path ● using a single matcher with i18n and basePath and trailingSlash › does not add the header for an unmatched path ● Test suite failed to run ● Test suite failed to run ● Test suite failed to run ● Test suite failed to run ● Test suite failed to run ● Test suite failed to run ● Test suite failed to run
Expand output● app dir - middleware with custom matcher › should match /:id (without asterisk)
Expand output● app-dir-prefetch-non-iso-url › should go to iso url ● app-dir-prefetch-non-iso-url › should go to non-iso url ● Test suite failed to run
Expand output● proxy-typescript › should have built and started
Expand output● required server files app router › should send the right cache headers for an app route ● required server files app router › should handle optional catchall ● required server files app router › should send the right cache headers for an app page ● required server files app router › should not fail caching ● required server files app router › should properly handle prerender for bot request ● required server files app router › should properly handle fallback for bot request ● required server files app router › should send cache tags in minimal mode for ISR ● required server files app router › should not send cache tags in minimal mode for SSR ● required server files app router › should not send invalid soft tags to cache handler ● required server files app router › should not override params with query params ● required server files app router › should de-dupe HTML/RSC requests for ISR pages ● required server files app router › should isolate cache between different ISR request groups ● Test suite failed to run
Expand output● adapter-config export › should call onBuildComplete with correct context
Expand output● instrumentation pages › should start and serve correctly ● instrumentation app › should start and serve correctly
Expand output● opentelemetry › root context › app router › should handle RSC with fetch ● opentelemetry › root context › app router › should handle RSC with fetch ● opentelemetry › root context › app router › should propagate custom context without span ● opentelemetry › root context › app router › should propagate custom context without span ● opentelemetry › root context › app router › should handle RSC with fetch on edge ● opentelemetry › root context › app router › should handle RSC with fetch on edge ● opentelemetry › root context › app router › should handle RSC with fetch in RSC mode ● opentelemetry › root context › app router › should handle RSC with fetch in RSC mode ● opentelemetry › root context › app router › should handle route handlers in app router ● opentelemetry › root context › app router › should handle route handlers in app router ● opentelemetry › root context › app router › should handle route handlers in app router on edge ● opentelemetry › root context › app router › should handle route handlers in app router on edge ● opentelemetry › root context › app router › should trace middleware ● opentelemetry › root context › app router › should trace middleware ● opentelemetry › root context › app router › should handle error in RSC ● opentelemetry › root context › app router › should handle error in RSC ● opentelemetry › root context › app router › should handle error inside Suspense boundary ● opentelemetry › root context › app router › should handle error inside Suspense boundary ● opentelemetry › root context › pages › should handle getServerSideProps ● opentelemetry › root context › pages › should handle getServerSideProps ● opentelemetry › root context › pages › should handle getStaticProps when fallback: 'blocking' ● opentelemetry › root context › pages › should handle getStaticProps when fallback: 'blocking' ● opentelemetry › root context › pages › should handle getServerSideProps on edge ● opentelemetry › root context › pages › should handle getServerSideProps on edge ● opentelemetry › root context › pages › should handle getServerSideProps exceptions ● opentelemetry › root context › pages › should handle getServerSideProps exceptions ● opentelemetry › root context › pages › should handle getServerSideProps returning notFound ● opentelemetry › root context › pages › should handle getServerSideProps returning notFound ● opentelemetry › root context › pages › should handle api routes in pages ● opentelemetry › root context › pages › should handle api routes in pages ● opentelemetry › root context › pages › should handle api routes in pages on edge ● opentelemetry › root context › pages › should handle api routes in pages on edge ● opentelemetry › incoming context propagation › app router › should handle RSC with fetch ● opentelemetry › incoming context propagation › app router › should handle RSC with fetch ● opentelemetry › incoming context propagation › app router › should propagate custom context without span ● opentelemetry › incoming context propagation › app router › should propagate custom context without span ● opentelemetry › incoming context propagation › app router › should handle RSC with fetch on edge ● opentelemetry › incoming context propagation › app router › should handle RSC with fetch on edge ● opentelemetry › incoming context propagation › app router › should handle RSC with fetch in RSC mode ● opentelemetry › incoming context propagation › app router › should handle RSC with fetch in RSC mode ● opentelemetry › incoming context propagation › app router › should handle route handlers in app router ● opentelemetry › incoming context propagation › app router › should handle route handlers in app router ● opentelemetry › incoming context propagation › app router › should handle route handlers in app router on edge ● opentelemetry › incoming context propagation › app router › should handle route handlers in app router on edge ● opentelemetry › incoming context propagation › app router › should trace middleware ● opentelemetry › incoming context propagation › app router › should trace middleware ● opentelemetry › incoming context propagation › app router › should handle error in RSC ● opentelemetry › incoming context propagation › app router › should handle error in RSC ● opentelemetry › incoming context propagation › app router › should handle error inside Suspense boundary ● opentelemetry › incoming context propagation › app router › should handle error inside Suspense boundary ● opentelemetry › incoming context propagation › pages › should handle getServerSideProps ● opentelemetry › incoming context propagation › pages › should handle getServerSideProps ● opentelemetry › incoming context propagation › pages › should handle getStaticProps when fallback: 'blocking' ● opentelemetry › incoming context propagation › pages › should handle getStaticProps when fallback: 'blocking' ● opentelemetry › incoming context propagation › pages › should handle getServerSideProps on edge ● opentelemetry › incoming context propagation › pages › should handle getServerSideProps on edge ● opentelemetry › incoming context propagation › pages › should handle getServerSideProps exceptions ● opentelemetry › incoming context propagation › pages › should handle getServerSideProps exceptions ● opentelemetry › incoming context propagation › pages › should handle getServerSideProps returning notFound ● opentelemetry › incoming context propagation › pages › should handle getServerSideProps returning notFound ● opentelemetry › incoming context propagation › pages › should handle api routes in pages ● opentelemetry › incoming context propagation › pages › should handle api routes in pages ● opentelemetry › incoming context propagation › pages › should handle api routes in pages on edge ● opentelemetry › incoming context propagation › pages › should handle api routes in pages on edge ● opentelemetry with disabled fetch tracing › root context › app router with disabled fetch › should handle RSC with disabled fetch ● opentelemetry with disabled fetch tracing › root context › app router with disabled fetch › should handle RSC with disabled fetch ● opentelemetry with custom server › should set attributes correctly on handleRequest span ● opentelemetry with custom server › should set attributes correctly on handleRequest span ● opentelemetry with direct entrypoint handler › should propagate incoming context without next-server wrapper ● opentelemetry with direct entrypoint handler › should propagate incoming context without next-server wrapper
Expand output● Edge runtime code with imports › Edge API statically importing node.js module › throws unsupported module error in dev at runtime and highlights the faulty line ● Edge runtime code with imports › Edge API statically importing node.js module › production mode › throws unsupported module error in production at runtime and prints error on logs ● Edge runtime code with imports › Edge API dynamically importing 3rd party module › throws not-found module error in dev at runtime and highlights the faulty line ● Edge runtime code with imports › Edge API importing unused 3rd party module › throws not-found module error in dev at runtime and highlights the faulty line ● Edge runtime code with imports › Edge API importing unused node.js module › does not throw in dev at runtime ● Edge runtime code with imports › Edge API importing unused node.js module › production mode › does not throw in production at runtime
Expand output● Edge runtime code with imports › test error if response is not Response type › Edge API dev test Response ● Edge runtime code with imports › test error if response is not Response type › production mode › Edge API build test Response ● Edge runtime code with imports › test error if response is not Response type › Middleware dev test Response ● Edge runtime code with imports › test error if response is not Response type › production mode › Middleware build test Response
Expand output● Middleware custom matchers basePath › should match ● Middleware custom matchers basePath › should not match ● Middleware custom matchers basePath › should not match ● Middleware custom matchers basePath › should match query path
Expand output● specified tsconfig › app router: allows a user-specific tsconfig via the next config ● specified tsconfig › pages router: allows a user-specific tsconfig via the next config ● specified tsconfig › middleware: allows a user-specific tsconfig via the next config
Expand output● searchparams-reuse-loading › should re-use the prefetched loading state when navigating to a new searchParam value ● searchparams-reuse-loading › should properly render root page with searchParams when prefetch is aliased ● searchparams-reuse-loading › should reflect the correct searchParams when re-using the same page segment ● searchparams-reuse-loading › should reflect the correct searchParams when the root page is prefetched first ● searchparams-reuse-loading › when aliasing is skipped › should work for not found pages ● searchparams-reuse-loading › when aliasing is skipped › should work for route handlers ● searchparams-reuse-loading › when aliasing is skipped › should work for navigating to pages dir
Expand output● app-dir - middleware rewrite with catch-all and parallel routes › payment route › should rewrite to the specific page instead of the catch-all with parallel route ● app-dir - middleware rewrite with catch-all and parallel routes › payment route › should redirect to the specific page instead of the catch-all with parallel route ● app-dir - middleware rewrite with catch-all and parallel routes › anotherRoute › should rewrite to the specific page instead of the catch-all without parallel route ● app-dir - middleware rewrite with catch-all and parallel routes › anotherRoute › should redirect to the specific page instead of the catch-all without parallel route
Expand output● opentelemetry › root context › app router › should handle RSC with fetch ● opentelemetry › root context › app router › should handle RSC with fetch ● opentelemetry › root context › app router › should propagate custom context without span ● opentelemetry › root context › app router › should propagate custom context without span ● opentelemetry › root context › app router › should handle RSC with fetch on edge ● opentelemetry › root context › app router › should handle RSC with fetch on edge ● opentelemetry › root context › app router › should handle RSC with fetch in RSC mode ● opentelemetry › root context › app router › should handle RSC with fetch in RSC mode ● opentelemetry › root context › app router › should handle route handlers in app router ● opentelemetry › root context › app router › should handle route handlers in app router ● opentelemetry › root context › app router › should handle route handlers in app router on edge ● opentelemetry › root context › app router › should handle route handlers in app router on edge ● opentelemetry › root context › app router › should trace middleware ● opentelemetry › root context › app router › should trace middleware ● opentelemetry › root context › app router › should handle error in RSC ● opentelemetry › root context › app router › should handle error in RSC ● opentelemetry › root context › app router › should handle error inside Suspense boundary ● opentelemetry › root context › app router › should handle error inside Suspense boundary ● opentelemetry › root context › pages › should handle getServerSideProps ● opentelemetry › root context › pages › should handle getServerSideProps ● opentelemetry › root context › pages › should handle getStaticProps when fallback: 'blocking' ● opentelemetry › root context › pages › should handle getStaticProps when fallback: 'blocking' ● opentelemetry › root context › pages › should handle getServerSideProps on edge ● opentelemetry › root context › pages › should handle getServerSideProps on edge ● opentelemetry › root context › pages › should handle getServerSideProps exceptions ● opentelemetry › root context › pages › should handle getServerSideProps exceptions ● opentelemetry › root context › pages › should handle getServerSideProps returning notFound ● opentelemetry › root context › pages › should handle getServerSideProps returning notFound ● opentelemetry › root context › pages › should handle api routes in pages ● opentelemetry › root context › pages › should handle api routes in pages ● opentelemetry › root context › pages › should handle api routes in pages on edge ● opentelemetry › root context › pages › should handle api routes in pages on edge ● opentelemetry › incoming context propagation › app router › should handle RSC with fetch ● opentelemetry › incoming context propagation › app router › should handle RSC with fetch ● opentelemetry › incoming context propagation › app router › should propagate custom context without span ● opentelemetry › incoming context propagation › app router › should propagate custom context without span ● opentelemetry › incoming context propagation › app router › should handle RSC with fetch on edge ● opentelemetry › incoming context propagation › app router › should handle RSC with fetch on edge ● opentelemetry › incoming context propagation › app router › should handle RSC with fetch in RSC mode ● opentelemetry › incoming context propagation › app router › should handle RSC with fetch in RSC mode ● opentelemetry › incoming context propagation › app router › should handle route handlers in app router ● opentelemetry › incoming context propagation › app router › should handle route handlers in app router ● opentelemetry › incoming context propagation › app router › should handle route handlers in app router on edge ● opentelemetry › incoming context propagation › app router › should handle route handlers in app router on edge ● opentelemetry › incoming context propagation › app router › should trace middleware ● opentelemetry › incoming context propagation › app router › should trace middleware ● opentelemetry › incoming context propagation › app router › should handle error in RSC ● opentelemetry › incoming context propagation › app router › should handle error in RSC ● opentelemetry › incoming context propagation › app router › should handle error inside Suspense boundary ● opentelemetry › incoming context propagation › app router › should handle error inside Suspense boundary ● opentelemetry › incoming context propagation › pages › should handle getServerSideProps ● opentelemetry › incoming context propagation › pages › should handle getServerSideProps ● opentelemetry › incoming context propagation › pages › should handle getStaticProps when fallback: 'blocking' ● opentelemetry › incoming context propagation › pages › should handle getStaticProps when fallback: 'blocking' ● opentelemetry › incoming context propagation › pages › should handle getServerSideProps on edge ● opentelemetry › incoming context propagation › pages › should handle getServerSideProps on edge ● opentelemetry › incoming context propagation › pages › should handle getServerSideProps exceptions ● opentelemetry › incoming context propagation › pages › should handle getServerSideProps exceptions ● opentelemetry › incoming context propagation › pages › should handle getServerSideProps returning notFound ● opentelemetry › incoming context propagation › pages › should handle getServerSideProps returning notFound ● opentelemetry › incoming context propagation › pages › should handle api routes in pages ● opentelemetry › incoming context propagation › pages › should handle api routes in pages ● opentelemetry › incoming context propagation › pages › should handle api routes in pages on edge ● opentelemetry › incoming context propagation › pages › should handle api routes in pages on edge ● opentelemetry with disabled fetch tracing › root context › app router with disabled fetch › should handle RSC with disabled fetch ● opentelemetry with disabled fetch tracing › root context › app router with disabled fetch › should handle RSC with disabled fetch ● opentelemetry with custom server › should set attributes correctly on handleRequest span ● opentelemetry with custom server › should set attributes correctly on handleRequest span ● opentelemetry with direct entrypoint handler › should propagate incoming context without next-server wrapper ● opentelemetry with direct entrypoint handler › should propagate incoming context without next-server wrapper |
8de4e5c to
b805494
Compare
b7e8e55 to
94e2640
Compare
Stats from current PR✅ No significant changes detected📊 All Metrics📖 Metrics GlossaryDev Server Metrics:
Build Metrics:
Change Thresholds:
📦 Dev Server (Webpack) (Legacy)📦 Dev Server (Webpack)
📦 Production Builds (Webpack) (Legacy)📦 Production Builds (Webpack)
📦 Bundle SizesBundle Sizes📦 WebpackClient Main Bundles
Polyfills
Pages
Server Edge SSR
Middleware
Build DetailsBuild Manifests
Build Cache
🔄 Shared (bundler-independent)Runtimes
📎 Tarball URL |
94e2640 to
0147745
Compare
0147745 to
4ef5274
Compare
4ef5274 to
428dbd2
Compare
428dbd2 to
4365394
Compare
4365394 to
f276b49
Compare
390d303 to
6d3950c
Compare
5619b68 to
28f2a1d
Compare

Uh oh!
There was an error while loading. Please reload this page.