Tim Neutkens

No. It works by default, the default is using Turbopack. You explicitly opted into webpack in your application 🙂

It's using webpack which has different limitations 🙂

By default Next.js uses Turbopack. webpack is opt-in only for backwards compat

Please correct the record / delete the incorrect information 🙂

Proof that the icon import you showed works as-is: 8rrzh7-3000.csb.app

Sandbox: codesandbox.io/p/devbox/8rr...

And screenshot:

This is not true. You can import .css files anywhere in Next.js with App Router.

The Tailwind loader works in Turbopack 😄 That's what I created it for in the first place.

The image will be used to create a false narrative, and you now know the image is incorrect. Best thing you can do at this point is fix the mistake instead of letting it get out there.

I'd recommend deleting and starting over with a new thread without results, it only has 12 likes so far. Enough room to correct the record at this point.

Otherwise you'll be undermining your own work / credibility of the work, which is the opposite of what you want.

Happy to join.

If the first interaction with framework authors is spreading charts that are wrong you're not setting yourself up for success here. Hurts your credibility a lot.

We already have to deal with enough misinformation being posted.

I'm expecting the original post will be deleted? Now that you know it's inaccurately showing frameworks performance.

It's very disappointing that you end up sharing numbers you know are not final yet. They will be misused to create a false narrative.

Before working on anything else I'd highly recommend first making sure that the results are actually correct, because the current setup is not as evidenced by my PR. Check with framework authors first.

Fix Next.js app to match other frameworks by timneutkens · Pull Request #94 · e18e/framework-tracker This is why it's so important to not share benchmark results on social media without verifying you did set up the apps to be a correct comparison of the same application. You set it up to do mo...

Hey Alexander,
The comparison is not doing the same work and added additional overhead in the Next.js implementation.

I'm disappointed you did not reach out to verify these before just sharing such results on social media. You know full well people will misuse these.

PR: github.com/e18e/framewo...

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.