Steven Vachon

Try installing the v0.8.0 (pre-release) branch: ```shell npm install https://github.com/stevenvachon/broken-link-checker#v0.8.0 ``` A lot has changed and it may have been fixed (?).

@howar31 sorry about that. I'd pushed my incomplete changes for `file://` which had an error in it. It should work now. If it doesn't work, you could try the previous...

Because the error isn't used. It simply moves onto the next page.

I'm only merging PRs to master branch right now. All other work is being done in v0.8.0 I haven't worked on this in a while, though. Looking to return to...

Thanks! Forgot about that one.

Interesting. A temporary solution would be to hit your site harder—if it can take it—with [options.maxSocketsPerHost](https://github.com/stevenvachon/broken-link-checker#optionsmaxsocketsperhost) (not currently available to the CLI).

Didn't Chrome remove these warnings?

Yes, it's caused by a navigable link to an image. The checker expects it to be an html document.

The mime match is necessary for not parsing a resource as html. There's currently no nice way of avoiding the error, though. You can create a custom logger with the...

Oh yeah, forgot about that option. Those keywords, however, will block domains, usernames, passwords and directories that contain such. I don't know if this will be fixed in 0.8.0 or...