diff --git a/test/rspack-dev-tests-manifest.json b/test/rspack-dev-tests-manifest.json index 0c6bdf8c127355..0e38444d786e8e 100644 --- a/test/rspack-dev-tests-manifest.json +++ b/test/rspack-dev-tests-manifest.json @@ -1168,7 +1168,10 @@ "loadConfig nextConfig.images defaults should assign a `images.remotePatterns` when using assetPrefix", "loadConfig nextConfig.images defaults should not assign a duplicate `images.remotePatterns` value when using assetPrefix", "loadConfig with a canary version errors when cacheComponents is enabled but PPR is disabled", - "loadConfig with a canary version errors when cacheComponents is enabled but PPR set to \"incremental\"" + "loadConfig with a canary version errors when cacheComponents is enabled but PPR set to \"incremental\"", + "loadConfig with a canary version migrates experimental.dynamicIO to experimental.cacheComponents", + "loadConfig with a canary version preserves cacheComponents when both dynamicIO and cacheComponents are set", + "loadConfig with a canary version warns when using deprecated experimental.dynamicIO" ], "failed": [], "pending": [], @@ -1881,6 +1884,69 @@ "flakey": [], "runtimeError": false }, + "packages/next/src/shared/lib/router/utils/sortable-routes.test.ts": { + "passed": [ + "compareRouteSegments should handle complete specificity hierarchy", + "compareRouteSegments should handle complex nested comparisons", + "compareRouteSegments should handle empty paths", + "compareRouteSegments should handle identical routes", + "compareRouteSegments should handle mixed depths with different specificities", + "compareRouteSegments should handle paths with leading/trailing slashes consistently", + "compareRouteSegments should handle root path", + "compareRouteSegments should prioritize catch-all over optional catch-all segments", + "compareRouteSegments should prioritize dynamic over catch-all segments", + "compareRouteSegments should prioritize shorter routes", + "compareRouteSegments should prioritize static over dynamic segments", + "compareRouteSegments should sort lexicographically when specificity is equal", + "getSegmentSpecificity should handle edge cases", + "getSegmentSpecificity should handle segments with brackets but not dynamic routes", + "getSegmentSpecificity should return 0 for static segments", + "getSegmentSpecificity should return 1 for dynamic segments", + "getSegmentSpecificity should return 2 for catch-all segments", + "getSegmentSpecificity should return 3 for optional catch-all segments", + "sortPageObjects should handle duplicate pages correctly (bug fix)", + "sortPageObjects should handle empty array", + "sortPageObjects should handle many duplicate routes efficiently", + "sortPageObjects should handle mixed route depths", + "sortPageObjects should handle single object", + "sortPageObjects should maintain original order for identical routes (stable sort)", + "sortPageObjects should not mutate the input array", + "sortPageObjects should sort lexicographically when specificity is equal", + "sortPageObjects should sort pages by specificity", + "sortPages should handle complex nested routes", + "sortPages should handle duplicate pages", + "sortPages should handle empty array", + "sortPages should handle mixed route depths", + "sortPages should handle single page", + "sortPages should not mutate the input array", + "sortPages should sort lexicographically when specificity is equal", + "sortPages should sort pages by specificity", + "sortSortableRouteObjects should handle complex route specificity ordering", + "sortSortableRouteObjects should handle duplicate route patterns with different objects", + "sortSortableRouteObjects should handle empty array", + "sortSortableRouteObjects should handle mixed route depths correctly", + "sortSortableRouteObjects should handle objects with different source and page paths", + "sortSortableRouteObjects should handle single object", + "sortSortableRouteObjects should not mutate the input array", + "sortSortableRouteObjects should sort by sourcePage first, then page as tiebreaker", + "sortSortableRouteObjects should sort lexicographically when all other factors are equal", + "sortSortableRouteObjects should sort objects by sourcePage and page while preserving object references", + "sortSortableRouteObjects should work with getter function that creates new objects each time", + "sortSortableRoutes should handle complex nested routes with different parameter types", + "sortSortableRoutes should handle empty routes array", + "sortSortableRoutes should handle identical routes", + "sortSortableRoutes should handle mixed route lengths correctly", + "sortSortableRoutes should handle single route", + "sortSortableRoutes should prioritize source over page in sorting", + "sortSortableRoutes should sort lexicographically when specificity is equal", + "sortSortableRoutes should sort routes by page", + "sortSortableRoutes should sort routes by specificity with different parameter types" + ], + "failed": [], + "pending": [], + "flakey": [], + "runtimeError": false + }, "packages/next/src/shared/lib/server-reference-info.test.ts": { "passed": [ "extractInfoFromServerReferenceId should parse id with typeBit 0, argMask 0b101010, restArgs false", @@ -2481,6 +2547,51 @@ "flakey": [], "runtimeError": false }, + "test/development/app-dir/cache-components-dev-cache-scope/cache-components-dev-cache-scope.test.ts": { + "passed": [ + "Cache Components Dev Errors should not show a red box error on the SSR render", + "Cache Components Dev Errors should show a red box error on the SSR render when data is uncached" + ], + "failed": [], + "pending": [], + "flakey": [], + "runtimeError": false + }, + "test/development/app-dir/cache-components-dev-errors/cache-components-dev-errors.test.ts": { + "passed": [ + "Cache Components Dev Errors should display error when component accessed data without suspense boundary", + "Cache Components Dev Errors should not log unhandled rejections for persistently thrown top-level errors", + "Cache Components Dev Errors should show a red box error on client navigations", + "Cache Components Dev Errors should show a red box error on the SSR render" + ], + "failed": [ + "Cache Components Dev Errors should clear segment errors after correcting them" + ], + "pending": [], + "flakey": [], + "runtimeError": false + }, + "test/development/app-dir/cache-components-dev-warmup/cache-components.dev-warmup.test.ts": { + "passed": [ + "cache-components-dev-warmup logs with Prerender or Server environment depending based on whether the timing of when the log runs relative to this environment boundary" + ], + "failed": [], + "pending": [], + "flakey": [], + "runtimeError": false + }, + "test/development/app-dir/cache-components-warnings/cache-components.warnings.test.ts": { + "passed": [], + "failed": [], + "pending": [ + "dynamic-requests warnings warns on reading the current time in the prerender portion of a dev render", + "dynamic-requests warnings warns on reading the random numbers in the prerender portion of a dev render", + "dynamic-requests warnings warns on reading the random values from node crypto APIs in the prerender portion of a dev render", + "dynamic-requests warnings warns on reading the random values from web crypto APIs in the prerender portion of a dev render" + ], + "flakey": [], + "runtimeError": false + }, "test/development/app-dir/capture-console-error-owner-stack/capture-console-error-owner-stack.test.ts": { "passed": [ "app-dir - capture-console-error-owner-stack should be able to capture rsc logged error", @@ -2542,51 +2653,6 @@ "flakey": [], "runtimeError": false }, - "test/development/app-dir/cache-components-dev-cache-scope/cache-components-dev-cache-scope.test.ts": { - "passed": [ - "Cache Components Dev Errors should not show a red box error on the SSR render", - "Cache Components Dev Errors should show a red box error on the SSR render when data is uncached" - ], - "failed": [], - "pending": [], - "flakey": [], - "runtimeError": false - }, - "test/development/app-dir/cache-components-dev-errors/cache-components-dev-errors.test.ts": { - "passed": [ - "Cache Components Dev Errors should display error when component accessed data without suspense boundary", - "Cache Components Dev Errors should not log unhandled rejections for persistently thrown top-level errors", - "Cache Components Dev Errors should show a red box error on client navigations", - "Cache Components Dev Errors should show a red box error on the SSR render" - ], - "failed": [ - "Cache Components Dev Errors should clear segment errors after correcting them" - ], - "pending": [], - "flakey": [], - "runtimeError": false - }, - "test/development/app-dir/cache-components-dev-warmup/cache-components.dev-warmup.test.ts": { - "passed": [ - "cache-components-dev-warmup logs with Prerender or Server environment depending based on whether the timing of when the log runs relative to this environment boundary" - ], - "failed": [], - "pending": [], - "flakey": [], - "runtimeError": false - }, - "test/development/app-dir/cache-components-warnings/cache-components.warnings.test.ts": { - "passed": [], - "failed": [], - "pending": [ - "dynamic-requests warnings warns on reading the current time in the prerender portion of a dev render", - "dynamic-requests warnings warns on reading the random numbers in the prerender portion of a dev render", - "dynamic-requests warnings warns on reading the random values from node crypto APIs in the prerender portion of a dev render", - "dynamic-requests warnings warns on reading the random values from web crypto APIs in the prerender portion of a dev render" - ], - "flakey": [], - "runtimeError": false - }, "test/development/app-dir/edge-errors-hmr/index.test.ts": { "passed": [ "develop - app-dir - edge errros hmr should recover from build errors when client component error", @@ -3019,10 +3085,10 @@ "runtimeError": false }, "test/development/basic/barrel-optimization/barrel-optimization-mui.test.ts": { - "passed": [], - "failed": [ + "passed": [ "Skipped in Turbopack optimizePackageImports - mui should support MUI" ], + "failed": [], "pending": [], "flakey": [], "runtimeError": false @@ -5668,776 +5734,776 @@ "flakey": [], "runtimeError": false }, - "test/e2e/app-dir/catchall-parallel-routes-group/catchall-parallel-routes-group.test.ts": { + "test/e2e/app-dir/cache-components-dynamic-imports/cache-components-dynamic-imports.test.ts": { "passed": [ - "catchall-parallel-routes-group should work without throwing any errors about invalid pages" + "async imports in cacheComponents - external packages does not instrument import() in external packages", + "async imports in cacheComponents are not instrumented in edge edge route handler", + "async imports in cacheComponents are not instrumented in edge middleware", + "async imports in cacheComponents inside a GET route handler import of a sync module", + "async imports in cacheComponents inside a GET route handler import of module with top-level-await", + "async imports in cacheComponents inside a client component import of a sync module", + "async imports in cacheComponents inside a client component import of module with top-level-await", + "async imports in cacheComponents inside a server component dynamic import in node_modules in a CJS package import of a sync module", + "async imports in cacheComponents inside a server component dynamic import in node_modules in an ESM package import of a sync module", + "async imports in cacheComponents inside a server component dynamic import in node_modules in an ESM package import of module with top-level-await", + "async imports in cacheComponents inside a server component import of a sync module", + "async imports in cacheComponents inside a server component import of module with top-level-await", + "async imports in cacheComponents outside of render client import of a sync module", + "async imports in cacheComponents outside of render client import of module with top-level-await", + "async imports in cacheComponents outside of render server import of a sync module", + "async imports in cacheComponents outside of render server import of module with top-level-await" ], "failed": [], "pending": [], "flakey": [], "runtimeError": false }, - "test/e2e/app-dir/catchall-specificity/catchall-specificity.test.ts": { - "passed": [ - "catchall-specificity should match the generic catchall correctly", - "catchall-specificity should match the specific catchall correctly" - ], + "test/e2e/app-dir/cache-components-errors/cache-components-errors.module-scope.test.ts": { + "passed": ["Lazy Module Init does not run in dev"], "failed": [], "pending": [], "flakey": [], "runtimeError": false }, - "test/e2e/app-dir/client-module-with-package-type/index.test.ts": { + "test/e2e/app-dir/cache-components-errors/cache-components-errors.prospective-errors.test.ts": { "passed": [ - "esm-client-module-without-exports \"type\": \"commonjs\" in package.json should render without errors: import cjs", - "esm-client-module-without-exports \"type\": \"commonjs\" in package.json should render without errors: require cjs", - "esm-client-module-without-exports \"type\": \"module\" in package.json should render without errors: import esm", - "esm-client-module-without-exports \"type\": \"module\" in package.json should render without errors: require esm" + "Cache Components Prospective Render Errors - Debug Build should error on the first visit to each page", + "Cache Components Prospective Render Errors - Standard Build should error on the first visit to each page" ], "failed": [], "pending": [], "flakey": [], "runtimeError": false }, - "test/e2e/app-dir/conflicting-page-segments/conflicting-page-segments.test.ts": { + "test/e2e/app-dir/cache-components-errors/cache-components-errors.test.ts": { "passed": [ - "conflicting-page-segments should throw an error when a route groups causes a conflict with a parallel segment" + "Cache Components Errors Dev Dynamic Boundary should not show a collapsed redbox error", + "Cache Components Errors Dev Dynamic Metadata - Dynamic Route should not show a collapsed redbox error", + "Cache Components Errors Dev Dynamic Metadata - Error Route should show a collapsed redbox error", + "Cache Components Errors Dev Dynamic Metadata - Static Route With Suspense should show a collapsed redbox error", + "Cache Components Errors Dev Dynamic Metadata - Static Route should show a collapsed redbox error", + "Cache Components Errors Dev Dynamic Root should show a collapsed redbox with two errors", + "Cache Components Errors Dev Dynamic Viewport - Dynamic Route should show a collapsed redbox error", + "Cache Components Errors Dev Dynamic Viewport - Static Route should show a collapsed redbox error", + "Cache Components Errors Dev Error Attribution with Sync IO Guarded RSC with guarded Client sync IO does not show a validation error in the dev overlay", + "Cache Components Errors Dev Error Attribution with Sync IO Guarded RSC with unguarded Client sync IO should show a collapsed redbox error", + "Cache Components Errors Dev Error Attribution with Sync IO Unguarded RSC with guarded Client sync IO should show a collapsed redbox error", + "Cache Components Errors Dev Error Attribution with Sync IO unguarded RSC with unguarded Client sync IO should show a collapsed redbox error", + "Cache Components Errors Dev Inside `use cache` cookies should show a redbox error", + "Cache Components Errors Dev Inside `use cache` draftMode should show a redbox error", + "Cache Components Errors Dev Inside `use cache` headers should show a redbox error", + "Cache Components Errors Dev Static Route should not show a collapsed redbox error", + "Cache Components Errors Dev Sync Dynamic Platform With Fallback - Math.random() should not show a collapsed redbox error", + "Cache Components Errors Dev Sync Dynamic Platform Without Fallback - Math.random() should show a collapsed redbox error", + "Cache Components Errors Dev Sync Dynamic Request client params should return `undefined` for `params.slug`", + "Cache Components Errors Dev Sync Dynamic Request client params should show a collapsed redbox with a sync access error", + "Cache Components Errors Dev Sync Dynamic Request client searchParams should return `undefined` for `searchParams.foo`", + "Cache Components Errors Dev Sync Dynamic Request client searchParams should show a collapsed redbox with a sync access error", + "Cache Components Errors Dev Sync Dynamic Request draftMode should return `undefined` for `draftMode().isEnabled`", + "Cache Components Errors Dev Sync Dynamic Request server params should return `undefined` for `params.slug`", + "Cache Components Errors Dev Sync Dynamic Request server params should show a collapsed redbox with a sync access error", + "Cache Components Errors Dev Sync Dynamic Request server searchParams should return `undefined` for `searchParams.foo`", + "Cache Components Errors Dev Sync Dynamic Request server searchParams should show a collapsed redbox with a sync access error" + ], + "failed": [ + "Cache Components Errors Dev Sync Dynamic Request cookies should show a redbox with a sync access error and a runtime error", + "Cache Components Errors Dev Sync Dynamic Request draftMode should show a collapsed redbox with a sync access error", + "Cache Components Errors Dev Sync Dynamic Request headers should show a redbox with a sync access error and a runtime error" ], - "failed": [], "pending": [], "flakey": [], "runtimeError": false }, - "test/e2e/app-dir/conflicting-search-and-route-params/conflicting-search-and-route-params.test.ts": { + "test/e2e/app-dir/cache-components-request-apis/cache-components-request-apis.test.ts": { "passed": [ - "conflicting-search-and-route-params should handle conflicting search and route params on API route", - "conflicting-search-and-route-params should handle conflicting search and route params on page" + "Request Promises On Prerender Completion does not run in dev", + "Request Promises On Prerender Interruption does not run in dev" ], "failed": [], "pending": [], "flakey": [], "runtimeError": false }, - "test/e2e/app-dir/create-root-layout/create-root-layout.test.ts": { - "passed": [ - "app-dir create root layout page.js find available dir create root layout", - "app-dir create root layout page.js root layout in app create root layout", - "app-dir create root layout page.js root layout in route group create root layout", - "app-dir create root layout page.tsx create root layout" + "test/e2e/app-dir/cache-components-segment-configs/cache-components-segment-configs.test.ts": { + "passed": [], + "failed": [ + "cache-components-segment-configs it should error when using segment configs that aren't supported by cacheComponents", + "cache-components-segment-configs should propagate configurations from layouts to pages" ], - "failed": [], "pending": [], "flakey": [], "runtimeError": false }, - "test/e2e/app-dir/crypto-globally-available/crypto-globally-available.test.ts": { + "test/e2e/app-dir/cache-components/cache-components.connection.test.ts": { "passed": [ - "Web Crypto API is available globally should be available in Route Handlers", - "Web Crypto API is available globally should be available in Server Components" + "cache-components should be able to pass connection as a promise to another component and trigger an intermediate Suspense boundary", + "cache-components should partially prerender pages that use connection" ], "failed": [], "pending": [], "flakey": [], "runtimeError": false }, - "test/e2e/app-dir/css-chunking/css-chunking.test.ts": { + "test/e2e/app-dir/cache-components/cache-components.console.test.ts": { "passed": [ - "css-chunking should be possible to disable the chunking plugin" + "cache-components dims console calls during prospective rendering" ], "failed": [], "pending": [], "flakey": [], "runtimeError": false }, - "test/e2e/app-dir/css-client-side-nav-parallel-routes/css-client-side-nav-parallel-routes.test.ts": { + "test/e2e/app-dir/cache-components/cache-components.cookies.test.ts": { "passed": [ - "css-client-side-nav-parallel-routes should apply styles after navigation" + "cache-components should be able to access cookie properties", + "cache-components should be able to pass cookies as a promise to another component and trigger an intermediate Suspense boundary", + "cache-components should partially prerender pages that use cookies" ], "failed": [], "pending": [], "flakey": [], "runtimeError": false }, - "test/e2e/app-dir/css-modules-data-urls/css-modules-data-urls.test.ts": { - "passed": [], - "failed": [], - "pending": [ - "css-modules-data-urls should apply client class name from data url correctly", - "css-modules-data-urls should apply client styles from data url correctly", - "css-modules-data-urls should apply rsc class name from data url correctly", - "css-modules-data-urls should apply rsc styles from data url correctly" + "test/e2e/app-dir/cache-components/cache-components.date.test.ts": { + "passed": [ + "cache-components should not have route specific errors", + "cache-components should not prerender pages with uncached `Date()` calls", + "cache-components should not prerender pages with uncached `Date.now()` calls", + "cache-components should not prerender pages with uncached `new Date()` calls", + "cache-components should not prerender pages with uncached static Date instances like `new Date(0)`", + "cache-components should prerender pages with cached `Date()` calls", + "cache-components should prerender pages with cached `Date.now()` calls", + "cache-components should prerender pages with cached `new Date()` calls", + "cache-components should prerender pages with cached static Date instances like `new Date(0)`" ], + "failed": [], + "pending": [], "flakey": [], "runtimeError": false }, - "test/e2e/app-dir/css-modules-pure-no-check/css-modules-pure-no-check.test.ts": { - "passed": ["css-modules-pure-no-check should apply styles correctly"], + "test/e2e/app-dir/cache-components/cache-components.draft-mode.test.ts": { + "passed": [ + "cache-components should fully prerender pages that use draftMode" + ], "failed": [], "pending": [], "flakey": [], "runtimeError": false }, - "test/e2e/app-dir/css-modules-scoping/css-modules-scoping.test.ts": { + "test/e2e/app-dir/cache-components/cache-components.headers.test.ts": { "passed": [ - "css-modules-scoping should not prefix grid areas", - "css-modules-scoping should prefix animation" + "cache-components should be able to access headers properties asynchronously", + "cache-components should be able to pass headers as a promise to another component and trigger an intermediate Suspense boundary", + "cache-components should partially prerender pages that use headers" ], "failed": [], "pending": [], "flakey": [], "runtimeError": false }, - "test/e2e/app-dir/css-order/css-order.test.ts": { + "test/e2e/app-dir/cache-components/cache-components.node-crypto.test.ts": { "passed": [ - "css-order loose should load correct styles navigating first -> first-client", - "css-order loose should load correct styles navigating first -> second", - "css-order loose should load correct styles navigating first -> second-client", - "css-order loose should load correct styles navigating first -> third", - "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 -> second-client", - "css-order loose should load correct styles navigating first-client -> third", - "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 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 second -> first", - "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 second -> third", - "css-order loose should load correct styles navigating second-client -> first", - "css-order loose should load correct styles navigating second-client -> first-client", - "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 third -> first", - "css-order loose should load correct styles navigating third -> first-client", - "css-order loose should load correct styles navigating third -> second", - "css-order loose should load correct styles navigating third -> second-client", - "css-order loose should load correct styles on big-interleaved-a", - "css-order loose should load correct styles on big-interleaved-b", - "css-order loose should load correct styles on first", - "css-order loose should load correct styles on first-client", - "css-order loose should load correct styles on interleaved-a", - "css-order loose should load correct styles on interleaved-b", - "css-order loose should load correct styles on pages-first", - "css-order loose should load correct styles on pages-interleaved-a", - "css-order loose should load correct styles on pages-interleaved-b", - "css-order loose should load correct styles on pages-partial-reversed-a", - "css-order loose should load correct styles on pages-partial-reversed-b", - "css-order loose should load correct styles on pages-reversed-a", - "css-order loose should load correct styles on pages-reversed-b", - "css-order loose should load correct styles on pages-second", - "css-order loose should load correct styles on pages-third", - "css-order loose should load correct styles on second", - "css-order loose should load correct styles on second-client", - "css-order loose should load correct styles on third", - "css-order loose should load correct styles on vendor", - "css-order strict should load correct styles navigating first -> first-client", - "css-order strict should load correct styles navigating first -> second", - "css-order strict should load correct styles navigating first -> second-client", - "css-order strict should load correct styles navigating first -> third", - "css-order strict should load correct styles navigating first-client -> first", - "css-order strict should load correct styles navigating first-client -> second", - "css-order strict should load correct styles navigating first-client -> second-client", - "css-order strict should load correct styles navigating first-client -> third", - "css-order strict should load correct styles navigating interleaved-a -> interleaved-b", - "css-order strict should load correct styles navigating interleaved-b -> interleaved-a", - "css-order strict should load correct styles navigating pages-first -> pages-second", - "css-order strict should load correct styles navigating pages-first -> pages-third", - "css-order strict should load correct styles navigating pages-second -> pages-first", - "css-order strict should load correct styles navigating pages-second -> pages-third", - "css-order strict should load correct styles navigating pages-third -> pages-first", - "css-order strict should load correct styles navigating pages-third -> pages-second", - "css-order strict should load correct styles navigating second -> first", - "css-order strict should load correct styles navigating second -> first-client", - "css-order strict should load correct styles navigating second -> second-client", - "css-order strict should load correct styles navigating second -> third", - "css-order strict should load correct styles navigating second-client -> first", - "css-order strict should load correct styles navigating second-client -> first-client", - "css-order strict should load correct styles navigating second-client -> second", - "css-order strict should load correct styles navigating second-client -> third", - "css-order strict should load correct styles navigating third -> first", - "css-order strict should load correct styles navigating third -> first-client", - "css-order strict should load correct styles navigating third -> second", - "css-order strict should load correct styles navigating third -> second-client", - "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 first", - "css-order strict should load correct styles on first-client", - "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 interleaved-a", - "css-order strict should load correct styles on interleaved-b", - "css-order strict should load correct styles on pages-first", - "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-partial-reversed-a", - "css-order strict should load correct styles on pages-partial-reversed-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-second", - "css-order strict should load correct styles on pages-third", - "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 reversed-a", - "css-order strict should load correct styles on reversed-b", - "css-order strict should load correct styles on second", - "css-order strict should load correct styles on second-client", - "css-order strict should load correct styles on third", - "css-order strict should load correct styles on vendor" + "cache-components should not have route specific errors", + "cache-components should not prerender pages with uncached `require('node:crypto').generateKeyPairSync(type, options)` calls", + "cache-components should not prerender pages with uncached `require('node:crypto').generateKeySync(type, options)` calls", + "cache-components should not prerender pages with uncached `require('node:crypto').generatePrimeSync(size, options)` calls", + "cache-components should not prerender pages with uncached `require('node:crypto').getRandomValues(...)` calls", + "cache-components should not prerender pages with uncached `require('node:crypto').randomBytes(size)` calls", + "cache-components should not prerender pages with uncached `require('node:crypto').randomFillSync(buffer)` calls", + "cache-components should not prerender pages with uncached `require('node:crypto').randomInt(max)` calls", + "cache-components should not prerender pages with uncached `require('node:crypto').randomInt(min, max)` calls", + "cache-components should not prerender pages with uncached `require('node:crypto').randomUUID()` calls", + "cache-components should prerender pages with cached `require('node:crypto').generateKeyPairSync(type, options)` calls", + "cache-components should prerender pages with cached `require('node:crypto').generateKeySync(type, options)` calls", + "cache-components should prerender pages with cached `require('node:crypto').generatePrimeSync(size, options)` calls", + "cache-components should prerender pages with cached `require('node:crypto').getRandomValues(...)` calls", + "cache-components should prerender pages with cached `require('node:crypto').randomBytes(size)` calls", + "cache-components should prerender pages with cached `require('node:crypto').randomFillSync(buffer)` calls", + "cache-components should prerender pages with cached `require('node:crypto').randomInt(max)` calls", + "cache-components should prerender pages with cached `require('node:crypto').randomInt(min, max)` calls", + "cache-components should prerender pages with cached `require('node:crypto').randomUUID()` calls" ], "failed": [], - "pending": [ - "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-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-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 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 strict should load correct styles navigating back again big-interleaved-a -> big-interleaved-b -> big-interleaved-a -> big-interleaved-b", - "css-order strict should load correct styles navigating back again big-interleaved-b -> big-interleaved-a -> big-interleaved-b -> big-interleaved-a", - "css-order strict should load correct styles navigating back again first -> first-client -> first -> first-client", - "css-order strict should load correct styles navigating back again first -> second -> first -> second", - "css-order strict should load correct styles navigating back again first -> second-client -> first -> second-client", - "css-order strict should load correct styles navigating back again first -> third -> first -> third", - "css-order strict should load correct styles navigating back again first-client -> first -> first-client -> first", - "css-order strict should load correct styles navigating back again first-client -> second -> first-client -> second", - "css-order strict should load correct styles navigating back again first-client -> second-client -> first-client -> second-client", - "css-order strict should load correct styles navigating back again first-client -> third -> first-client -> third", - "css-order strict should load correct styles navigating back again interleaved-a -> interleaved-b -> interleaved-a -> interleaved-b", - "css-order strict should load correct styles navigating back again interleaved-b -> interleaved-a -> interleaved-b -> interleaved-a", - "css-order strict should load correct styles navigating back again pages-first -> pages-second -> pages-first -> pages-second", - "css-order strict should load correct styles navigating back again pages-first -> pages-third -> pages-first -> pages-third", - "css-order strict should load correct styles navigating back again pages-interleaved-a -> pages-interleaved-b -> pages-interleaved-a -> pages-interleaved-b", - "css-order strict should load correct styles navigating back again pages-interleaved-b -> pages-interleaved-a -> pages-interleaved-b -> pages-interleaved-a", - "css-order strict should load correct styles navigating back again pages-partial-reversed-a -> pages-partial-reversed-b -> pages-partial-reversed-a -> pages-partial-reversed-b", - "css-order strict should load correct styles navigating back again pages-partial-reversed-b -> pages-partial-reversed-a -> pages-partial-reversed-b -> pages-partial-reversed-a", - "css-order strict should load correct styles navigating back again pages-reversed-a -> pages-reversed-b -> pages-reversed-a -> pages-reversed-b", - "css-order strict should load correct styles navigating back again pages-reversed-b -> pages-reversed-a -> pages-reversed-b -> pages-reversed-a", - "css-order strict should load correct styles navigating back again pages-second -> pages-first -> pages-second -> pages-first", - "css-order strict should load correct styles navigating back again pages-second -> pages-third -> pages-second -> pages-third", - "css-order strict should load correct styles navigating back again pages-third -> pages-first -> pages-third -> pages-first", - "css-order strict should load correct styles navigating back again pages-third -> pages-second -> pages-third -> pages-second", - "css-order strict should load correct styles navigating back again second -> first -> second -> first", - "css-order strict should load correct styles navigating back again second -> first-client -> second -> first-client", - "css-order strict should load correct styles navigating back again second -> second-client -> second -> second-client", - "css-order strict should load correct styles navigating back again second -> third -> second -> third", - "css-order strict should load correct styles navigating back again second-client -> first -> second-client -> first", - "css-order strict should load correct styles navigating back again second-client -> first-client -> second-client -> first-client", - "css-order strict should load correct styles navigating back again second-client -> second -> second-client -> second", - "css-order strict should load correct styles navigating back again second-client -> third -> second-client -> third", - "css-order strict should load correct styles navigating back again third -> first -> third -> first", - "css-order strict should load correct styles navigating back again third -> first-client -> third -> first-client", - "css-order strict should load correct styles navigating back again third -> second -> third -> second", - "css-order strict should load correct styles navigating back again third -> second-client -> third -> second-client", - "css-order strict should load correct styles navigating big-interleaved-a -> big-interleaved-b", - "css-order strict should load correct styles navigating big-interleaved-b -> big-interleaved-a", - "css-order strict should load correct styles navigating pages-interleaved-a -> pages-interleaved-b", - "css-order strict should load correct styles navigating pages-interleaved-b -> pages-interleaved-a", - "css-order strict should load correct styles navigating pages-partial-reversed-a -> pages-partial-reversed-b", - "css-order strict should load correct styles navigating pages-partial-reversed-b -> pages-partial-reversed-a", - "css-order strict should load correct styles navigating pages-reversed-a -> pages-reversed-b", - "css-order strict should load correct styles navigating pages-reversed-b -> pages-reversed-a", - "css-order true should load correct styles navigating back again big-interleaved-a -> big-interleaved-b -> big-interleaved-a -> big-interleaved-b", - "css-order true should load correct styles navigating back again big-interleaved-b -> big-interleaved-a -> big-interleaved-b -> big-interleaved-a", - "css-order true should load correct styles navigating back again first -> first-client -> first -> first-client", - "css-order true should load correct styles navigating back again first -> second -> first -> second", - "css-order true should load correct styles navigating back again first -> second-client -> first -> second-client", - "css-order true should load correct styles navigating back again first -> third -> first -> third", - "css-order true should load correct styles navigating back again first-client -> first -> first-client -> first", - "css-order true should load correct styles navigating back again first-client -> second -> first-client -> second", - "css-order true should load correct styles navigating back again first-client -> second-client -> first-client -> second-client", - "css-order true should load correct styles navigating back again first-client -> third -> first-client -> third", - "css-order true should load correct styles navigating back again interleaved-a -> interleaved-b -> interleaved-a -> interleaved-b", - "css-order true should load correct styles navigating back again interleaved-b -> interleaved-a -> interleaved-b -> interleaved-a", - "css-order true should load correct styles navigating back again pages-first -> pages-second -> pages-first -> pages-second", - "css-order true should load correct styles navigating back again pages-first -> pages-third -> pages-first -> pages-third", - "css-order true should load correct styles navigating back again pages-interleaved-a -> pages-interleaved-b -> pages-interleaved-a -> pages-interleaved-b", - "css-order true should load correct styles navigating back again pages-interleaved-b -> pages-interleaved-a -> pages-interleaved-b -> pages-interleaved-a", - "css-order true should load correct styles navigating back again pages-partial-reversed-a -> pages-partial-reversed-b -> pages-partial-reversed-a -> pages-partial-reversed-b", - "css-order true should load correct styles navigating back again pages-partial-reversed-b -> pages-partial-reversed-a -> pages-partial-reversed-b -> pages-partial-reversed-a", - "css-order true should load correct styles navigating back again pages-reversed-a -> pages-reversed-b -> pages-reversed-a -> pages-reversed-b", - "css-order true should load correct styles navigating back again pages-reversed-b -> pages-reversed-a -> pages-reversed-b -> pages-reversed-a", - "css-order true should load correct styles navigating back again pages-second -> pages-first -> pages-second -> pages-first", - "css-order true should load correct styles navigating back again pages-second -> pages-third -> pages-second -> pages-third", - "css-order true should load correct styles navigating back again pages-third -> pages-first -> pages-third -> pages-first", - "css-order true should load correct styles navigating back again pages-third -> pages-second -> pages-third -> pages-second", - "css-order true should load correct styles navigating back again second -> first -> second -> first", - "css-order true should load correct styles navigating back again second -> first-client -> second -> first-client", - "css-order true should load correct styles navigating back again second -> second-client -> second -> second-client", - "css-order true should load correct styles navigating back again second -> third -> second -> third", - "css-order true should load correct styles navigating back again second-client -> first -> second-client -> first", - "css-order true should load correct styles navigating back again second-client -> first-client -> second-client -> first-client", - "css-order true should load correct styles navigating back again second-client -> second -> second-client -> second", - "css-order true should load correct styles navigating back again second-client -> third -> second-client -> third", - "css-order true should load correct styles navigating back again third -> first -> third -> first", - "css-order true should load correct styles navigating back again third -> first-client -> third -> first-client", - "css-order true should load correct styles navigating back again third -> second -> third -> second", - "css-order true should load correct styles navigating back again third -> second-client -> third -> second-client" - ], + "pending": [], "flakey": [], "runtimeError": false }, - "test/e2e/app-dir/cssnano-colormin/index.test.ts": { - "passed": ["cssnano-colormin should not minify rgb colors to hsla"], + "test/e2e/app-dir/cache-components/cache-components.params.test.ts": { + "passed": [ + "cache-components Param Shadowing should correctly allow param names like then, value, and status when `use`ing params in a client component", + "cache-components Param Shadowing should correctly allow param names like then, value, and status when awaiting params in a server component", + "cache-components Params should fully prerender pages that check individual param keys after `use`ing params in a client component", + "cache-components Params should fully prerender pages that check individual param keys after awaiting params in a server component", + "cache-components Params should partially prerender pages that await params in a server components", + "cache-components Params should partially prerender pages that spread `use`ed params in a client component", + "cache-components Params should partially prerender pages that spread awaited params in a server component", + "cache-components Params should partially prerender pages that use params in a client components" + ], "failed": [], "pending": [], "flakey": [], "runtimeError": false }, - "test/e2e/app-dir/custom-cache-control/custom-cache-control.test.ts": { + "test/e2e/app-dir/cache-components/cache-components.random.test.ts": { "passed": [ - "custom-cache-control should have custom cache-control for app-ssg lazy", - "custom-cache-control should have custom cache-control for app-ssg prerendered", - "custom-cache-control should have custom cache-control for app-ssr", - "custom-cache-control should have custom cache-control for auto static page", - "custom-cache-control should have custom cache-control for pages-ssg lazy", - "custom-cache-control should have custom cache-control for pages-ssg prerendered", - "custom-cache-control should have default cache-control for app-ssg another", - "custom-cache-control should have default cache-control for pages-ssg another", - "custom-cache-control should have default cache-control for pages-ssr" + "cache-components should not have route specific errors", + "cache-components should not prerender pages with uncached Math.random() calls", + "cache-components should prerender pages with cached Math.random() calls" ], "failed": [], "pending": [], "flakey": [], "runtimeError": false }, - "test/e2e/app-dir/dedupe-rsc-error-log/dedupe-rsc-error-log.test.ts": { + "test/e2e/app-dir/cache-components/cache-components.routes.test.ts": { "passed": [ - "dedupe-rsc-error-log should only log RSC error once for edge runtime", - "dedupe-rsc-error-log should only log RSC error once for nodejs runtime", - "dedupe-rsc-error-log should only log SSR error once for edge runtime", - "dedupe-rsc-error-log should only log SSR error once for nodejs runtime" + "cache-components should not prerender GET route handlers that complete in a new Task", + "cache-components should not prerender GET route handlers that have some uncached io (fetches)", + "cache-components should not prerender GET route handlers that have some uncached io (unstable_cache)", + "cache-components should not prerender GET route handlers that use dynamic APIs", + "cache-components should prerender GET route handlers that complete synchronously or in a microtask", + "cache-components should prerender GET route handlers that have entirely cached io (\"use cache\")", + "cache-components should prerender GET route handlers that have entirely cached io (fetches)", + "cache-components should prerender GET route handlers that have entirely cached io (unstable_cache)", + "cache-components should prerender GET route handlers when accessing params" ], "failed": [], "pending": [], "flakey": [], "runtimeError": false }, - "test/e2e/app-dir/dev-overlay/portal-not-affect-parent/portal-not-affect-parent.test.ts": { + "test/e2e/app-dir/cache-components/cache-components.search.test.ts": { "passed": [ - "dev-overlay - portal-not-affect-parent should not affect parent display" + "cache-components should partially prerender pages that `use` searchParams in a client component", + "cache-components should partially prerender pages that `use` searchParams in a server component", + "cache-components should partially prerender pages that await searchParams in a server component" ], "failed": [], "pending": [], "flakey": [], "runtimeError": false }, - "test/e2e/app-dir/disable-logging-route/disable-logging-route.test.ts": { + "test/e2e/app-dir/cache-components/cache-components.server-action.test.ts": { "passed": [ - "app-dir - disable-logging-route should not log if disabled logging" + "cache-components should not fail decoding server action arguments", + "cache-components should not have cache components errors when encoding bound args for inline server actions", + "cache-components should prerender pages with inline server actions" ], "failed": [], "pending": [], "flakey": [], "runtimeError": false }, - "test/e2e/app-dir/draft-mode-middleware/draft-mode-middleware.test.ts": { + "test/e2e/app-dir/cache-components/cache-components.test.ts": { "passed": [ - "app-dir - draft-mode-middleware should be able to disable draft mode with middleware present", - "app-dir - draft-mode-middleware should be able to enable draft mode with middleware present" + "cache-components can prerender pages with parallel routes that are static", + "cache-components can prerender pages with parallel routes that resolve in a microtask", + "cache-components does not prerender pages with parallel routes that resolve in a task", + "cache-components does not prerender pages with parallel routes that uses a dynamic API", + "cache-components should fully prerender pages that use `unstable_noStore()`", + "cache-components should not have route specific errors", + "cache-components should not log not-found errors", + "cache-components should not resume when client components are dynamic but the RSC render was static", + "cache-components should partially prerender pages that do any uncached IO", + "cache-components should partially prerender pages that do any uncached IO (use cache)", + "cache-components should partially prerender pages that take longer than a task to render", + "cache-components should partially prerender pages that use `cookies()`", + "cache-components should partially prerender pages that use `headers()`", + "cache-components should partially prerender pages that use `searchParams` in Client Components", + "cache-components should partially prerender pages that use `searchParams` in Server Components", + "cache-components should partially prerender pages that use at least one fetch without cache", + "cache-components should prerender fully static pages", + "cache-components should prerender pages that cached the whole page", + "cache-components should prerender pages that only use cached (\"use cache\") IO", + "cache-components should prerender pages that only use cached (unstable_cache) IO", + "cache-components should prerender pages that only use cached fetches", + "cache-components should prerender pages that render in a microtask", + "cache-components should prerender static not-found pages" ], "failed": [], "pending": [], "flakey": [], "runtimeError": false }, - "test/e2e/app-dir/draft-mode/draft-mode.test.ts": { + "test/e2e/app-dir/cache-components/cache-components.web-crypto.test.ts": { "passed": [ - "app dir - draft mode in edge runtime should be disabled from api route handler", - "app dir - draft mode in edge runtime should be enabled from api route handler when draft mode enabled", - "app dir - draft mode in edge runtime should generate rand when draft mode enabled", - "app dir - draft mode in edge runtime should have set-cookie header on enable", - "app dir - draft mode in edge runtime should have set-cookie header with redirect location", - "app dir - draft mode in edge runtime should not perform full page navigation on router.refresh()", - "app dir - draft mode in edge runtime should read other cookies when draft mode enabled", - "app dir - draft mode in edge runtime should use initial rand when draft mode is disabled on /with-edge/index", - "app dir - draft mode in edge runtime should use initial rand when draft mode is disabled on /with-edge/with-cookies", - "app dir - draft mode in nodejs runtime should be disabled from api route handler", - "app dir - draft mode in nodejs runtime should be enabled from api route handler when draft mode enabled", - "app dir - draft mode in nodejs runtime should generate rand when draft mode enabled", - "app dir - draft mode in nodejs runtime should have set-cookie header on enable", - "app dir - draft mode in nodejs runtime should have set-cookie header with redirect location", - "app dir - draft mode in nodejs runtime should not perform full page navigation on router.refresh()", - "app dir - draft mode in nodejs runtime should read other cookies when draft mode enabled", - "app dir - draft mode in nodejs runtime should use initial rand when draft mode is disabled on /index", - "app dir - draft mode in nodejs runtime should use initial rand when draft mode is disabled on /with-cookies" + "cache-components should not have route specific errors", + "cache-components should not prerender pages with uncached `crypto.getRandomValues(...)` calls", + "cache-components should not prerender pages with uncached `crypto.randomUUID()` calls", + "cache-components should prerender pages with cached `crypto.getRandomValues(...)` calls", + "cache-components should prerender pages with cached `crypto.randomUUID()` calls" ], "failed": [], "pending": [], "flakey": [], "runtimeError": false }, - "test/e2e/app-dir/dynamic-css/index.test.ts": { + "test/e2e/app-dir/catchall-parallel-routes-group/catchall-parallel-routes-group.test.ts": { "passed": [ - "app dir - dynamic css should not throw with accessing to ALS in preload css", - "app dir - dynamic css should only apply corresponding css for page loaded in edge runtime", - "app dir - dynamic css should only apply corresponding css for page loaded that /another", - "app dir - dynamic css should only apply corresponding css for page loaded that /ssr", - "app dir - dynamic css should preload all chunks of dynamic component during SSR" + "catchall-parallel-routes-group should work without throwing any errors about invalid pages" ], "failed": [], "pending": [], "flakey": [], "runtimeError": false }, - "test/e2e/app-dir/dynamic-data/dynamic-data.test.ts": { + "test/e2e/app-dir/catchall-specificity/catchall-specificity.test.ts": { "passed": [ - "dynamic-data inside cache scope displays redbox when accessing dynamic data inside a cache scope", - "dynamic-data should render empty objects for dynamic APIs when rendering with force-static", - "dynamic-data should render the dynamic apis dynamically when used in a top-level scope", - "dynamic-data should render the dynamic apis dynamically when used in a top-level scope with force dynamic", - "dynamic-data should track searchParams access as dynamic when the Page is a client component", - "dynamic-data with dynamic = \"error\" displays redbox when `dynamic = \"error\"` and dynamic data is read in dev" + "catchall-specificity should match the generic catchall correctly", + "catchall-specificity should match the specific catchall correctly" ], "failed": [], "pending": [], "flakey": [], "runtimeError": false }, - "test/e2e/app-dir/dynamic-href/dynamic-href.test.ts": { + "test/e2e/app-dir/client-module-with-package-type/index.test.ts": { "passed": [ - "dynamic-href should error when using dynamic href in app dir", - "dynamic-href should error when using dynamic href.pathname in app dir" + "esm-client-module-without-exports \"type\": \"commonjs\" in package.json should render without errors: import cjs", + "esm-client-module-without-exports \"type\": \"commonjs\" in package.json should render without errors: require cjs", + "esm-client-module-without-exports \"type\": \"module\" in package.json should render without errors: import esm", + "esm-client-module-without-exports \"type\": \"module\" in package.json should render without errors: require esm" ], "failed": [], "pending": [], "flakey": [], "runtimeError": false }, - "test/e2e/app-dir/dynamic-import/dynamic-import.test.ts": { + "test/e2e/app-dir/conflicting-page-segments/conflicting-page-segments.test.ts": { "passed": [ - "dynamic-import should render the dynamically imported component" + "conflicting-page-segments should throw an error when a route groups causes a conflict with a parallel segment" ], "failed": [], "pending": [], "flakey": [], "runtimeError": false }, - "test/e2e/app-dir/dynamic-in-generate-params/index.test.ts": { + "test/e2e/app-dir/conflicting-search-and-route-params/conflicting-search-and-route-params.test.ts": { "passed": [ - "app-dir - dynamic in generate params should be able to call fetch while generating multiple dynamic pages", - "app-dir - dynamic in generate params should be able to call while generating multiple dynamic sitemaps", - "app-dir - dynamic in generate params should render sitemap with generateSitemaps in force-dynamic config dynamically" + "conflicting-search-and-route-params should handle conflicting search and route params on API route", + "conflicting-search-and-route-params should handle conflicting search and route params on page" ], "failed": [], "pending": [], "flakey": [], "runtimeError": false }, - "test/e2e/app-dir/dynamic-interception-route-revalidate/dynamic-interception-route-revalidate.test.ts": { + "test/e2e/app-dir/create-root-layout/create-root-layout.test.ts": { "passed": [ - "dynamic-interception-route-revalidate should refresh the dynamic intercepted route when the interception route is revalidated" + "app-dir create root layout page.js find available dir create root layout", + "app-dir create root layout page.js root layout in app create root layout", + "app-dir create root layout page.js root layout in route group create root layout", + "app-dir create root layout page.tsx create root layout" ], "failed": [], "pending": [], "flakey": [], "runtimeError": false }, - "test/e2e/app-dir/cache-components-dynamic-imports/cache-components-dynamic-imports.test.ts": { + "test/e2e/app-dir/crypto-globally-available/crypto-globally-available.test.ts": { "passed": [ - "async imports in cacheComponents - external packages does not instrument import() in external packages", - "async imports in cacheComponents are not instrumented in edge edge route handler", - "async imports in cacheComponents are not instrumented in edge middleware", - "async imports in cacheComponents inside a GET route handler import of a sync module", - "async imports in cacheComponents inside a GET route handler import of module with top-level-await", - "async imports in cacheComponents inside a client component import of a sync module", - "async imports in cacheComponents inside a client component import of module with top-level-await", - "async imports in cacheComponents inside a server component dynamic import in node_modules in a CJS package import of a sync module", - "async imports in cacheComponents inside a server component dynamic import in node_modules in an ESM package import of a sync module", - "async imports in cacheComponents inside a server component dynamic import in node_modules in an ESM package import of module with top-level-await", - "async imports in cacheComponents inside a server component import of a sync module", - "async imports in cacheComponents inside a server component import of module with top-level-await", - "async imports in cacheComponents outside of render client import of a sync module", - "async imports in cacheComponents outside of render client import of module with top-level-await", - "async imports in cacheComponents outside of render server import of a sync module", - "async imports in cacheComponents outside of render server import of module with top-level-await" + "Web Crypto API is available globally should be available in Route Handlers", + "Web Crypto API is available globally should be available in Server Components" ], "failed": [], "pending": [], "flakey": [], "runtimeError": false }, - "test/e2e/app-dir/cache-components-errors/cache-components-errors.module-scope.test.ts": { - "passed": ["Lazy Module Init does not run in dev"], + "test/e2e/app-dir/css-chunking/css-chunking.test.ts": { + "passed": [ + "css-chunking should be possible to disable the chunking plugin" + ], "failed": [], "pending": [], "flakey": [], "runtimeError": false }, - "test/e2e/app-dir/cache-components-errors/cache-components-errors.prospective-errors.test.ts": { + "test/e2e/app-dir/css-client-side-nav-parallel-routes/css-client-side-nav-parallel-routes.test.ts": { "passed": [ - "Cache Components Prospective Render Errors - Debug Build should error on the first visit to each page", - "Cache Components Prospective Render Errors - Standard Build should error on the first visit to each page" + "css-client-side-nav-parallel-routes should apply styles after navigation" ], "failed": [], "pending": [], "flakey": [], "runtimeError": false }, - "test/e2e/app-dir/cache-components-errors/cache-components-errors.test.ts": { - "passed": [ - "Cache Components Errors Dev Dynamic Boundary should not show a collapsed redbox error", - "Cache Components Errors Dev Dynamic Metadata - Dynamic Route should not show a collapsed redbox error", - "Cache Components Errors Dev Dynamic Metadata - Error Route should show a collapsed redbox error", - "Cache Components Errors Dev Dynamic Metadata - Static Route With Suspense should show a collapsed redbox error", - "Cache Components Errors Dev Dynamic Metadata - Static Route should show a collapsed redbox error", - "Cache Components Errors Dev Dynamic Root should show a collapsed redbox with two errors", - "Cache Components Errors Dev Dynamic Viewport - Dynamic Route should show a collapsed redbox error", - "Cache Components Errors Dev Dynamic Viewport - Static Route should show a collapsed redbox error", - "Cache Components Errors Dev Error Attribution with Sync IO Guarded RSC with guarded Client sync IO does not show a validation error in the dev overlay", - "Cache Components Errors Dev Error Attribution with Sync IO Guarded RSC with unguarded Client sync IO should show a collapsed redbox error", - "Cache Components Errors Dev Error Attribution with Sync IO Unguarded RSC with guarded Client sync IO should show a collapsed redbox error", - "Cache Components Errors Dev Error Attribution with Sync IO unguarded RSC with unguarded Client sync IO should show a collapsed redbox error", - "Cache Components Errors Dev Inside `use cache` cookies should show a redbox error", - "Cache Components Errors Dev Inside `use cache` draftMode should show a redbox error", - "Cache Components Errors Dev Inside `use cache` headers should show a redbox error", - "Cache Components Errors Dev Static Route should not show a collapsed redbox error", - "Cache Components Errors Dev Sync Dynamic Platform With Fallback - Math.random() should not show a collapsed redbox error", - "Cache Components Errors Dev Sync Dynamic Platform Without Fallback - Math.random() should show a collapsed redbox error", - "Cache Components Errors Dev Sync Dynamic Request client params should return `undefined` for `params.slug`", - "Cache Components Errors Dev Sync Dynamic Request client params should show a collapsed redbox with a sync access error", - "Cache Components Errors Dev Sync Dynamic Request client searchParams should return `undefined` for `searchParams.foo`", - "Cache Components Errors Dev Sync Dynamic Request client searchParams should show a collapsed redbox with a sync access error", - "Cache Components Errors Dev Sync Dynamic Request draftMode should return `undefined` for `draftMode().isEnabled`", - "Cache Components Errors Dev Sync Dynamic Request server params should return `undefined` for `params.slug`", - "Cache Components Errors Dev Sync Dynamic Request server params should show a collapsed redbox with a sync access error", - "Cache Components Errors Dev Sync Dynamic Request server searchParams should return `undefined` for `searchParams.foo`", - "Cache Components Errors Dev Sync Dynamic Request server searchParams should show a collapsed redbox with a sync access error" - ], - "failed": [ - "Cache Components Errors Dev Sync Dynamic Request cookies should show a redbox with a sync access error and a runtime error", - "Cache Components Errors Dev Sync Dynamic Request draftMode should show a collapsed redbox with a sync access error", - "Cache Components Errors Dev Sync Dynamic Request headers should show a redbox with a sync access error and a runtime error" + "test/e2e/app-dir/css-modules-data-urls/css-modules-data-urls.test.ts": { + "passed": [], + "failed": [], + "pending": [ + "css-modules-data-urls should apply client class name from data url correctly", + "css-modules-data-urls should apply client styles from data url correctly", + "css-modules-data-urls should apply rsc class name from data url correctly", + "css-modules-data-urls should apply rsc styles from data url correctly" ], - "pending": [], "flakey": [], "runtimeError": false }, - "test/e2e/app-dir/cache-components-request-apis/cache-components-request-apis.test.ts": { - "passed": [ - "Request Promises On Prerender Completion does not run in dev", - "Request Promises On Prerender Interruption does not run in dev" - ], + "test/e2e/app-dir/css-modules-pure-no-check/css-modules-pure-no-check.test.ts": { + "passed": ["css-modules-pure-no-check should apply styles correctly"], "failed": [], "pending": [], "flakey": [], "runtimeError": false }, - "test/e2e/app-dir/cache-components-segment-configs/cache-components-segment-configs.test.ts": { - "passed": [], - "failed": [ - "cache-components-segment-configs it should error when using segment configs that aren't supported by cacheComponents", - "cache-components-segment-configs should propagate configurations from layouts to pages" + "test/e2e/app-dir/css-modules-scoping/css-modules-scoping.test.ts": { + "passed": [ + "css-modules-scoping should not prefix grid areas", + "css-modules-scoping should prefix animation" ], + "failed": [], "pending": [], "flakey": [], "runtimeError": false }, - "test/e2e/app-dir/cache-components/cache-components.connection.test.ts": { + "test/e2e/app-dir/css-order/css-order.test.ts": { "passed": [ - "cache-components should be able to pass connection as a promise to another component and trigger an intermediate Suspense boundary", - "cache-components should partially prerender pages that use connection" + "css-order loose should load correct styles navigating first -> first-client", + "css-order loose should load correct styles navigating first -> second", + "css-order loose should load correct styles navigating first -> second-client", + "css-order loose should load correct styles navigating first -> third", + "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 -> second-client", + "css-order loose should load correct styles navigating first-client -> third", + "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 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 second -> first", + "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 second -> third", + "css-order loose should load correct styles navigating second-client -> first", + "css-order loose should load correct styles navigating second-client -> first-client", + "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 third -> first", + "css-order loose should load correct styles navigating third -> first-client", + "css-order loose should load correct styles navigating third -> second", + "css-order loose should load correct styles navigating third -> second-client", + "css-order loose should load correct styles on big-interleaved-a", + "css-order loose should load correct styles on big-interleaved-b", + "css-order loose should load correct styles on first", + "css-order loose should load correct styles on first-client", + "css-order loose should load correct styles on interleaved-a", + "css-order loose should load correct styles on interleaved-b", + "css-order loose should load correct styles on pages-first", + "css-order loose should load correct styles on pages-interleaved-a", + "css-order loose should load correct styles on pages-interleaved-b", + "css-order loose should load correct styles on pages-partial-reversed-a", + "css-order loose should load correct styles on pages-partial-reversed-b", + "css-order loose should load correct styles on pages-reversed-a", + "css-order loose should load correct styles on pages-reversed-b", + "css-order loose should load correct styles on pages-second", + "css-order loose should load correct styles on pages-third", + "css-order loose should load correct styles on second", + "css-order loose should load correct styles on second-client", + "css-order loose should load correct styles on third", + "css-order loose should load correct styles on vendor", + "css-order strict should load correct styles navigating first -> first-client", + "css-order strict should load correct styles navigating first -> second", + "css-order strict should load correct styles navigating first -> second-client", + "css-order strict should load correct styles navigating first -> third", + "css-order strict should load correct styles navigating first-client -> first", + "css-order strict should load correct styles navigating first-client -> second", + "css-order strict should load correct styles navigating first-client -> second-client", + "css-order strict should load correct styles navigating first-client -> third", + "css-order strict should load correct styles navigating interleaved-a -> interleaved-b", + "css-order strict should load correct styles navigating interleaved-b -> interleaved-a", + "css-order strict should load correct styles navigating pages-first -> pages-second", + "css-order strict should load correct styles navigating pages-first -> pages-third", + "css-order strict should load correct styles navigating pages-second -> pages-first", + "css-order strict should load correct styles navigating pages-second -> pages-third", + "css-order strict should load correct styles navigating pages-third -> pages-first", + "css-order strict should load correct styles navigating pages-third -> pages-second", + "css-order strict should load correct styles navigating second -> first", + "css-order strict should load correct styles navigating second -> first-client", + "css-order strict should load correct styles navigating second -> second-client", + "css-order strict should load correct styles navigating second -> third", + "css-order strict should load correct styles navigating second-client -> first", + "css-order strict should load correct styles navigating second-client -> first-client", + "css-order strict should load correct styles navigating second-client -> second", + "css-order strict should load correct styles navigating second-client -> third", + "css-order strict should load correct styles navigating third -> first", + "css-order strict should load correct styles navigating third -> first-client", + "css-order strict should load correct styles navigating third -> second", + "css-order strict should load correct styles navigating third -> second-client", + "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 first", + "css-order strict should load correct styles on first-client", + "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 interleaved-a", + "css-order strict should load correct styles on interleaved-b", + "css-order strict should load correct styles on pages-first", + "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-partial-reversed-a", + "css-order strict should load correct styles on pages-partial-reversed-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-second", + "css-order strict should load correct styles on pages-third", + "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 reversed-a", + "css-order strict should load correct styles on reversed-b", + "css-order strict should load correct styles on second", + "css-order strict should load correct styles on second-client", + "css-order strict should load correct styles on third", + "css-order strict should load correct styles on vendor" + ], + "failed": [], + "pending": [ + "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-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-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 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 strict should load correct styles navigating back again big-interleaved-a -> big-interleaved-b -> big-interleaved-a -> big-interleaved-b", + "css-order strict should load correct styles navigating back again big-interleaved-b -> big-interleaved-a -> big-interleaved-b -> big-interleaved-a", + "css-order strict should load correct styles navigating back again first -> first-client -> first -> first-client", + "css-order strict should load correct styles navigating back again first -> second -> first -> second", + "css-order strict should load correct styles navigating back again first -> second-client -> first -> second-client", + "css-order strict should load correct styles navigating back again first -> third -> first -> third", + "css-order strict should load correct styles navigating back again first-client -> first -> first-client -> first", + "css-order strict should load correct styles navigating back again first-client -> second -> first-client -> second", + "css-order strict should load correct styles navigating back again first-client -> second-client -> first-client -> second-client", + "css-order strict should load correct styles navigating back again first-client -> third -> first-client -> third", + "css-order strict should load correct styles navigating back again interleaved-a -> interleaved-b -> interleaved-a -> interleaved-b", + "css-order strict should load correct styles navigating back again interleaved-b -> interleaved-a -> interleaved-b -> interleaved-a", + "css-order strict should load correct styles navigating back again pages-first -> pages-second -> pages-first -> pages-second", + "css-order strict should load correct styles navigating back again pages-first -> pages-third -> pages-first -> pages-third", + "css-order strict should load correct styles navigating back again pages-interleaved-a -> pages-interleaved-b -> pages-interleaved-a -> pages-interleaved-b", + "css-order strict should load correct styles navigating back again pages-interleaved-b -> pages-interleaved-a -> pages-interleaved-b -> pages-interleaved-a", + "css-order strict should load correct styles navigating back again pages-partial-reversed-a -> pages-partial-reversed-b -> pages-partial-reversed-a -> pages-partial-reversed-b", + "css-order strict should load correct styles navigating back again pages-partial-reversed-b -> pages-partial-reversed-a -> pages-partial-reversed-b -> pages-partial-reversed-a", + "css-order strict should load correct styles navigating back again pages-reversed-a -> pages-reversed-b -> pages-reversed-a -> pages-reversed-b", + "css-order strict should load correct styles navigating back again pages-reversed-b -> pages-reversed-a -> pages-reversed-b -> pages-reversed-a", + "css-order strict should load correct styles navigating back again pages-second -> pages-first -> pages-second -> pages-first", + "css-order strict should load correct styles navigating back again pages-second -> pages-third -> pages-second -> pages-third", + "css-order strict should load correct styles navigating back again pages-third -> pages-first -> pages-third -> pages-first", + "css-order strict should load correct styles navigating back again pages-third -> pages-second -> pages-third -> pages-second", + "css-order strict should load correct styles navigating back again second -> first -> second -> first", + "css-order strict should load correct styles navigating back again second -> first-client -> second -> first-client", + "css-order strict should load correct styles navigating back again second -> second-client -> second -> second-client", + "css-order strict should load correct styles navigating back again second -> third -> second -> third", + "css-order strict should load correct styles navigating back again second-client -> first -> second-client -> first", + "css-order strict should load correct styles navigating back again second-client -> first-client -> second-client -> first-client", + "css-order strict should load correct styles navigating back again second-client -> second -> second-client -> second", + "css-order strict should load correct styles navigating back again second-client -> third -> second-client -> third", + "css-order strict should load correct styles navigating back again third -> first -> third -> first", + "css-order strict should load correct styles navigating back again third -> first-client -> third -> first-client", + "css-order strict should load correct styles navigating back again third -> second -> third -> second", + "css-order strict should load correct styles navigating back again third -> second-client -> third -> second-client", + "css-order strict should load correct styles navigating big-interleaved-a -> big-interleaved-b", + "css-order strict should load correct styles navigating big-interleaved-b -> big-interleaved-a", + "css-order strict should load correct styles navigating pages-interleaved-a -> pages-interleaved-b", + "css-order strict should load correct styles navigating pages-interleaved-b -> pages-interleaved-a", + "css-order strict should load correct styles navigating pages-partial-reversed-a -> pages-partial-reversed-b", + "css-order strict should load correct styles navigating pages-partial-reversed-b -> pages-partial-reversed-a", + "css-order strict should load correct styles navigating pages-reversed-a -> pages-reversed-b", + "css-order strict should load correct styles navigating pages-reversed-b -> pages-reversed-a", + "css-order true should load correct styles navigating back again big-interleaved-a -> big-interleaved-b -> big-interleaved-a -> big-interleaved-b", + "css-order true should load correct styles navigating back again big-interleaved-b -> big-interleaved-a -> big-interleaved-b -> big-interleaved-a", + "css-order true should load correct styles navigating back again first -> first-client -> first -> first-client", + "css-order true should load correct styles navigating back again first -> second -> first -> second", + "css-order true should load correct styles navigating back again first -> second-client -> first -> second-client", + "css-order true should load correct styles navigating back again first -> third -> first -> third", + "css-order true should load correct styles navigating back again first-client -> first -> first-client -> first", + "css-order true should load correct styles navigating back again first-client -> second -> first-client -> second", + "css-order true should load correct styles navigating back again first-client -> second-client -> first-client -> second-client", + "css-order true should load correct styles navigating back again first-client -> third -> first-client -> third", + "css-order true should load correct styles navigating back again interleaved-a -> interleaved-b -> interleaved-a -> interleaved-b", + "css-order true should load correct styles navigating back again interleaved-b -> interleaved-a -> interleaved-b -> interleaved-a", + "css-order true should load correct styles navigating back again pages-first -> pages-second -> pages-first -> pages-second", + "css-order true should load correct styles navigating back again pages-first -> pages-third -> pages-first -> pages-third", + "css-order true should load correct styles navigating back again pages-interleaved-a -> pages-interleaved-b -> pages-interleaved-a -> pages-interleaved-b", + "css-order true should load correct styles navigating back again pages-interleaved-b -> pages-interleaved-a -> pages-interleaved-b -> pages-interleaved-a", + "css-order true should load correct styles navigating back again pages-partial-reversed-a -> pages-partial-reversed-b -> pages-partial-reversed-a -> pages-partial-reversed-b", + "css-order true should load correct styles navigating back again pages-partial-reversed-b -> pages-partial-reversed-a -> pages-partial-reversed-b -> pages-partial-reversed-a", + "css-order true should load correct styles navigating back again pages-reversed-a -> pages-reversed-b -> pages-reversed-a -> pages-reversed-b", + "css-order true should load correct styles navigating back again pages-reversed-b -> pages-reversed-a -> pages-reversed-b -> pages-reversed-a", + "css-order true should load correct styles navigating back again pages-second -> pages-first -> pages-second -> pages-first", + "css-order true should load correct styles navigating back again pages-second -> pages-third -> pages-second -> pages-third", + "css-order true should load correct styles navigating back again pages-third -> pages-first -> pages-third -> pages-first", + "css-order true should load correct styles navigating back again pages-third -> pages-second -> pages-third -> pages-second", + "css-order true should load correct styles navigating back again second -> first -> second -> first", + "css-order true should load correct styles navigating back again second -> first-client -> second -> first-client", + "css-order true should load correct styles navigating back again second -> second-client -> second -> second-client", + "css-order true should load correct styles navigating back again second -> third -> second -> third", + "css-order true should load correct styles navigating back again second-client -> first -> second-client -> first", + "css-order true should load correct styles navigating back again second-client -> first-client -> second-client -> first-client", + "css-order true should load correct styles navigating back again second-client -> second -> second-client -> second", + "css-order true should load correct styles navigating back again second-client -> third -> second-client -> third", + "css-order true should load correct styles navigating back again third -> first -> third -> first", + "css-order true should load correct styles navigating back again third -> first-client -> third -> first-client", + "css-order true should load correct styles navigating back again third -> second -> third -> second", + "css-order true should load correct styles navigating back again third -> second-client -> third -> second-client" ], - "failed": [], - "pending": [], "flakey": [], "runtimeError": false }, - "test/e2e/app-dir/cache-components/cache-components.console.test.ts": { - "passed": [ - "cache-components dims console calls during prospective rendering" - ], + "test/e2e/app-dir/cssnano-colormin/index.test.ts": { + "passed": ["cssnano-colormin should not minify rgb colors to hsla"], "failed": [], "pending": [], "flakey": [], "runtimeError": false }, - "test/e2e/app-dir/cache-components/cache-components.cookies.test.ts": { + "test/e2e/app-dir/custom-cache-control/custom-cache-control.test.ts": { "passed": [ - "cache-components should be able to access cookie properties", - "cache-components should be able to pass cookies as a promise to another component and trigger an intermediate Suspense boundary", - "cache-components should partially prerender pages that use cookies" + "custom-cache-control should have custom cache-control for app-ssg lazy", + "custom-cache-control should have custom cache-control for app-ssg prerendered", + "custom-cache-control should have custom cache-control for app-ssr", + "custom-cache-control should have custom cache-control for auto static page", + "custom-cache-control should have custom cache-control for pages-ssg lazy", + "custom-cache-control should have custom cache-control for pages-ssg prerendered", + "custom-cache-control should have default cache-control for app-ssg another", + "custom-cache-control should have default cache-control for pages-ssg another", + "custom-cache-control should have default cache-control for pages-ssr" ], "failed": [], "pending": [], "flakey": [], "runtimeError": false }, - "test/e2e/app-dir/cache-components/cache-components.date.test.ts": { + "test/e2e/app-dir/dedupe-rsc-error-log/dedupe-rsc-error-log.test.ts": { "passed": [ - "cache-components should not have route specific errors", - "cache-components should not prerender pages with uncached `Date()` calls", - "cache-components should not prerender pages with uncached `Date.now()` calls", - "cache-components should not prerender pages with uncached `new Date()` calls", - "cache-components should not prerender pages with uncached static Date instances like `new Date(0)`", - "cache-components should prerender pages with cached `Date()` calls", - "cache-components should prerender pages with cached `Date.now()` calls", - "cache-components should prerender pages with cached `new Date()` calls", - "cache-components should prerender pages with cached static Date instances like `new Date(0)`" + "dedupe-rsc-error-log should only log RSC error once for edge runtime", + "dedupe-rsc-error-log should only log RSC error once for nodejs runtime", + "dedupe-rsc-error-log should only log SSR error once for edge runtime", + "dedupe-rsc-error-log should only log SSR error once for nodejs runtime" ], "failed": [], "pending": [], "flakey": [], "runtimeError": false }, - "test/e2e/app-dir/cache-components/cache-components.draft-mode.test.ts": { + "test/e2e/app-dir/dev-overlay/portal-not-affect-parent/portal-not-affect-parent.test.ts": { "passed": [ - "cache-components should fully prerender pages that use draftMode" + "dev-overlay - portal-not-affect-parent should not affect parent display" ], "failed": [], "pending": [], "flakey": [], "runtimeError": false }, - "test/e2e/app-dir/cache-components/cache-components.headers.test.ts": { + "test/e2e/app-dir/disable-logging-route/disable-logging-route.test.ts": { "passed": [ - "cache-components should be able to access headers properties asynchronously", - "cache-components should be able to pass headers as a promise to another component and trigger an intermediate Suspense boundary", - "cache-components should partially prerender pages that use headers" + "app-dir - disable-logging-route should not log if disabled logging" ], "failed": [], "pending": [], "flakey": [], "runtimeError": false }, - "test/e2e/app-dir/cache-components/cache-components.node-crypto.test.ts": { + "test/e2e/app-dir/draft-mode-middleware/draft-mode-middleware.test.ts": { "passed": [ - "cache-components should not have route specific errors", - "cache-components should not prerender pages with uncached `require('node:crypto').generateKeyPairSync(type, options)` calls", - "cache-components should not prerender pages with uncached `require('node:crypto').generateKeySync(type, options)` calls", - "cache-components should not prerender pages with uncached `require('node:crypto').generatePrimeSync(size, options)` calls", - "cache-components should not prerender pages with uncached `require('node:crypto').getRandomValues(...)` calls", - "cache-components should not prerender pages with uncached `require('node:crypto').randomBytes(size)` calls", - "cache-components should not prerender pages with uncached `require('node:crypto').randomFillSync(buffer)` calls", - "cache-components should not prerender pages with uncached `require('node:crypto').randomInt(max)` calls", - "cache-components should not prerender pages with uncached `require('node:crypto').randomInt(min, max)` calls", - "cache-components should not prerender pages with uncached `require('node:crypto').randomUUID()` calls", - "cache-components should prerender pages with cached `require('node:crypto').generateKeyPairSync(type, options)` calls", - "cache-components should prerender pages with cached `require('node:crypto').generateKeySync(type, options)` calls", - "cache-components should prerender pages with cached `require('node:crypto').generatePrimeSync(size, options)` calls", - "cache-components should prerender pages with cached `require('node:crypto').getRandomValues(...)` calls", - "cache-components should prerender pages with cached `require('node:crypto').randomBytes(size)` calls", - "cache-components should prerender pages with cached `require('node:crypto').randomFillSync(buffer)` calls", - "cache-components should prerender pages with cached `require('node:crypto').randomInt(max)` calls", - "cache-components should prerender pages with cached `require('node:crypto').randomInt(min, max)` calls", - "cache-components should prerender pages with cached `require('node:crypto').randomUUID()` calls" + "app-dir - draft-mode-middleware should be able to disable draft mode with middleware present", + "app-dir - draft-mode-middleware should be able to enable draft mode with middleware present" ], "failed": [], "pending": [], "flakey": [], "runtimeError": false }, - "test/e2e/app-dir/cache-components/cache-components.params.test.ts": { + "test/e2e/app-dir/draft-mode/draft-mode.test.ts": { "passed": [ - "cache-components Param Shadowing should correctly allow param names like then, value, and status when `use`ing params in a client component", - "cache-components Param Shadowing should correctly allow param names like then, value, and status when awaiting params in a server component", - "cache-components Params should fully prerender pages that check individual param keys after `use`ing params in a client component", - "cache-components Params should fully prerender pages that check individual param keys after awaiting params in a server component", - "cache-components Params should partially prerender pages that await params in a server components", - "cache-components Params should partially prerender pages that spread `use`ed params in a client component", - "cache-components Params should partially prerender pages that spread awaited params in a server component", - "cache-components Params should partially prerender pages that use params in a client components" + "app dir - draft mode in edge runtime should be disabled from api route handler", + "app dir - draft mode in edge runtime should be enabled from api route handler when draft mode enabled", + "app dir - draft mode in edge runtime should generate rand when draft mode enabled", + "app dir - draft mode in edge runtime should have set-cookie header on enable", + "app dir - draft mode in edge runtime should have set-cookie header with redirect location", + "app dir - draft mode in edge runtime should not perform full page navigation on router.refresh()", + "app dir - draft mode in edge runtime should read other cookies when draft mode enabled", + "app dir - draft mode in edge runtime should use initial rand when draft mode is disabled on /with-edge/index", + "app dir - draft mode in edge runtime should use initial rand when draft mode is disabled on /with-edge/with-cookies", + "app dir - draft mode in nodejs runtime should be disabled from api route handler", + "app dir - draft mode in nodejs runtime should be enabled from api route handler when draft mode enabled", + "app dir - draft mode in nodejs runtime should generate rand when draft mode enabled", + "app dir - draft mode in nodejs runtime should have set-cookie header on enable", + "app dir - draft mode in nodejs runtime should have set-cookie header with redirect location", + "app dir - draft mode in nodejs runtime should not perform full page navigation on router.refresh()", + "app dir - draft mode in nodejs runtime should read other cookies when draft mode enabled", + "app dir - draft mode in nodejs runtime should use initial rand when draft mode is disabled on /index", + "app dir - draft mode in nodejs runtime should use initial rand when draft mode is disabled on /with-cookies" ], "failed": [], "pending": [], "flakey": [], "runtimeError": false }, - "test/e2e/app-dir/cache-components/cache-components.random.test.ts": { + "test/e2e/app-dir/dynamic-css/index.test.ts": { "passed": [ - "cache-components should not have route specific errors", - "cache-components should not prerender pages with uncached Math.random() calls", - "cache-components should prerender pages with cached Math.random() calls" + "app dir - dynamic css should not throw with accessing to ALS in preload css", + "app dir - dynamic css should only apply corresponding css for page loaded in edge runtime", + "app dir - dynamic css should only apply corresponding css for page loaded that /another", + "app dir - dynamic css should only apply corresponding css for page loaded that /ssr", + "app dir - dynamic css should preload all chunks of dynamic component during SSR" ], "failed": [], "pending": [], "flakey": [], "runtimeError": false }, - "test/e2e/app-dir/cache-components/cache-components.routes.test.ts": { + "test/e2e/app-dir/dynamic-data/dynamic-data.test.ts": { "passed": [ - "cache-components should not prerender GET route handlers that complete in a new Task", - "cache-components should not prerender GET route handlers that have some uncached io (fetches)", - "cache-components should not prerender GET route handlers that have some uncached io (unstable_cache)", - "cache-components should not prerender GET route handlers that use dynamic APIs", - "cache-components should prerender GET route handlers that complete synchronously or in a microtask", - "cache-components should prerender GET route handlers that have entirely cached io (\"use cache\")", - "cache-components should prerender GET route handlers that have entirely cached io (fetches)", - "cache-components should prerender GET route handlers that have entirely cached io (unstable_cache)", - "cache-components should prerender GET route handlers when accessing params" + "dynamic-data inside cache scope displays redbox when accessing dynamic data inside a cache scope", + "dynamic-data should render empty objects for dynamic APIs when rendering with force-static", + "dynamic-data should render the dynamic apis dynamically when used in a top-level scope", + "dynamic-data should render the dynamic apis dynamically when used in a top-level scope with force dynamic", + "dynamic-data should track searchParams access as dynamic when the Page is a client component", + "dynamic-data with dynamic = \"error\" displays redbox when `dynamic = \"error\"` and dynamic data is read in dev" ], "failed": [], "pending": [], "flakey": [], "runtimeError": false }, - "test/e2e/app-dir/cache-components/cache-components.search.test.ts": { + "test/e2e/app-dir/dynamic-href/dynamic-href.test.ts": { "passed": [ - "cache-components should partially prerender pages that `use` searchParams in a client component", - "cache-components should partially prerender pages that `use` searchParams in a server component", - "cache-components should partially prerender pages that await searchParams in a server component" + "dynamic-href should error when using dynamic href in app dir", + "dynamic-href should error when using dynamic href.pathname in app dir" ], "failed": [], "pending": [], "flakey": [], "runtimeError": false }, - "test/e2e/app-dir/cache-components/cache-components.server-action.test.ts": { + "test/e2e/app-dir/dynamic-import/dynamic-import.test.ts": { "passed": [ - "cache-components should not fail decoding server action arguments", - "cache-components should not have cache components errors when encoding bound args for inline server actions", - "cache-components should prerender pages with inline server actions" + "dynamic-import should render the dynamically imported component" ], "failed": [], "pending": [], "flakey": [], "runtimeError": false }, - "test/e2e/app-dir/cache-components/cache-components.test.ts": { + "test/e2e/app-dir/dynamic-in-generate-params/index.test.ts": { "passed": [ - "cache-components can prerender pages with parallel routes that are static", - "cache-components can prerender pages with parallel routes that resolve in a microtask", - "cache-components does not prerender pages with parallel routes that resolve in a task", - "cache-components does not prerender pages with parallel routes that uses a dynamic API", - "cache-components should fully prerender pages that use `unstable_noStore()`", - "cache-components should not have route specific errors", - "cache-components should not log not-found errors", - "cache-components should not resume when client components are dynamic but the RSC render was static", - "cache-components should partially prerender pages that do any uncached IO", - "cache-components should partially prerender pages that do any uncached IO (use cache)", - "cache-components should partially prerender pages that take longer than a task to render", - "cache-components should partially prerender pages that use `cookies()`", - "cache-components should partially prerender pages that use `headers()`", - "cache-components should partially prerender pages that use `searchParams` in Client Components", - "cache-components should partially prerender pages that use `searchParams` in Server Components", - "cache-components should partially prerender pages that use at least one fetch without cache", - "cache-components should prerender fully static pages", - "cache-components should prerender pages that cached the whole page", - "cache-components should prerender pages that only use cached (\"use cache\") IO", - "cache-components should prerender pages that only use cached (unstable_cache) IO", - "cache-components should prerender pages that only use cached fetches", - "cache-components should prerender pages that render in a microtask", - "cache-components should prerender static not-found pages" + "app-dir - dynamic in generate params should be able to call fetch while generating multiple dynamic pages", + "app-dir - dynamic in generate params should be able to call while generating multiple dynamic sitemaps", + "app-dir - dynamic in generate params should render sitemap with generateSitemaps in force-dynamic config dynamically" ], "failed": [], "pending": [], "flakey": [], "runtimeError": false }, - "test/e2e/app-dir/cache-components/cache-components.web-crypto.test.ts": { + "test/e2e/app-dir/dynamic-interception-route-revalidate/dynamic-interception-route-revalidate.test.ts": { "passed": [ - "cache-components should not have route specific errors", - "cache-components should not prerender pages with uncached `crypto.getRandomValues(...)` calls", - "cache-components should not prerender pages with uncached `crypto.randomUUID()` calls", - "cache-components should prerender pages with cached `crypto.getRandomValues(...)` calls", - "cache-components should prerender pages with cached `crypto.randomUUID()` calls" + "dynamic-interception-route-revalidate should refresh the dynamic intercepted route when the interception route is revalidated" ], "failed": [], "pending": [], @@ -7458,6 +7524,18 @@ "flakey": [], "runtimeError": false }, + "test/e2e/app-dir/middleware-rewrite-catchall-priority-with-parallel-route/middleware-rewrite-catchall-priority-with-parallel-route.test.js": { + "passed": [ + "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", + "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 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 payment route should rewrite to the specific page instead of the catch-all with parallel route" + ], + "failed": [], + "pending": [], + "flakey": [], + "runtimeError": false + }, "test/e2e/app-dir/middleware-rewrite-dynamic/middleware-rewrite-dynamic.test.ts": { "passed": [ "app dir - middleware rewrite dynamic should properly rewrite for /favicon.ico",