Conversation
779e853 to
88852b7
Compare
Failing test suitesCommit: 541e7b4 | About building and testing Next.js
Expand output● next/dynamic › production mode › should cancel slow page loads on re-navigation
Expand output● 500 Page Support › production mode › should use pages/500 ● 500 Page Support › production mode › should set correct status code with pages/500 ● 500 Page Support › production mode › should not error when visited directly ● 500 Page Support › production mode › should output 500.html during build ● 500 Page Support › production mode › should add /500 to pages-manifest correctly ● 500 Page Support › production mode 2 › should have correct cache control for 500 page with getStaticProps ● 500 Page Support › production mode 2 › does not build 500 statically with getInitialProps in _app ● 500 Page Support › production mode 2 › builds 500 statically by default with no pages/500 ● 500 Page Support › production mode 2 › builds 500 statically by default with no pages/500 and custom _error without getInitialProps ● 500 Page Support › production mode 2 › does not build 500 statically with no pages/500 and custom getInitialProps in _error ● 500 Page Support › production mode 2 › does not build 500 statically with no pages/500 and custom getInitialProps in _error and _app ● 500 Page Support › production mode 2 › shows error with getInitialProps in pages/500 build
Expand output● Fallback path encoding › production mode › should output paths correctly ● Fallback path encoding › production mode › should handle non-prerendered paths correctly ● Fallback path encoding › production mode › should respond with the prerendered pages correctly ● Fallback path encoding › production mode › should respond with the prerendered data correctly ● Fallback path encoding › production mode › should render correctly in the browser for prerender paths ● Fallback path encoding › production mode › should navigate client-side correctly with interpolating ● Fallback path encoding › production mode › should navigate client-side correctly with string href
Expand output● Trailing Slash Rewrite Proxying › production mode › should resolve index page correctly ● Trailing Slash Rewrite Proxying › production mode › should resolve products page correctly ● Trailing Slash Rewrite Proxying › production mode › should resolve a dynamic page correctly ● Trailing Slash Rewrite Proxying › production mode › should resolve a catch-all page correctly ● Trailing Slash Rewrite Proxying › production mode › should proxy non-existent page correctly
Expand output● Relay Compiler Transform - Multi Project Config › production mode › project-a › should resolve index page correctly ● Relay Compiler Transform - Multi Project Config › production mode › project-b › should resolve index page correctly
Expand output● Image Component Default Tests › production mode › should load the images ● Image Component Default Tests › production mode › should preload priority images ● Image Component Default Tests › production mode › should work with preload prop ● Image Component Default Tests › production mode › should not pass through user-provided srcset (causing a flash) ● Image Component Default Tests › production mode › should update the image on src change ● Image Component Default Tests › production mode › should callback onLoadingComplete when image is fully loaded ● Image Component Default Tests › production mode › should callback native onLoad with sythetic event ● Image Component Default Tests › production mode › should callback native onError when error occurred while loading image ● Image Component Default Tests › production mode › should callback native onError even when error before hydration ● Image Component Default Tests › production mode › should work with image with blob src ● Image Component Default Tests › production mode › should work when using flexbox ● Image Component Default Tests › production mode › should work when using overrideSrc prop ● Image Component Default Tests › production mode › should work with sizes and automatically use responsive srcset ● Image Component Default Tests › production mode › should render no wrappers or sizers ● Image Component Default Tests › production mode › should lazy load with placeholder=blur ● Image Component Default Tests › production mode › should handle the styles prop appropriately ● Image Component Default Tests › production mode › should warn when legacy prop layout=fill ● Image Component Default Tests › production mode › should warn when legacy prop layout=responsive ● Image Component Default Tests › production mode › should render picture via getImageProps ● Image Component Default Tests › production mode › should not create an image folder in server/chunks ● Image Component Default Tests › production mode › should render as unoptimized with missing src prop ● Image Component Default Tests › production mode › should render as unoptimized with empty string src prop ● Image Component Default Tests › production mode › should correctly ignore prose styles ● Image Component Default Tests › production mode › should apply style inheritance for img elements but not wrapper elements ● Image Component Default Tests › production mode › should apply filter style after image loads ● Image Component Default Tests › production mode › should emit image for next/dynamic with non ssr case ● Image Component Default Tests › production mode › Fill-mode tests › should include a data-attribute on fill images ● Image Component Default Tests › production mode › Fill-mode tests › should include a data-attribute on fill images ● Image Component Default Tests › production mode › Fill-mode tests › should add position:absolute to fill images ● Image Component Default Tests › production mode › Fill-mode tests › should add position:absolute to fill images ● Image Component Default Tests › production mode › Fill-mode tests › should add 100% width and height to fill images ● Image Component Default Tests › production mode › Fill-mode tests › should add 100% width and height to fill images ● Image Component Default Tests › production mode › Fill-mode tests › should add position styles to fill images ● Image Component Default Tests › production mode › Fill-mode tests › should add position styles to fill images ● Image Component Default Tests › production mode › should correctly rotate image ● Image Component Default Tests › production mode › should create images folder in static/media for edge runtime ● Image Component Default Tests › production mode › should have data url placeholder when enabled ● Image Component Default Tests › production mode › should remove data url placeholder after image loads ● Image Component Default Tests › production mode › should render correct objectFit when data url placeholder and fill ● Image Component Default Tests › production mode › should have blurry placeholder when enabled ● Image Component Default Tests › production mode › should remove blurry placeholder after image loads ● Image Component Default Tests › production mode › should render correct objectFit when blurDataURL and fill ● Image Component Default Tests › production mode › should be valid HTML
Expand output● Export with cloudinary loader next/legacy/image component › production mode › should build successfully ● Export with cloudinary loader next/legacy/image component › production mode › should contain img element in html output ● Export with custom loader next/legacy/image component › production mode › should build successfully ● Export with custom loader next/legacy/image component › production mode › should contain img element with same src in html output ● Export with custom loader config but no loader prop on next/legacy/image › production mode › should fail build ● Export with unoptimized next/legacy/image component › production mode › should build successfully ● Export with unoptimized next/legacy/image component › production mode › should contain img element with same src in html output
Expand output● Application Export Intent Output › production mode › Default Export › should build and export ● Application Export Intent Output › production mode › Default Export › should have the expected outputs for export ● Application Export Intent Output › Custom Export › production mode › should build and export ● Application Export Intent Output › Custom Export › production mode › should have the expected outputs for export ● Application Export Intent Output › Custom Out › production mode › should build and export ● Application Export Intent Output › Custom Out › production mode › should have the expected outputs for export ● Application Export Intent Output › Bad Export › production mode › should build and export ● Application Export Intent Output › Bad Export › production mode › should have the expected outputs for export ● Application Export Intent Output › No Export › production mode › should build and not export ● Application Export Intent Output › No Export › production mode › should have the expected outputs for export ● Application Export Intent Output › No Export › production mode › should build and clean up
Expand output● Basic CSS Module Support › production mode › should have compiled successfully ● Basic CSS Module Support › production mode › should've emitted a single CSS file ● Basic CSS Module Support › production mode › should've injected the CSS on server render ● 3rd Party CSS Module Support › production mode › should have compiled successfully ● 3rd Party CSS Module Support › production mode › should've emitted a single CSS file ● 3rd Party CSS Module Support › production mode › should've injected the CSS on server render ● Has CSS Module in computed styles in Production › production mode › should have compiled successfully ● Has CSS Module in computed styles in Production › production mode › should have CSS for page ● Valid CSS Module Usage from within node_modules › production mode › should have compiled successfully ● Valid CSS Module Usage from within node_modules › production mode › should've prerendered with relevant data ● Valid CSS Module Usage from within node_modules › production mode › should've emitted a single CSS file ● CSS Module Composes Usage (Basic) › production mode › should have compiled successfully ● CSS Module Composes Usage (Basic) › production mode › should've emitted a single CSS file ● Dynamic Route CSS Module Usage › production mode › should have compiled successfully ● Dynamic Route CSS Module Usage › production mode › should apply styles correctly ● Dynamic Route CSS Module Usage › production mode › should've emitted a single CSS file ● Catch-all Route CSS Module Usage › production mode › should have compiled successfully ● Catch-all Route CSS Module Usage › production mode › should apply styles correctly ● Catch-all Route CSS Module Usage › production mode › should've emitted a single CSS file ● cssmodules-pure-no-check usage › should have compiled successfully ● cssmodules-pure-no-check usage › should apply styles correctly ● cssmodules-pure-no-check usage › should've emitted a CSS file
Expand output● next-image-legacy-src-with-query-without-local-patterns › should throw error for relative image with query without localPatterns for legacy Image
Expand output● New Link Behavior with child › should throw error with child ● Test suite failed to run ● Test suite failed to run
Expand output● i18n: Event with stale state - static route previously was dynamic › Ignore event without query param ● i18n: Event with stale state - static route previously was dynamic › Ignore event with query param ● i18n: Event with stale state - static route previously was dynamic › Don't ignore event with different locale ● Test suite failed to run ● Test suite failed to run
Expand output● should handle unresolved files gracefully › production mode › should build correctly ● should handle unresolved files gracefully › production mode › should have correct file references in CSS output ● Data URLs › production mode › should compile successfully ● Data URLs › production mode › should have emitted expected files ● Ordering with Global CSS and Modules (prod) › production mode › useLightnincsss(true) › should have compiled successfully ● Ordering with Global CSS and Modules (prod) › production mode › useLightnincsss(true) › should have the correct color (css ordering) ● Ordering with Global CSS and Modules (prod) › production mode › useLightnincsss(false) › should have compiled successfully ● Ordering with Global CSS and Modules (prod) › production mode › useLightnincsss(false) › should have the correct color (css ordering)
Expand output● edge-render-getserversideprops › should not output trace files for edge routes ● edge-render-getserversideprops › should have correct query for pages/api ● edge-render-getserversideprops › should have correct query for pages/api dynamic ● edge-render-getserversideprops › should have correct query/params on index ● edge-render-getserversideprops › should have correct query/params on /[id] ● edge-render-getserversideprops › should have correct query/params on rewrite ● edge-render-getserversideprops › should have correct query/params on dynamic rewrite ● edge-render-getserversideprops › should respond to _next/data for index correctly ● edge-render-getserversideprops › should respond to _next/data for [id] correctly ● edge-render-getserversideprops › should have data routes in routes-manifest ● Test suite failed to run
Expand output● next-image-src-with-query-without-local-patterns › should throw error for relative image with query without localPatterns |
Merging this PR will not alter performance
Comparing Footnotes
|
Stats from current PR✅ No significant changes detected📊 All Metrics📖 Metrics GlossaryDev Server Metrics:
Build Metrics:
Change Thresholds:
⚡ Dev Server
📦 Dev Server (Webpack) (Legacy)📦 Dev Server (Webpack)
⚡ Production Builds
📦 Production Builds (Webpack) (Legacy)📦 Production Builds (Webpack)
📦 Bundle SizesBundle Sizes⚡ TurbopackClient Main Bundles: **399 kB** → **399 kB** ✅ -8 B80 files with content-based hashes (individual files not comparable between builds) Server Middleware
Build DetailsBuild Manifests
📦 WebpackClient Main Bundles
Polyfills
Pages
Server Edge SSR
Middleware
Build DetailsBuild Manifests
Build Cache
🔄 Shared (bundler-independent)Runtimes
|
b9c6bd2 to
541e7b4
Compare
In dev validation, we're disassembling a payload from a dynamic render.
If the request had search params, page segments in the router state will
have them attached: `__PAGE__?{"q":"123"}`. In
`findNavigationsToValidate`, we do the equivalent of constructing a
flightRouterState, so we need to match that, otherwise we'll name the
segment `__PAGE__` instead and then can't look it up in the cache, and
crash during validation.
541e7b4 to
4d25156
Compare

No description provided.