Tim Neutkens

Following up here

Why?

Next.js 16

• Cache Components
• Turbopack enabled by default
• Turbopack file system caching (beta)
• Optimized navigations and prefetching
• Improved caching APIs
• Build Adapters API (alpha)
• React 19.2

nextjs.org/blog/next-16

There hasn’t been many new bundlers 😄 proving that it works at the scale of large Next.js applications is important to us 👍

What packages are you using?

Because we decided to focus on Next.js applications first. There will be a more generic API to use the bundler in the future.

next.config.js: turbopack | Next.js Configure Next.js with Turbopack-specific options

Maybe there is a lockfile at multiple levels in the monorepo incorrectly, which makes automatic root detection detect the application directory as the root.

More info in these docs: nextjs.org/docs/app/api...

Thank you!

Saying "be honest" claims I'm lying. I'm not lying.

Everything you're bringing up so far is stuff outside of our control that we're somehow getting blamed for by you "Not using Unjs" "Not using Vite" "The React docs".

We maybe made decisions you personally don't like, that's different than evil.

We have no control over what the React team at Meta recommends in their documentation. There is no conspiracy.

It's really weird for you to claim that because we did not contribute to one project (i.e. unjs) we're somehow "hostile"? We contribute to many other projects that help everyone.

We live in a time where I couldn’t be happier about web tooling. A time of optimizing what came before, and everyone building for the web wins. We want the web to win. That includes people building with Nuxt / Nitro / Vite.

Somehow people assume that because we don’t use Vite in Next.js that we believe it’s bad. This is just not the case. It’s a good tool, it just wasn’t the tool for us to build Next.js. We had different requirements. It’s good for other things.

Choosing a different bundler because it doesn’t fit our needs is far from stubborn. The web benefits from variety of tools. You could always host Next.js yourself, just like Nuxt: next build -> next start. We’re also working with Netlify Cloudflare and others on adapters.

Yeah so far it's better in terms of bots here, except that on the other side bluesky engagement is reposted 😆

Hope you have a good day!

Like I said before, it's not about you. It's about in general. I have to deal with bots posting random engagement bait based on other people's tweets 🙂 Hope you can understand that.

Also I did not even say you were spreading fake news. I said "this is how fake news is spread" which is very different than claiming what you in particular said is fake news.

Again, you're okay 🙏 Have a good day!

You're reading way too much into this. Like I said I don't think you intended harm at all. There's a reason you deleted the post. That's totally okay. No hard feelings.

I'm guessing you think I'm mad at you? I'm not.

You shared Next.js / Turbopack DX is terrible. Which wasn’t the case. So fake news 🙂

Gotcha. I’m sure you mean well but this is quite unfortunate. This is how fake news is spread.

Guides: Debugging | Next.js Learn how to debug your Next.js application with VS Code, Chrome DevTools, or Firefox DevTools.

nextjs.org/docs/app/gui...

You can follow this to run the Node.js devtools, then go to the performance tab and capture a CPU profile, works the same way as browser CPU profile. Will show you exactly why the request was slow

`generateStaticParams` even runs async and doesn't block requests. Worth for you grabbing a Node.js CPU profile here I think. Feel free to send one over so I can take a look.

Until the "✓ Compiled / in 11ms" is with revalidate+force-static.

After that it's without anything added.

As you can see it's the same time for both.

Had the page do a fetch to an external url.

Are you using `generateStaticParams` when adding `revalidate`? If so it'll run `generateStaticParams` each request to a route that matches.

And you're dynamically rendering markdown?

In the screenshot the part of Turbopack is the `Compiled X in Yms`. The rest is individual requests unrelated to Turbopack.

So it's not Turbopack but can have a look at ISR in your app. Is this for www.openstatus.dev or something else?

Proud of the Turbopack team. This is a big milestone that we've been working towards since Next.js 15 was released. Now on towards `next build --turbopack` stable.

5/5

Performance Improvements:
As we get more real-world data we'll be able to optimize further, Turbopack will get faster over time as we identify common patterns across more applications.

4/5

Persistent Caching:
We're in the process of dogfooding disk caching at Vercel to catch edge cases, once these edge cases have been resolved you'll be able to try it out.

GitHub Issues:
Focus on fixing feedback from early adopters.

3/5

Tests:
57 tests left. Though we don't expected most applications to run into these cases.

Bundle Size:
There's some optimizations we still have to implement. Getting more data from real applications will also help in tweaking the chunking heuristics to be optimal for most applications.

2/5

Excited to bring you the first version of "next build --turbopack"!

Looking forward to seeing the results and iterating quickly towards stability. If you have feedback, let us know!

Next up:

1/5