fix: correctly checks so that error value exists before trying to show one in useAsyncStoryblok

[SebbeJohansson]

• Fix: Checks so that error.value?.response is true-ish before trying to display an error with nuxt - Getting error folowing setup tutorial Unhandled error during execution of setup function #210
• Feat: Changes how the playground refers to the module so that its easier to debug.
• Feat: Adds a slug fallback page so that its possible to test against 404 slugs.

[alvarosabu]

@SebbeJohansson pipelines broke, can you please check if the lock is updated?

[SebbeJohansson]

@alvarosabu I think that issue is coming from my change in the playground where I am including the storyblok-nuxt package locally instead of using the public version (or what ever it was doing before).
I can fix the package file, but I would love it if you could give me some feedback on whether or not you think its a good idea to locally refer to the package.

[alvarosabu]

Set the playground ref to "0.0.1" to avoid issues

[SebbeJohansson]

@alvarosabu can you confirm that playground works at all for you if you do that? Cause it ain't for me! 😁😅

[SebbeJohansson]

I reverted the change anyways, but the pipeline still failed.

[SebbeJohansson]

Something went wrong when i commited this because the useASyncStoryblok composable looks weird as all hell.

Maybe something went wrong when I merged main. Not entirely sure.

I have updated it and it should now run fine. I am still having the issue above when I reverted the package.json file. Not sure what to do.

[github-actions]

🎉 This PR is included in version 5.4.2 🎉

The release is available on:

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

Your semantic-release bot 📦🚀