Pretty print ENOENT errors on cli

[mccraveiro]

Marked version: master branch

Markdown flavor: n/a

Description

Hide the JS stack trace on CLI errors

• Fixes Bad CLI error output when outputting to nonexistent directory #205

Contributor

• Test(s) exist to ensure functionality and minimize regression (if no tests added, list tests covering this PR); or,
• no tests required for this PR.
• If submitting new feature, it has been documented in the appropriate places.

Committer

In most cases, this should be a different person than the contributor.

• Draft GitHub release notes have been updated.
• CI is green (no forced merge required).
• Merge PR

[UziTech]

I'm not sure if this is the correct solution. It would be easier to debug with the stack trace.

If we want to fix #205 we should catch that error and show a relevant message.

[mccraveiro]

@UziTech What message would you show on #205 situation?

I'm not sure that debugging is something one would do while using the cli.
Should we use NODE_ENV to show the stack when in development mode?

[UziTech]

could be something like

marked: output to nonexistent_dir/test.html: No such directory

The way this PR is right now the output would be

Error: ENOENT, open 'nonexistent_dir/test.html'

which is not much more helpful.

[mccraveiro]

@UziTech done :)

[styfle]

LGTM 👍