Josh Junon

It's still being discussed.

@chagris this looks like a great start :) If you open up a PR and tick the box that says "allow maintainers to push commits", I'd be happy to start...

I can't either, I think `%J*` would be a special case (one of the few, if not the _only_ special case). I think `DEBUG_COLOR` should also go away, as will...

@Joshfindit the problem there is that sometimes events don't happen for hours at a time. Millisecond triviality goes out the window at that scale. Hence why we use `ms`. But...

Yep @dimitarnestorov's way is currently the "official" way of doing it and is entirely acceptable.

Yes but `self.log` shouldn't be set to anything. ``` Welcome to Node.js v17.3.1. Type ".help" for more information. > const debug = require('debug'); undefined > debug.log [Function: log] > d1...

I'm not sure what you want. If you specify a logger on individual debug instances, of course it will override the global logger. That's well defined. What behavior would you...

You're right, GitHub has a scrollbar on mobile and I missed it in your other comment. My apologies. PR welcome to fix the docs. There isn't a great way to...

It might be much more practical to just have a top level function on the `debug` instance. However, it's usually an anti-pattern to modify a package's state in a way...

Right now it's going to `stderr` FWIW. Also, why not just use shell redirection? I still think a top-level function that receives all of the raw output (that defaults to...