next.js

4250c5b3 - feat(turbopack): Invalidate the persistent cache upon panic (#80225)

feat(turbopack): Invalidate the persistent cache upon panic (#80225) This is intended as a band-aid "fix" for persistent caching where issues stick around after restarts of the development server. It builds on top of the same codepath we're using for the explicit cache clearing button in the devtools. As part of this work, this adds a centralized registry for dynamically-registered panic hooks. ## Notes & Next Steps - I'll disable this behavior for Vercel employees in front, so that we continue to get valuable bug reports. - I'll follow up with some warning message in the terminal so that the subsequent restart of `next dev` will warn the user that the persistent cache was cleared and that's why build may be slow. - We've got a some in-progress work handed to me from @wbinnssmith for better logging of anonymized (uncaught) panics to telemetry, so that should be useful in cases like this. - Yes, this will still invalidate the cache on caught panics. I'm not 100% sure that's the behavior we want, but I think it is. ## Test Plan Built with: ``` pnpm pack-next -p ~/front/apps/vercel-site cd ~/front pnpm i pnpm turbo --filter=vercel-site dev ``` Restarted a few times and looked at the persistent cache files and saw that they keep accumulating. Then, deleted a random `.sst` file, restarted, and observed a bunch of panics. Saw that the invalidation file was written. Restarted the server again and saw that it recovered itself by clearing the cache.