Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide a cache invalidation endpoint for static builds #140

Open
eric-burel opened this issue Dec 14, 2021 · 0 comments
Open

Provide a cache invalidation endpoint for static builds #140

eric-burel opened this issue Dec 14, 2021 · 0 comments

Comments

@eric-burel
Copy link
Collaborator

eric-burel commented Dec 14, 2021

Is your feature request related to a problem? Please describe.

vercel/next.js#21903
https://www.reddit.com/r/nextjs/comments/p37y5r/invalidate_cache_after_post_request/
vercel/next.js#10945
vercel/next.js#10721 (comment)
vercel/next.js#22384
https://stackoverflow.com/questions/68444505/how-to-clear-delete-cache-in-nextjs

Edit: See leerob comment: vercel/next.js#11552 (comment)

Describe the solution you'd like

  • An API route that acts as a webhook to invalidate some statically rendered/ISR pages? Not sure if that works as API routes might live in a different volume.
  • Implementing A possible strategy for cache purging vercel/next.js#22384 => needs a custom server
  • Using a hidden param hack: change the hidden param value on demand (eg store it in redis or in the db), and rewrite to the URL with this param. When the param change, it force a new render.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant