Next 15 is already pretty behind when it comes to Turbopack. We shipped a file system cache for dev in Next 16.1 that helps a lot. nextjs.org/blog/next-16...
19.02.2026 20:10
👍 1
🔁 0
💬 1
📌 0
Next 15 is already pretty behind when it comes to Turbopack. We shipped a file system cache for dev in Next 16.1 that helps a lot. nextjs.org/blog/next-16...
Without agents, I likely wouldn't have made the effort to report the bug.
This worked so well because the task was easy but tedious (delete code) and trivially verifiable (compile, run, check process exit code).
Some of the best LLM uses don't involve code generation.
I found a Rust miscompilation, but the repro was inside Turbopack (huge, many crates).
It would've taken hours to minimize by hand, but I used an agent to prune code/dependencies until the repro was just 34 lines.
github.com/rust-lang/ru...
Great write-up from @sentry.io! They now support Turbopack, and in the process they were able to simplify their implementation and reduce their build time overhead! blog.sentry.io/turbopack-su...
Wow, this is really cool! Many apps spend a lot of time doing static site generation in Next.js, and need incremental solutions if we want to solve that.
I'm very interested in seeing all the places you end up using picante.
I shipped a blog post!
Variance has got to be one of the least intuitive aspects of most type systems.
Keep an eye on where the server is located, and where in the world you and your friends are. Network latency is important for games like Minecraft.
There's a whole section on this in The Little Book of Rust Macros. Your solution will form an AST that's inefficient to process. lukaswirth.dev/tlborm/decl-...
We've been dogfooding and iterating on file system caching for over a year. We didn't want to release it until it met our own high quality bar. We're excited to announce that it's now stable and on-by-default for 𝚗𝚎𝚡𝚝 𝚍𝚎𝚟.
Glad to hear it. The offer still stands to dive into the traces!
There is critical vulnerability in React Server Components disclosed as CVE-2025-55182 that impacts React 19 and frameworks that use it.
A fix has been published in React versions 19.0.1, 19.1.2, and 19.2.1. We recommend upgrading immediately.
react.dev/blog/2025/12...
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...
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.
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.
@runofthemillgeek.com Happy to help dig in, especially with traces, if that document doesn't solve it for you. My DMs are open.
Happy Halloween!
Local microfrontends support is a big deal!
You can see small spikes in October months around Next.js Conf 👀
I'm excited about the new release, and I'm looking forward to seeing the community tomorrow at Next.js Conf!
Build time cut in half after upgrading.
• next@15.4 - 1m 33s cold
• next@16-beta - 45s cold
Turbopack! Turbopack turbopack turbopack. Turbopack? Turbopack!
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!
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.
Coming soon to Turbopack in Next.js 16:
Babel configuration files (babel.config.js or .babelrc) will be automatically detected and run over your project code!
Fortunately, the breaking changes planned for 16 should be pretty minor for most people.
Did you try the codemods that Next 15 shipped with?
Next.js 15.5
• Turbopack for builds (beta)
• Node.js middleware (stable)
• TypeScript support improvements
• `next lint` command deprecation
• Next.js 16 deprecation warnings
nextjs.org/blog/next-15-5
Wrote an article about how React Server Components integrate with a bundler. It's a deep dive into how code splitting works, how RSCs eliminate network waterfalls, how environment directives like "use client" work, CSS loading, etc. Check it out! devongovett.me/blog/parcel-...
Nuxt 4.0 is here at last … and it's all about DX ✨
🗂️ app/ directory for better organisation
🔄 smarter data fetching
⚡️ a faster CLI with socket communication
🔧 improved TypeScript integration
... and a smooth upgrade experience. 💚
👉 nuxt.com/blog/v4
While investigating @rspack.dev performance in Next.js, SyMind found a simple opportunity to add caching that speeds up webpack >6%! github.com/vercel/next....
An awesome contribution for those still stuck on webpack.