Turbopack: emit/collect#91100
Turbopack: emit/collect#91100mischnic wants to merge 21 commits intomischnic/ReferenceTypeConditionfrom
Conversation
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
Failing test suitesCommit: e810348 | About building and testing Next.js
Expand output● turbopack-emit-collect › works for /client/a ● turbopack-emit-collect › works for /client/b ● turbopack-emit-collect › works for /rsc/a ● turbopack-emit-collect › works for /rsc/b ● turbopack-emit-collect › works for /rsc/c ● turbopack-emit-collect › works for /api
Expand output● Root Catch-all Cache › production mode › should cache / correctly
Expand output● build trace with extra entries › production mode › should build and trace correctly
Expand output● next-config-ts-top-level-await-esm › should support top-level await (ESM)
Expand output● next-config-ts-node-api-esm › should be able to use Node.js API (ESM)
Expand output● next/dynamic › production mode › should load a Pages Router page correctly ● next/dynamic › production mode › should load a App Router page correctly
Expand output● Telemetry CLI › production mode › detects tests correctly for ● Telemetry CLI › production mode › detect static 404 correctly for ● Telemetry CLI › production mode › detect page counts correctly for
Expand output● config telemetry › production mode › detects rewrites, headers, and redirects for next build ● config telemetry › production mode › emits telemetry for usage of middleware
Expand output● tsconfig.json verifier › Creates a default tsconfig.json when one is missing ● tsconfig.json verifier › Works with an empty tsconfig.json (docs) ● tsconfig.json verifier › Updates an existing tsconfig.json without losing comments ● tsconfig.json verifier › allows you to set commonjs module mode ● tsconfig.json verifier › allows you to set es2020 module mode ● tsconfig.json verifier › allows you to set node16 moduleResolution mode ● tsconfig.json verifier › allows you to set bundler moduleResolution mode ● tsconfig.json verifier › allows you to set target mode ● tsconfig.json verifier › allows you to set node16 module mode ● tsconfig.json verifier › allows you to set verbatimModuleSyntax true without adding isolatedModules ● tsconfig.json verifier › allows you to set verbatimModuleSyntax true via extends without adding isolatedModules ● tsconfig.json verifier › allows you to extend another configuration file ● tsconfig.json verifier › creates compilerOptions when you extend another config
Expand output● stale-dev-types › should not fail build when .next/dev has stale types from deleted routes
Expand output● Image localPatterns config › production mode › should load img when quality is undefined ● Image localPatterns config › production mode › should load img when quality 42 ● Image localPatterns config › production mode › should load img when quality 69 ● Image localPatterns config › production mode › should load img when quality 88 ● Image localPatterns config › production mode › should coerce quality 100 to closest matching of 88 ● Image localPatterns config › production mode › should build correct images-manifest.json
Expand output● escheck-output › es2020 › should downlevel JS ● escheck-output › default browserslist › should downlevel JS ● escheck-output › nomodule browsers › should downlevel JS
Expand output● app dir - with output export - dynamic api route › should work in prod with dynamicPage undefined › should work ● app dir - with output export - dynamic api route › should work in prod with dynamicPage 'error' › should work ● app dir - with output export - dynamic api route › should work in prod with dynamicPage 'force-static' › should work
Expand output● deterministic build - changing deployment id › standard - .next folder › should produce identical build outputs even when changing deployment id ● deterministic build - changing deployment id › build output API - standard builder › should produce identical build outputs even when changing deployment id ● deterministic build - changing deployment id › build output API - standard adapter › should produce identical build outputs even when changing deployment id ● deterministic build - changing deployment id › build output API - cacheComponents builder › should produce identical build outputs even when changing deployment id ● deterministic build - changing deployment id › build output API - cacheComponents adapter › should produce identical build outputs even when changing deployment id
Expand output● postcss-config-ts › postcss.config.ts › works with postcss.config.ts files ● postcss-config-ts › .postcssrc.ts › works with .postcssrc.ts files ● postcss-config-ts › postcss.config.mts › works with postcss.config.mts files ● postcss-config-ts › postcss.config.cts › works with postcss.config.cts files
Expand output● debug-build-paths › default fixture › explicit path formats › should build dynamic route with literal [slug] path ● debug-build-paths › default fixture › glob pattern matching › should match app and pages routes with glob patterns ● debug-build-paths › default fixture › glob pattern matching › should match nested routes with app/blog/**/page.tsx pattern ● debug-build-paths › default fixture › glob pattern matching › should match dynamic routes with glob before brackets like app/**/[slug]/page.tsx ● debug-build-paths › default fixture › glob pattern matching › should match hybrid pattern with literal [slug] and glob ** ● debug-build-paths › default fixture › glob pattern matching › should match multiple app routes with explicit patterns ● debug-build-paths › default fixture › glob pattern matching › should exclude paths matching negation patterns ● debug-build-paths › default fixture › glob pattern matching › should exclude dynamic route paths with negation ● debug-build-paths › default fixture › glob pattern matching › should support multiple negation patterns ● debug-build-paths › default fixture › glob pattern matching › should build everything except excluded paths when only negation patterns are provided ● debug-build-paths › default fixture › glob pattern matching › should build routes inside route groups ● debug-build-paths › default fixture › glob pattern matching › should build routes with parallel routes ● debug-build-paths › with-compile-error fixture › should skip compilation of excluded routes with compile errors
Expand output● deployment-id-handling enabled with NEXT_DEPLOYMENT_ID › should append dpl query to all assets correctly for / ● deployment-id-handling enabled with NEXT_DEPLOYMENT_ID › should append dpl query to all assets correctly for /pages-edge ● deployment-id-handling enabled with NEXT_DEPLOYMENT_ID › should append dpl query to all assets correctly for /from-app ● deployment-id-handling enabled with NEXT_DEPLOYMENT_ID › should append dpl query to all assets correctly for /from-app/edge ● deployment-id-handling enabled with NEXT_DEPLOYMENT_ID › should have deployment id env available ● deployment-id-handling enabled with NEXT_DEPLOYMENT_ID › should have deployment id env available ● deployment-id-handling enabled with NEXT_DEPLOYMENT_ID › should contain deployment id in prefetch request ● deployment-id-handling enabled with NEXT_DEPLOYMENT_ID › should contain deployment id in RSC payload request headers ● deployment-id-handling enabled with CUSTOM_DEPLOYMENT_ID › should append dpl query to all assets correctly for / ● deployment-id-handling enabled with CUSTOM_DEPLOYMENT_ID › should append dpl query to all assets correctly for /pages-edge ● deployment-id-handling enabled with CUSTOM_DEPLOYMENT_ID › should append dpl query to all assets correctly for /from-app ● deployment-id-handling enabled with CUSTOM_DEPLOYMENT_ID › should append dpl query to all assets correctly for /from-app/edge ● deployment-id-handling enabled with CUSTOM_DEPLOYMENT_ID › should have deployment id env available ● deployment-id-handling enabled with CUSTOM_DEPLOYMENT_ID › should have deployment id env available ● deployment-id-handling enabled with CUSTOM_DEPLOYMENT_ID › should contain deployment id in prefetch request ● deployment-id-handling enabled with CUSTOM_DEPLOYMENT_ID › should contain deployment id in RSC payload request headers ● deployment-id-handling enabled with NEXT_DEPLOYMENT_ID and runtimeServerDeploymentId › should append dpl query to all assets correctly for / ● deployment-id-handling enabled with NEXT_DEPLOYMENT_ID and runtimeServerDeploymentId › should append dpl query to all assets correctly for /pages-edge ● deployment-id-handling enabled with NEXT_DEPLOYMENT_ID and runtimeServerDeploymentId › should append dpl query to all assets correctly for /from-app ● deployment-id-handling enabled with NEXT_DEPLOYMENT_ID and runtimeServerDeploymentId › should append dpl query to all assets correctly for /from-app/edge ● deployment-id-handling enabled with NEXT_DEPLOYMENT_ID and runtimeServerDeploymentId › should have deployment id env available ● deployment-id-handling enabled with NEXT_DEPLOYMENT_ID and runtimeServerDeploymentId › should have deployment id env available ● deployment-id-handling enabled with NEXT_DEPLOYMENT_ID and runtimeServerDeploymentId › should contain deployment id in prefetch request ● deployment-id-handling enabled with NEXT_DEPLOYMENT_ID and runtimeServerDeploymentId › should contain deployment id in RSC payload request headers ● deployment-id-handling enabled with IMMUTABLE_ASSET_TOKEN › should append dpl query to all assets correctly for / ● deployment-id-handling enabled with IMMUTABLE_ASSET_TOKEN › should append dpl query to all assets correctly for /pages-edge ● deployment-id-handling enabled with IMMUTABLE_ASSET_TOKEN › should append dpl query to all assets correctly for /from-app ● deployment-id-handling enabled with IMMUTABLE_ASSET_TOKEN › should append dpl query to all assets correctly for /from-app/edge ● deployment-id-handling enabled with IMMUTABLE_ASSET_TOKEN › should have deployment id env available ● deployment-id-handling enabled with IMMUTABLE_ASSET_TOKEN › should have deployment id env available ● deployment-id-handling enabled with IMMUTABLE_ASSET_TOKEN › should contain deployment id in prefetch request ● deployment-id-handling enabled with IMMUTABLE_ASSET_TOKEN › should contain deployment id in RSC payload request headers ● deployment-id-handling disabled › should not append dpl query to all assets for / ● deployment-id-handling disabled › should not append dpl query to all assets for /pages-edge ● deployment-id-handling disabled › should not append dpl query to all assets for /from-app ● deployment-id-handling disabled › should not append dpl query to all assets for /from-app/edge |
Merging this PR will not alter performance
Comparing Footnotes
|
Stats from current PR✅ No significant changes detected📊 All Metrics📖 Metrics GlossaryDev Server Metrics:
Build Metrics:
Change Thresholds:
⚡ Dev Server
📦 Dev Server (Webpack) (Legacy)📦 Dev Server (Webpack)
⚡ Production Builds
📦 Production Builds (Webpack) (Legacy)📦 Production Builds (Webpack)
📦 Bundle SizesBundle Sizes⚡ TurbopackClient Main Bundles: **402 kB** → **402 kB** ✅ -11 B80 files with content-based hashes (individual files not comparable between builds) Server Middleware
Build DetailsBuild Manifests
📦 WebpackClient Main Bundles
Polyfills
Pages
Server Edge SSR
Middleware
Build DetailsBuild Manifests
Build Cache
🔄 Shared (bundler-independent)Runtimes
📎 Tarball URL |
358196c to
91a848f
Compare
91a848f to
e810348
Compare

No description provided.