-
Notifications
You must be signed in to change notification settings - Fork 541
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve unhandled dev server errors #2927
Comments
@pi0 I think I can handle it this week. Is that ok for you? |
I've created 2 PR for that 🧑💻 for V2 and V3 |
@pi0 can u move that forward? |
Hi dear @OskarLebuda sorry for not updating here. I had been investigating it and found strangely issue was only happening with Nuxt (not Nitro CLI itself when we testing) The issue was that, consola was not supporting error causes. With consola 3.3 bundled into latest |
Good to know! Thanks for the update 🙏🏻 |
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
The text was updated successfully, but these errors were encountered: