Turbopack File System Caching feedback

[lukesandberg]

Thread for posting feedback about the file system cache for turbopack

[maiconcarraro]

Once upgraded to 16.1 it's not building on Windows env:

> next build

▲ Next.js 16.1.0 (Turbopack)
- Environments: .env.local, .env
- Experiments (use with caution):
  · clientTraceMetadata

  Creating an optimized production build ...

-----
FATAL: An unexpected Turbopack error occurred. A panic log has been written to C:\Users\xxxxxx\AppData\Local\Temp\next-panic-93eb27ba7277714b720bfebe70aea46c.log.

To help make Turbopack better, report this error by clicking here.
-----


> Build error occurred
Error [TurbopackInternalError]: create symlink to ../../node_modules/pg

Caused by:
- O cliente não tem o privilégio necessário. (os error 1314)
    at ignore-listed frames {
  type: 'TurbopackInternalError',
  location: undefined
}

It's not only related to pg, but any package, everytime it shows up a different package like pg, sharp and others. It does work fine in GH actions and Vercel deployment.

[maiconcarraro]

The build using 16.0.10 also works fine in Windows env.

[maiconcarraro]

Fixed on https://github.com/vercel/next.js/releases/tag/v16.1.1

[sandren]

Is it possible to configure the invalidation? I notice it always invalidates the cache when starting a new GitHub Codespace session even though .next data is still intact.