Sergey Ermakovich

@alex-statsig caching NPM modules usually negatively affects build performance, because you spend more time on extracting and saving cache back compared to just not using cache and simply downloading packages...

We are also experiencing this issue. The worst thing is that fetch requests triggered by revalidation are NOT cached during server action execution/rendering phase. Cache will be fulfilled ONLY during...

@gnoff > Additionally all the other ways fetches can be cached in Next.js should still work (`{ cache: 'force-cache'}` or `{ next: { revalidate: ... } }`, etc...) I'm not...

> The `(hard refresh)` indicates that you likely have the "Disable cache" checkbox checked in your browser's dev tools. In this case Next.js [explicitly bypasses caches](https://nextjs.org/docs/app/api-reference/functions/fetch#hard-refresh-and-caching-in-development). @unstubbable nope, this is...

yep, will do. Thank you.