Full static site generation support with no backend call on client side

[idflood]

Hi,

I'm trying to publish a website with full static site generation, and I would like to avoid any call to the graphql server from client side.

On first page load it currently works as expected, there is no call to the graphql endpoint and the data is loaded from the payload.js.

But once the user navigate to another page then the graphql request is made. If the page is then refreshed it loads the data from payload. As I understand from the "payload rendering support" pull request it should already be implemented and working on the Nuxt side, including the "Load payload on navigation". (found the unit test about this use case in the merged pull request)

Is it something that is implemented on nuxt-graphql-client? Or is there anything wrong with my setup?

build command: npx nuxi generate

nuxt.config.ts

export default defineNuxtConfig({
  ssr: true,
  modules: [
    'nuxt-graphql-client',
  ],
  …

to load data in files

const data = await useAsyncGql({
  operation: 'contentByUri',
  variables: {
      uri: id,
      idType: id_type,
      preview: preview
  }
});

[idflood]

My issue was related to inconsistent slug handling in my catchall page, and probably different and/or wrong response from the graphql backend.

After making sure the "full slug" has leading and trailing slashes the static site generation is working as expected.

[idflood]

Finally found out that it is also related to the issue here about GqlInstance vs useAsyncGql behaviour: #283