Next.js fixes Turbopack imports, devtools, benchmarking
Turbopack now respects module-sync exports and external package subpaths; devtools detects renamed VS Code macOS binary; benchmarking adds percentile comparison and retry logic.
May 28, 2026
Summary
These fixes reduce friction in build tooling and local development iteration: external package imports work correctly, editor launch detection doesn't fail on macOS, and benchmark results become more reliable. Cumulative effect is fewer surprises during development.
Why it matters
These fixes reduce friction in build tooling and local development iteration: external package imports work correctly, editor launch detection doesn't fail on macOS, and benchmark results become more reliable. Cumulative effect is fewer surprises during development.
Implementation verdict
Cherry-pick relevant fixes into your Next.js version if you hit the specific issues (Turbopack subpath imports, VS Code launch, benchmark flakiness). Otherwise wait for the next stable release. Low friction to adopt once released.
Sources
- 1.Turbopack: fix subpath imports pointing to external packages
- 2.fix(devtools): detect VS Code renamed macOS binary in launch-editor
- 3.devlow-bench: percentile-based comparison and run retries
- 4.Turbopack: respect the module-sync export condition
Dev Signal
Get briefs like this in your inbox — free, 3x a week.
100+ sources compressed into one 4-minute read. Ranked, cited, implementation-ready.