Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. |
Failing test suitesCommit: 2ccaa11 | About building and testing Next.js
Expand output● app dir client cache semantics (30s/5min) › prefetch={undefined} - default › should refetch the full page after 5 mins
Expand output● segment cache (basic tests) › refreshes page segments when navigating to the exact same URL as the current location
Expand output● app dir client cache with parallel routes › prefetch={true} › should re-use the cache for the full page, only for 5 mins |
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: **400 kB** → **400 kB** ✅ -13 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 |
a3751bd to
2ccaa11
Compare

Two steps forward, one step back
Reverts #88641 and #88806
I ended up having to keep the build id in
_next/dataroutes anyway (and made the id a constant if skew protection is enabled). This was because it was utterly impossible to change the routes from_next/data/:buildId/*to_next/data/*in the builder in a backwards-compatible way.So there is no need to remove the build id from
_next/statichere either. It just makes testing a huge pain because the paths keep changing