fix(nuxt): pass and format vite-node build errors

[antfu]

🔗 Linked issue

❓ 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

To pass down the nested h3 app's error to be handled by the main one. nodeHandler comes with its own error handling (https://github.com/unjs/h3/blob/b95ab25575e1a6c022ff40cfd731d27cb735f621/src/app.ts#L57), changed to handler so it let the error flow down.

📝 Checklist

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

[netlify]

✅ Deploy Preview for nuxt3-docs canceled.

Name	Link
🔨 Latest commit	9cfee0c
🔍 Latest deploy log	https://app.netlify.com/sites/nuxt3-docs/deploys/631323b82937a20008ddc3e3

[pi0]

Thanks for PR @antfu. Please use description for next PRs even if we internally discussed 🙏🏼

[antfu]

Added, thanks!

[pi0]

Checking more locally, it seems passing main handler is not enough. Vite node (client) throws nice object with nice trace info (id, plugin, message, name, stack, loc, pluginCode, frame). Passing it up to the dev server handler, won't help. But we could pass it down to the vite-node fetch client. There I tried to restore main error object from HTTP response and throw it in fetchModule of viteNodeRunner. But it will be only handled when we call render...

What happens is: Browser request => Nitro server => SSR => Vite Node Client (Runner) => Fetch A problematic module => Gets error object.

[pi0]

BTW comparing to legacy bundler, we were never handling build errors from server side but using an empty module. They were being then handled on client-side.

I've just pushed 808fd5b to show how similar effect works.

[pi0]

I had been testing giving error data for few cases. There is really no standard for errors coming from vite, rollup plugins and parsers such as babel used for sfc. I've made a temporary normalizer on best efforts and compatible with default error template but we should make something more standard for normalization later.

Script:

Template:

Style: