I’m using Nuxt 3 with Sanity and hosted on Netlify and have always ran npm run generate to serve SSG which requires a redeploy after content/data changes. This has always generally worked fine. However recently I had to serve a build as SSR using npm run build.
So with SSR, using npm run build, if I make a change on Sanity it should be affected on the production site almost immediately, right? Each page visit should have the most up to date content (no need for a redeploy).
I have useCdn set to false in my nuxt.config.js for Sanity and I query my data using the composable useSanityQuery.
It’s bugging me out because I thought I maybe just didn’t understand SSR (as it’s my first site as SSR rather than SSG) and it can’t be Sanity as locally it’s correct and redeploying it fixes it.
Can anyone advise whether I’m completely misunderstanding SSR npm run build or should the production site be showing live changes within a reasonable timeframe? The changes never come through.
Attached is what Netlify have responded with.
