Sebastian Johansson
Sebastian Johansson
I can confirm the same issue with `await storyblokApi.get("cdn/stories", {})`. The data is pulled on the server, but the components are not rendered on the server. I think the issue...
@nedas-dev Holy shit thats a good workaround! Thanks for that fix! Since mine is in a v-for I did it as follows: ``` /* Pull data using await storyblokApi.get("cdn/stories", {})...
Does it work with subdomains for you? I cant get differentDomains to work at all.
Could be the same then? If www doesn't work, then it could simply be because its a subdomain!
I can confirm that this is being displayed both with useStoryblok and useAsyncStoryblok.
@Dawntraoz is this in the pipeline to fix?
The issue is located here: https://github.com/storyblok/storyblok-nuxt/blob/main/lib/src/runtime/composables/useAsyncStoryblok.js#L13 The if state looks at the story, which is true as long as URL is set to something (as far as I can tell,...
I too would like this to be a thing. Insane to think that nothing has happened since 2020.
~@Dawntraoz useAsyncStoryblok does not work correctly in dev mode.~   ~Maybe I should open a separate issue.~ Edit: I think I was confused back in november.
~Actually, that issue might be coming from some kind of issue in nuxt. I am not sure. It suddenly stopped happening after resaving nuxt.config.ts. Weird stuff!~ Edit: I think I...