-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Better error output #53
Comments
Looks nice, but kind of too heavy. Will be cool to find something lightweight and focusing only on pretty-printing errors. |
By install size? It is almost same install size of chalk (#52) due to actually using it :D Anyway this might be helpful for formatting stack to reduce verbosity: |
Also from the screenshot looks like it not printing code snippet there error thrown. Will be cool to have code also printed as it does in standard error printing. |
Hmm, reading and printing code around could be nice. But it involves a more complex setup to try reading from file-system using a search path since usually stack traces are not absolute or relative to cwd also we may use source-map to reverse to original source. Please let me know about your decision would be happy to help to implement either directly in zx or as a consola reporter (extending fancy for code-snippet support). Consola had been battle-tested for a long time in different setups and the core overhead is not that much comparing to essential infra is providing for the same purpose of improving CLI output. |
Both ways are fine. |
Errors mostly okay now. |
Will be cool to add colors to error output of uncatched errors.
The text was updated successfully, but these errors were encountered: