Better error output about zx HOT 7 CLOSED

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.

from zx.

I would suggest trying consola. We can hook into all console calls to catch and format both logs and errors/stacks. (in conflict with #52 but is easily solvable)

from zx.

Looks nice, but kind of too heavy. Will be cool to find something lightweight and focusing only on pretty-printing errors.

from zx.

but kind of too heavy

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:

• Parse: https://github.com/unjs/consola/blob/4477e87a5153d31d22a2692565959d90599a6b61/src/utils/error.js#L3
• Format: https://github.com/unjs/consola/blob/4477e87a5153d31d22a2692565959d90599a6b61/src/reporters/fancy.js#L31

from zx.

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.

from zx.

Both ways are fine.

from zx.

Errors mostly okay now.

from zx.