- Issue created by @chfoidl
- Status changed to Fixed
7 months ago 10:15am 27 May 2024 Automatically closed - issue fixed for 2 weeks with no activity.
Dedicated support for Next.js environments is not needed. This unnessecarily bloats the configuration of the module.
Changing the cache webhook path to the full URL is sufficient.
The initial motivation of using environments was, that the cache may need to be invalidated per deployment.
This is NOT the case, because Vercel cache is per project and per environment, as stated here:
https://vercel.com/docs/infrastructure/data-cache#revalidation-behavior
The idea is to set the environment-specific correct URL for cache invalidation. Cache revalidation then works across all deployments in the same environment.
Fixed
1.0
Code
Automatically closed - issue fixed for 2 weeks with no activity.