Sanity and Next.js Automatic Static Optimization

4 replies
Last updated: May 18, 2020
hey you cool cats and kittens,
I'm having a little bit of an issue with Sanity and nextJS Automatic Static Optimization.

I followed the example similar to here:
https://github.com/sanity-io/example-frontend-next-js
However every time I update my content in Sanity, I don't get the up to date data in nextJS! Am I missing something?
🤔
May 17, 2020, 5:08 PM
I'm new to ASO, I understand why the data is outdated but how would you recommend dealing with this? with Gatsby, we'd just trigger another build. I guess with this one, there needs to be a way to get nextjs to invalidate the cache on publish somehow.
May 17, 2020, 5:19 PM
Hi. If your hosting next with Vercel, in git integration section you can create a deploy hook, then make an api route in your next app that when requested would call that deploy hook, then finally in sanity project settings/api set up a webhook to your next api endpoint. So whenever sanity content is changed webhook calls your next api and it calls deployment hook - new build takes place and app gets up to date content
May 17, 2020, 7:44 PM
user G
thank you
May 18, 2020, 3:50 PM
I did just that
May 18, 2020, 3:50 PM

Sanity– build remarkable experiences at scale

Sanity is a modern headless CMS that treats content as data to power your digital business. Free to get started, and pay-as-you-go on all plans.

Was this answer helpful?