Tim Neutkens
@timneutkens.bsky.social
Next.js lead at Vercel, co-author of Next.js, MDX, Micro, and ncc. Opinions are my own.
Following up here
October 27, 2025 at 11:07 AM
Following up here
There hasn’t been many new bundlers 😄 proving that it works at the scale of large Next.js applications is important to us 👍
October 20, 2025 at 4:58 PM
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?
October 20, 2025 at 4:54 PM
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.
October 19, 2025 at 6:31 PM
Because we decided to focus on Next.js applications first. There will be a more generic API to use the bundler in the future.
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...
More info in these docs: nextjs.org/docs/app/api...
next.config.js: turbopack | Next.js
Configure Next.js with Turbopack-specific options
nextjs.org
October 14, 2025 at 11:38 AM
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...
More info in these docs: nextjs.org/docs/app/api...
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.
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.
July 9, 2025 at 11:56 AM
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.
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.
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.
July 9, 2025 at 11:51 AM
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.
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.
July 8, 2025 at 8:28 PM
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.
July 8, 2025 at 8:25 PM
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.
July 8, 2025 at 8:24 PM
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!
Hope you have a good day!
May 13, 2025 at 9:08 AM
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!
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.
May 13, 2025 at 9:00 AM
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!
Again, you're okay 🙏 Have a good day!
May 13, 2025 at 8:52 AM
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!
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.
I'm guessing you think I'm mad at you? I'm not.
May 13, 2025 at 8:49 AM
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.
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 🙂
May 13, 2025 at 4:30 AM
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.
May 12, 2025 at 7:44 PM
Gotcha. I’m sure you mean well but this is quite unfortunate. This is how fake news is spread.
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
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
Guides: Debugging | Next.js
Learn how to debug your Next.js application with VS Code, Chrome DevTools, or Firefox DevTools.
nextjs.org
May 12, 2025 at 7:36 PM
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
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.
May 12, 2025 at 3:43 PM
`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.
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.
May 12, 2025 at 3:36 PM
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.
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.
May 12, 2025 at 3:33 PM
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?
May 12, 2025 at 3:29 PM
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?
So it's not Turbopack but can have a look at ISR in your app. Is this for www.openstatus.dev or something else?
May 12, 2025 at 3:20 PM
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?
So it's not Turbopack but can have a look at ISR in your app. Is this for www.openstatus.dev or something else?