GQL is executed before useRoute about nuxt-graphql-client HOT 1 CLOSED

@ririen The issue faced here was that recent changes to Nuxt caused the client side runtimeConfig to resolve incorrectly, hence the module wasn't able to execute properly on client side. It should be fixed now that nuxt/framework#4267 is merged.

Also, I had a look at your reproduction and just a few points to make note of:

• when using useAsyncData on dynamic pages you have to ensure that the key is unique per page. Using an already populated key will result in stale data across pages.

- const { data, error } = await useAsyncData("starlink", () =>
+ const { data, error } = await useAsyncData("starlink" + <PAGE_KEY>, () =>
  GqlLaunches({ limit: route.fullPath.replace("/", "") })
);

• The variable type for limit is supposed to be an Int, as opposed to string. So that would also cause the query to fail

- GqlLaunches({ limit: route.fullPath.replace("/", "") })
+ GqlLaunches({ limit: Number(route.fullPath.replace("/", "")) })

from nuxt-graphql-client.