Evan Pierce
Results
2
comments of
Evan Pierce
it looks like they introduced a cache for hot reloads thats on by default. disabling this fixes the issue. https://nextjs.org/docs/app/api-reference/next-config-js/serverComponentsHmrCache
> Could you create an issue in the next.js repository? Yes and I appreciate your considerate response. I'll see to it sometime tomorrow.