Benjamin Woodruff
@benjam.info
Software Engineer at ▲Vercel on Turbopack, formerly at Meta
https://benjam.info
https://x.com/_bgwoodruff
https://github.com/bgw
https://benjam.info
https://x.com/_bgwoodruff
https://github.com/bgw
Glad to hear it. The offer still stands to dive into the traces!
December 11, 2025 at 11:43 PM
Glad to hear it. The offer still stands to dive into the traces!
I'm happy to dive into traces with you over DMs. Often there's some minor things that can be tweaked to improve performance.
nextjs.org/docs/app/api...
nextjs.org/docs/app/api...
API Reference: Turbopack | Next.js
Turbopack is an incremental bundler optimized for JavaScript and TypeScript, written in Rust, and built into Next.js.
nextjs.org
November 23, 2025 at 10:04 PM
I'm happy to dive into traces with you over DMs. Often there's some minor things that can be tweaked to improve performance.
nextjs.org/docs/app/api...
nextjs.org/docs/app/api...
No, we've discussed it, but:
- We think the filesystem cache is a better all-around solution.
- If you have a large app, which routes should we compile?
- We're keeping an eye on memory usage, and with our current architecture, this would likely waste more memory than most users would want.
- We think the filesystem cache is a better all-around solution.
- If you have a large app, which routes should we compile?
- We're keeping an eye on memory usage, and with our current architecture, this would likely waste more memory than most users would want.
November 23, 2025 at 10:04 PM
No, we've discussed it, but:
- We think the filesystem cache is a better all-around solution.
- If you have a large app, which routes should we compile?
- We're keeping an eye on memory usage, and with our current architecture, this would likely waste more memory than most users would want.
- We think the filesystem cache is a better all-around solution.
- If you have a large app, which routes should we compile?
- We're keeping an eye on memory usage, and with our current architecture, this would likely waste more memory than most users would want.
The filesystem cache is available in beta on Next 16.0, and we're hoping to ship it as stable and on-by-default very soon (we've been working on it for over a year!). nextjs.org/blog/next-16...
Next.js 16
Next.js 16 includes Cache Components, stable Turbopack, file system caching, React Compiler support, smarter routing, new caching APIs, and React 19.2 features.
nextjs.org
November 21, 2025 at 9:15 PM
The filesystem cache is available in beta on Next 16.0, and we're hoping to ship it as stable and on-by-default very soon (we've been working on it for over a year!). nextjs.org/blog/next-16...
Regarding compilation upon navigation: It should be better in Next 16, but we are working on a couple things to address this:
- A file-system cache that persists across restarts of `next dev`.
- An alternate bundling mode that shares more work across pages, at the cost of a slower first page load.
- A file-system cache that persists across restarts of `next dev`.
- An alternate bundling mode that shares more work across pages, at the cost of a slower first page load.
November 21, 2025 at 9:14 PM
Regarding compilation upon navigation: It should be better in Next 16, but we are working on a couple things to address this:
- A file-system cache that persists across restarts of `next dev`.
- An alternate bundling mode that shares more work across pages, at the cost of a slower first page load.
- A file-system cache that persists across restarts of `next dev`.
- An alternate bundling mode that shares more work across pages, at the cost of a slower first page load.
@runofthemillgeek.com Happy to help dig in, especially with traces, if that document doesn't solve it for you. My DMs are open.
November 19, 2025 at 11:57 PM
@runofthemillgeek.com Happy to help dig in, especially with traces, if that document doesn't solve it for you. My DMs are open.
Local microfrontends support is a big deal!
October 31, 2025 at 6:20 PM
Local microfrontends support is a big deal!
You can try it out both of these features today in the latest Next.js canary:
npm install next@canary
If you run into any issues, let me know so we can fix it before Next.js 16 goes out!
npm install next@canary
If you run into any issues, let me know so we can fix it before Next.js 16 goes out!
September 23, 2025 at 3:23 PM
You can try it out both of these features today in the latest Next.js canary:
npm install next@canary
If you run into any issues, let me know so we can fix it before Next.js 16 goes out!
npm install next@canary
If you run into any issues, let me know so we can fix it before Next.js 16 goes out!
In addition to this automatic configuration of Babel, we added a new 'condition' field for controlling when manually-configured webpack loaders run in Turbopack.
It builds on top of internal functionality that we didn't cleanly expose until now.
It builds on top of internal functionality that we didn't cleanly expose until now.
Turbopack: Document new advanced `turbopack.rule.*.condition` config options by bgw · Pull Request #83246 · vercel/next.js
I'm looking for review/feedback, but DO NOT MERGE UNTIL NEXT 16.0 IS RELEASED. These APIs are not available on 15.5, and merging it now would be confusing to users. If you want to try it out, u...
github.com
September 23, 2025 at 3:23 PM
In addition to this automatic configuration of Babel, we added a new 'condition' field for controlling when manually-configured webpack loaders run in Turbopack.
It builds on top of internal functionality that we didn't cleanly expose until now.
It builds on top of internal functionality that we didn't cleanly expose until now.
Fortunately, the breaking changes planned for 16 should be pretty minor for most people.
Did you try the codemods that Next 15 shipped with?
Did you try the codemods that Next 15 shipped with?
August 20, 2025 at 5:01 AM
Fortunately, the breaking changes planned for 16 should be pretty minor for most people.
Did you try the codemods that Next 15 shipped with?
Did you try the codemods that Next 15 shipped with?
Yikes. One major difference between Turbopack and webpack is that Turbopack uses a stricter parser (lightningcss) that errors on broken css that would be silently ignored in webpack.
The new behavior is better, but the migration can be painful.
I'd love to hear if you figure out the issue here.
The new behavior is better, but the migration can be painful.
I'd love to hear if you figure out the issue here.
June 13, 2025 at 6:02 AM
Yikes. One major difference between Turbopack and webpack is that Turbopack uses a stricter parser (lightningcss) that errors on broken css that would be silently ignored in webpack.
The new behavior is better, but the migration can be painful.
I'd love to hear if you figure out the issue here.
The new behavior is better, but the migration can be painful.
I'd love to hear if you figure out the issue here.