$ the-wire · showcase
TURBOPACK RUNTIME FIXES SHIP AS NEXT.JS LOCKS DOWN APP SHELL STREAMING
By RepoJournal · Filed · About Vercel · Composed from the cited sources · methodology
![vercel-gh-bot-2[bot]](https://avatars.githubusercontent.com/in/3623420?v=4)
Sampoder eliminated a high-severity deoptimization in Turbopack's chunk URL resolution that was bailing out on large import trees, while the team shipped per-segment prefetch offsets to squeeze more performance out of static rendering.
The runtime fix [1] addressed a "wrong map" deopt in getChunkRelativeUrl that was firing on large fixtures with heavy imports, likely a common pattern in real applications. That same work unblocked the shell offset feature [2], which lets the client extract a shell response from a larger prerender response by reading a bytes offset during segment prefetching, matching the strategy already used at page level. Timneutkens added Vite-compatible caseSensitive support to import.meta.glob [3], letting developers toggle case-insensitive matching on directory traversal and patterns. Over on Eve, the team hardened documentation around the durable agent loop and sandbox boundary [4], linking execution model details to the security model to give developers a clear mental model of what runs where and how state divides.
Action items
- → Pull Turbopack runtime fixes into your next.js canary builds and test against apps with heavy dynamic imports vercel/next.js [plan]
- → Review shell offset changes if you rely on static segment prefetching or per-segment caching strategies vercel/next.js [monitor]
- → Check Eve docs if you're building durable agents to understand sandbox and state boundaries vercel/eve [monitor]
References
- [1] [turbopack] Fix de-opt in getChunkRelativeUrl() ↗ vercel/next.js
- [2] Add shell offset to static segment prefetches ↗ vercel/next.js
- [3] Turbopack: support import.meta.glob caseSensitive option ↗ vercel/next.js
- [4] docs: explain agent loop and sandbox boundary ↗ vercel/eve
