Fix ENOENT error message in CLI

[rzhade3]

Marked version: 11.1.1

Markdown flavor: n/a

Description

This PR fixes a slight bug in the marked CLI in which the error message due to a ENOENT was bugging out the error output.

I also updated the language in the ENOENT error to better reflect the fact that the ENOENT may have been due to any of the inputted files.

Expectation

When running the marked CLI with an input file that does not exist, I expect it to print out an error containing only the relevant information.

Result

Marked was attempting to print out both error paths, and attempting to print an error object to stderr

What was attempted

The stacktrace above was remediated.

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.

• CI is green (no forced merge required).
• Squash and Merge PR following conventional commit guidelines.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
marked-website	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 25, 2024 11:09pm

[UziTech]

Looks like some tests are failing. Can you also add a test for this so there is no regression in the future?

[rzhade3]

@UziTech I've fixed the failing tests and attempted to write a test to prevent regressions, but it looked like this part of the code is currently not well tested. I seem to be running into this error whenever I attempt to pass a file as an input to the tests, that I'd appreciate some help debugging:

[UziTech]

looks like the error was in the bin test framework