Skip navigation
Next.js 16.1: Turbopack filesystem caching for 𝚍𝚎𝚟 is now enabled by default.
0:00 / 0:20

Next.js 16.1: Turbopack filesystem caching for 𝚍𝚎𝚟 is now enabled by default.

Next.js

@nextjs296K followers

Visit on X
587 likesDownloadOriginal post

46,026 views

Next.js 16.1: Turbopack filesystem caching for 𝚍𝚎𝚟 is now enabled by default. Example field test in an open-source app: 3.7s β†’ 336ms

17 Comments

Comments from the original post on X (Twitter)

  • Next.js's profile picture

    @nextjs

    More:

    71 likes

  • Injamul Islam's profile picture

    @Iam_Injamul

    Great, the Tanstack wave is pushing the web forward

    3 likes

  • Ghassen Hassine's profile picture

    @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

  • Manish Kumar's profile picture

    @Manixh02

    Lessss go

    1 like

  • mav's profile picture

    @maciejtrebacz

    Finally! ❀️

  • RutsuKun's profile picture

    @rutsukun

    When will the turbopack come out of the beta?

  • Pietro Montaldo's profile picture

    @PietroMontaldo

    That speedup is absolutely wild.

  • Ajay Thakur's profile picture

    @ajthakur_

    @grok how to disable it ?

  • Suraj Shah's profile picture

    @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

  • Kinging Chukwunonso's profile picture

    @SuperKindaBreed

    Nice improvement @nextjs πŸ”₯πŸ”₯

  • η§‘ε…ΉΒ·ζ²™θ΅«β„’'s profile picture

    @Joker4mas

    Waw beautiful

  • Hane Smitter's profile picture

    @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's profile picture

    @Dendy__F

    Woww

  • Γ–zgΓΌr Γ–ZALP's profile picture

    @ozqurozalp

    I was also wondering why my Tailwind classes weren’t being reflected in the DOM

  • Pandelis's profile picture

    @PandelisZ

    Thanks santa

  • Yash Solanki's profile picture

    @YashSolanki_

    that was quick fr

  • Rob Davarnia's profile picture

    @robdvr

    solid DX improvement, ty!