Improve unhandled dev server errors

[pi0]

Describe the feature

With recent ecosystem updates, several issues surfaced that fail dev server startup, but Nitro does not provide enough context of what error is,

Only simple message like [ERROR [worker reload] [worker init] ../.nuxt/dev/index.mjs failed](https://github.com/primefaces/primevue/issues/6712#top) is currently displayed.

One simple way to find root of issues currently is to do a production build (npm run build should show more hints)

A nice solution (primefaces/primevue#6712) had been suggested by @web-dev-sam to attach error cause.

(I will be working on a PR but if anyone wanted to pick it earlier, please ping + consider helping to make a minimal reproduction to confirm our fix alongside)

Additional information

• Would you be willing to help implement this feature?

[OskarLebuda]

@pi0 I think I can handle it this week. Is that ok for you?

[OskarLebuda]

Got something like that:

The reproduction is quite simple for the Nuxt. Just add app.config.ts:

// app.config.ts

export default defineAppConfig({
  ready: ref(false),
});

ref is not defined here, so the worker will not initialize.

[OskarLebuda]

I've created 2 PR for that 🧑‍💻 for V2 and V3