Closed kastentx closed 4 years ago
I didn't see that these had been approved before losing write access 😿
If anyone wants to merge and republish to npm
it should be all good to go, and pretty straightforward.
somehow 🤷 this got lost/dropped. i am closing as a recent refactor/update addressed similar issue.
This adds the 'offending' filename to error output for dir scans, along with a general refactor of the error message contents.
With these changes, if a scan is run on a directory containing a corrupt image file, like in the example given in the open issue, the output is
Running the tool on that file directly:
Fixes #5