Nuxt•2y ago

Nuxt/Sanity/Netlify SSR not showing up to date data issue...

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.

18 Replies

manniL•2y ago

@rich What command do you use to deploy? Did you set up any route rules?

richOP•2y ago

Thanks so much for the reply @manniL / TheAlexLichter base is web, build command is npm run build and publish directory is web/dist And no route rules I also ran npm run preview locally and the Network requests are the same If I update Sanity and test locally when using npm run preview it doesn't show the updates (same as on Netlify in prod) Should the Network tab for SSR and SSG look similar (almost identical)? I'm comparing an SSG site I just launched with this SSR site that's having the issue and the Network tab looks very similar What's also strange is if I exit npm run preview and update @nuxtjs/sanity to 1.8.3 (from 1.8.0) then npm run preview again... the change in Sanity still isn't there. I'd have assumed on npm run preview it would've shown me the most up to date data... Almost like a redeploy...

manniL•2y ago

no problem! I am not very experienced with the sanity module to be fair but: Did you provide a token? otherwise, useCdn is set to true

manniL•2y ago

https://github.com/nuxt-modules/sanity/commit/68faefaf648da3cc1eedff37df8d106ca3cd8fcb

GitHub

fix: enable useCdn at runtime if no token is available · nuxt-modul...

richOP•2y ago

This is an extract from my nuxt.config file... at the bottom I've explicity set useCdn to false...

export default defineNuxtConfig({

   ...
    
    sanity: {
        'projectId': process.env.SANITY_PROJECT_ID,
        'dataset': process.env.SANITY_PROJECT_DATASET,
        'apiVersion': process.env.SANITY_API_VERSION,
        'useCdn': false
    }

})

export default defineNuxtConfig({

   ...
    
    sanity: {
        'projectId': process.env.SANITY_PROJECT_ID,
        'dataset': process.env.SANITY_PROJECT_DATASET,
        'apiVersion': process.env.SANITY_API_VERSION,
        'useCdn': false
    }

})

manniL•2y ago

Two things: You should set the "env"-based things via runtimeConfig as described here https://sanity.nuxtjs.org/getting-started/configuration#runtime-configuration (Also take care of how you name the runtimeConfig things - see https://www.youtube.com/watch?v=_FYV5WfiWvs) and you need a token ( token: process.env.NUXT_SANITY_TOKEN,), otherwise useCDN will be set to true

richOP•2y ago

So I should be generating an API token in Sanity and using that even if I explicity set useCdn to false? Weird!

manniL•2y ago

So I should be generating an API token in Sanity and using that even if I explicity set useCdn to false? Weird!

Because I assume you can't use the non-CDN version without a token, but as mentioned, I don't know much about sentry 😋

richOP•2y ago

What's even weirder is that Vue Telescope states the Deployment is 'Static'

manniL•2y ago

do you have a link to your app?

richOP•2y ago

https://www.gouxstudio.com – thanks so much for looking

Goux Studio New York makes contemporary furniture and objects. The Plus Collection is a family of everyday items all designed around the same plus-shaped extrusion, including wall-mounted nightstands, mirrors, planters, shelves, and hooks—practical and versatile pieces that display an understated and timeless character.

manniL•2y ago

yup

manniL•2y ago

seems like the deployment is static indeed

manniL•2y ago

which must be the main issue make sure your build command is not running nuxt generate but nuxt build (though netlify should auto-detect that)

richOP•2y ago

richOP•2y ago

I'm so confused 😩 It's the same if I do npm run build locally then use node .output/server/index.mjs I'm guessing window.NUXT.prerenderedAt on a SSR site should be the time you visited the page? Or I guess serverRendered would be true Okay I figured this out... I had this in my nuxt.config.js for the sitemap.xml which was prerendering everything... commented this out and it now works as expected

nitro: {
  prerender: {
    crawlLinks: true,
    routes: ['/', 'sitemap.xml'],
  },
},

nitro: {
  prerender: {
    crawlLinks: true,
    routes: ['/', 'sitemap.xml'],
  },
},

So now I need to work out how to have a sitemap on SSR haha

manniL•2y ago

@rich disable crawlLinks and you can even remove the routes there, then the sitemap will be updated "on the go"

richOP•2y ago

Thanks for all the help @manniL / TheAlexLichter

Gaming

Programming

Nuxt/Sanity/Netlify SSR not showing up to date data issue...

Did you find this page helpful?