Better reporting

[davidanson]

Better reporting

[DavidAnson]

Glad you like it!

To your first point, check-pages is a library, so logging and error handling are generally up to whatever code is using it. The API allows you to pass console as the Host parameter for easy logging (https://github.com/DavidAnson/check-pages/blob/master/README.md#host), but you can pass something else that customizes the output if you'd like (such as by coloring it or adding pretty icons). Regarding the exception you are getting, I think that check pages handles it's own errors properly, but if you have a simple demonstration of the problem, I'd like to understand if this is actually a bug in my code.

Regarding your second point, colorization and summarization of output is something that the check-pages-cli package (https://github.com/DavidAnson/check-pages-cli) already supports. If that's relevant to your scenario, please try it out because you may find it's easier to use and maybe more friendly. :)

[DavidAnson]

Assuming the above reply was helpful, I'm closing this issue to clean up. Thanks!

[lukasoppermann]

Hey @DavidAnson, thank you for your answer. The cli is a little inconvenient as I am using it in gulp, however, I just use the logging function from there and it is perfect. For anybody who needs it:

  let host = {
    "log": function log (msg) {
      console.log(chalk.green('✔ ' +msg));
    },
    "error": function error (msg) {
      console.error(chalk.red('× ' +msg));
    }
  };

  checkPages(host, options, callback)

I believe the issues arise from redirects on my side, the page errors did not show up before I used your function. So I will investigate this further.