Next.js 16.1: Turbopack filesystem caching for πππ is now enabled by default.
@nextjs296K followers
46,026 views
17 Comments
Comments from the original post on X (Twitter)

@nextjs
More:
71 likes

@Iam_Injamul
Great, the Tanstack wave is pushing the web forward
3 likes

@HsineGh
Thatβs a game-changer for developer velocity! Going from 3.7 seconds down to 336ms in dev mode is an incredible leap. Enabling filesystem caching by default with Turbopack removes friction and keeps the focus on building, not waiting. Well done, Next.js team.
2 likes

@Manixh02
Lessss go
1 like

@maciejtrebacz
Finally! β€οΈ

@rutsukun
When will the turbopack come out of the beta?

@PietroMontaldo
That speedup is absolutely wild.

@ajthakur_
@grok how to disable it ?

@Maybesuraj
I am facing this issue - I dont use - useSearchParams anywhere in my code. using nextjs - 16.1.1 this error comes when using vercel/analytics with cache components

@SuperKindaBreed
Nice improvement @nextjs π₯π₯

@Joker4mas
Waw beautiful

@SmitterHane
I rewrote a codebase to remix. And now I regret since they announced they'll be dropping React in later versions. Do you have a migration tool because I can't imagine the effort for rewriting codebase again!

@Dendy__F
Woww

@ozqurozalp
I was also wondering why my Tailwind classes werenβt being reflected in the DOM

@PandelisZ
Thanks santa

@YashSolanki_
that was quick fr

@robdvr
solid DX improvement, ty!