@mtharrison @mugli this look like it meets your needs?

Having second thoughts about this, feels a bit wrong to me for a library to log to my stdout, even in warning situation. It could mess up whatever logging strategy I have in place. I wonder if there's a better way of doing this without throwing. Would it possible to use the hapi request.log()/server.log() here? Or at least use console.error() or console.warn() so it's sent to stderr.

Anyone else have a good idea?

I personally think sending it to stderr is sufficient, and I agree that sending it to stdout feels bad. I'm not totally convinced that hapi logging applies here very well. Hrm!

Thanks for the feedback! @mtharrison I considered server.log() but it seemed to run up against some of your earlier concerns that the warning may not be immediately apparent in the default case. This is because logging would have to be explicitly configured on the server (either via a plugin or the debug option) in order to see the output. Also, since this issue seems to skew toward the development cycle I don't think that a whole lot is lost by not sending the warning to server.log(). However, I had not considered how stdout could mess up other logging strategies. console.warn() seems reasonable to me. I will update accordingly if nobody can think of any final objections.

This thread has been automatically locked due to inactivity. Please open a new issue for related bugs or questions following the new issue template instructions.