fix(vite): include id and stack in vite-node fallback error handler

[danielroe]

🔗 Linked issue

ref nuxt/nuxt#14909

❓ 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 adds more info in the event of minimal error data. In the linked issue, error data is:

const errorData = {
  code: "ERR_MODULE_NOT_FOUND",
}

That's enough to thwart our formatter.

This PR adds stack + reason fallbacks, transforming it to:

Admittedly probably the stack isn't helpful in this case, but at least the error message tells us the module that couldn't be fetched. Alternatively, maybe we could directly throw the error if we only have a code in errorData?

📝 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	c8bf713
🔍 Latest deploy log	https://app.netlify.com/sites/nuxt3-docs/deploys/6324bc24890e120008731618

[pi0]

I've made #7589 for a better normalization approach. I think we can change this PR to make fatal errors (unhandled while normalizing) to include module id in the message. But reason is internal preserving it will be confusing.

[danielroe]

Sure 👍 Also happy to close this and we can do it all in your linked PR.

[pi0]

I've double-checked now. Unless formatViteError fails (which is solved with other PR), we show 500 error (network error actually) with path to module id. That should only happen in rare cases of internal error. we could still show moduleId in fallback

[pi0]

Improved fallback including id:

(note: this is not real! I had to make an intentional bug to the format error to produce above. just in case we missed something yet for normalization)