How can I stop Next.js from writing to cache after builds?

vegan_vicky

I’m doing a lot of vibe coding with Next.js 16. After every turn, Copilot tries to validate its changes by running a full project rebuild. The build itself isn’t too slow, about a minute, but it ends with a cache-writing step that’s useless during active development. As a result, the LLM and I end up spending 15–20 minutes a day just watching the “Finishing writing to cache...” message. I’ve dug through the docs, but I couldn’t find a way to...

Originally asked by Andrej Kirejeŭ on Stack Exchange (stackoverflow) (CC BY-SA 4.0).

uphilltech

Great question — answering as the UphillTech team:

That should be the Turbopack's filesystem cache; you can turn it off for builds in next.config const nextConfig: NextConfig = { experimental: { turbopackFileSystemCacheForBuild: false, }, } Read more: https://nextjs.org/docs/app/api-reference/config/next-config-js/turbopackFileSystemCache

Full answer by Emmanuel Obiechina Ikenna: https://stackoverflow.stackexchange.com/a/80008511 (CC BY-SA 4.0).

Need it done for your business? UphillTech.