Next Js Daily: Request Insights Land, Turbopack Trims the Fat
A five-part request insights stack merged today, giving dev servers and tooling visibility into request history and spans, while a separate trio of Turbopack PRs builds out dead-code elimination for CommonJS modules. Meanwhile, three targeted fixes address long-standing routing and build edge cases.
Duration: PT2M23S
Episode overview
This episode is a short developer briefing from Next Js Daily.
It explains recent repository work in plain language.
- Show: Next Js Daily
- Published: 2026-07-12T22:00:52Z
- Audio duration: PT2M23S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good morning. It's July 12th, 2026, and this is Next Js Daily.
The big story today is request insights, a five-part stack from Jimmy Lai that merged in full. The pattern here is a layered build-out: first a local span recorder that mirrors OTEL data without needing a provider installed, that's PR ninety-three-nine-seven-four. Then a history store on top of it, keeping the last…
Second theme: Turbopack is getting smarter about dead code in CommonJS modules. Sampoder shipped three connected PRs — analyzing which exports are actually used from CJS modules in PR ninety-five-seven-one-six, tracking how required modules get consumed in PR ninety-five-seven-one-seven, and then actually dropping…
On the fix side, three separate bugs worth flagging. PR ninety-five-seven-one-three stops an empty app directory from silently overriding a pages 404 page. PR ninety-five-seven-one-one fixes a webpack build failure when page extensions is configured with a single value — a querystring serialization quirk was…
What's next: watch for the remaining two PRs in the request insights stack — agent diagnosis access and a DevTools panel — to land soon. And if you're on Turbopack's tree-shaking flag, the…
That'…