[Not for merge] Fixture for sourcemaps#96084
Conversation
Stats from current PR🔴 1 regression
📊 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
Server Middleware
Build DetailsBuild Manifests
📦 WebpackClient Main Bundles
Polyfills
Pages
Server Edge SSR
Middleware
Build DetailsBuild Manifests
Build Cache
🔄 Shared (bundler-independent)Runtimes
📎 Tarball URLCommit: edbe4a9 |
1977956 to
90bf403
Compare
Failing test suitesCommit: edbe4a9 | About building and testing Next.js
Expand output● fake stack frames › reviving one error › revives an error with a source mapped fake stack frame ● fake stack frames › reviving one error › reproduces the fake script layout byte-for-byte across revivals ● fake stack frames › reviving one error › reuses fake stack frame scripts for identical frames ● fake stack frames › reviving one error › creates one fake script per consumer under colliding URLs ● fake stack frames › which frames serialize › serializes no frames for code in node_modules ● fake stack frames › which frames serialize › serializes no frames for chunks in directories named like node_modules ... truncated ...
... truncated to fit in one GitHub comment ... |
90bf403 to
b8cbac4
Compare
b8cbac4 to
edbe4a9
Compare
Not for merge.
I asked Claude to make this fixture to help me understand the impact of changes to sourcemapping logic in Next.js. It hardcodes checked-in faithful (hopefully) copies of the relevant React logic without actual Flight stuff, rendering, etc.
So we can capture dozens of inline snapshots that show how different pieces of Next.js see the stack. I've nudged Claude towards as much Next.js coverage as reasonable. If you scroll through this test, you'll see what I mean.
This reflects the current behavior so there might be some weird tests.
Since this would require updating whenever React updates upstream, even though (I believe) any divergence is caught by tests, this is still too annoying. So I don't actually aim to merge it but can use every once in a while as an aid.