fix: refactor the async composable to use native fetch and useState only

[Dawntraoz]

Refactor the useAsyncStoryblok composable to use useState and be able to handle errors on the page level.

[Dawntraoz]

@alvarosabu @alexjoverm I need your help to review why when we generate the static version, the error page is not shown, but it works fine locally :S I've already tried so many things but no luck, I guess I need some fresh eyes on it <3

[alvarosabu]

need your help to review why when we generate the static version, the error page is not shown, but it works fine locally :S I've already tried so many things but no luck, I guess I need some fresh eyes on it <3

I think the error page is a feature only for SSR and SPA, since it's not a route (is on the root directory, not in the pages directory) the command npm run generate will not prerender it.

For static I guess you would need to add an error page on pages and just deal with the error handling manually

[annejan89]

bump, without this PR Nuxt3 with Storyblok is useless

[github-actions]

🎉 This PR is included in version 5.6.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀