useStoryblok and useAsyncStoryblok doesnt support being used outside of setup because bridge needs onMounted

[SebbeJohansson]

Since both useStoryblok and useAsyncStoryblok require it being used in setup, it is not possible to get proper routing when using app.vue instead of pages

The point behind me wanting to use my own routing instead of vue-router (which is what the pages folder in nuxt uses) is to save on bundle size. The way I need to do the route check might be a bit special since I need to support fetching from multiple CMS' in my application.

Expected Behavior

I would expect useStoryblok and useAsyncStoryblok to work properly in for example watchEffect so that I can watch on route changes.

Current Behavior

I get warnings about onMounted being used outside of setup, which I think is coming from the bridge.

Steps to Reproduce

1. Create a new Nuxt3 project from scratch.
2. Add fetching from storyblok using useStoryblok or useAsyncStoryblok inside a watchEffect.

Full disclosure, this could all just be from me trying to do weird stuff

[SebbeJohansson]

Here is the places where i use it in my weird project:
https://github.com/SebbeJohansson/Vrtx.ContentSystem/blob/main/composables/usePageFetch.ts#L17-L25
https://github.com/SebbeJohansson/Vrtx.ContentSystem/blob/main/composables/useStoryblokFetch.ts
https://github.com/SebbeJohansson/Vrtx.ContentSystem/blob/main/app.vue#L3

[Dawntraoz]

Hi @SebbeJohansson, you can always use useStoryblokApi and the useStoryblokBridge composables separated in this case.

For now, I will close this one, and we will work on making the module work on the server side by allowing this feature -> #440