fix(nuxt): pass async-data errors through to client

[danielroe]

🔗 Linked issue

resolvesnuxt/nuxt#12885

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

This PR passes error status/message through to client side. Together with unjs/ofetch#152 and h3js/h3#213 this will enable accessing error.statusCode (which is useful for making decisions regarding 404s, etc.) and will pass a normalised error object through to client.

There will still be some differences between client + server errors because server errors are raw and not normalised with createError.

You can test with:

<template>
<div>{{ error.message }}</div>
</template>
<script setup>const { error } =awaituseFetch('https://jsonplaceholder.typicode.com/404')onMounted(() =>console.log(error.value))</script>

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[codesandbox]

Open in CodeSandbox Web Editor | VS Code | VS Code Insiders

[netlify]

✅ Deploy Preview for nuxt3-docs canceled.

Name	Link
🔨 Latest commit	79f21bb
🔍 Latest deploy log	https://app.netlify.com/sites/nuxt3-docs/deploys/635a891f05b2c500095e6f45

[wobsoriano]

Finally 😅

[szulcus]

I'm very happy about this! ❤️