It's about time for another step in bringing debug up to date - the 5.x major release.
I know it hasn't been a long time since 4.x was released, and I'm aware that its release kind of forced.. pushed.. nudged users to update their best practices.
Here's what to expect from the 5.x release:
debug versions for formatting and pluggability upgrades (#644).enable() (#425, #636, #737)console.debug() in the browser where available (#600)Any chance we can get the issue fixed where you have
.env
DEBUG=*
And you run babel-node -r dotenv/config ./index.js
As right now this won't work
@OllieJennings #705 please search next time.
@OllieJennings, that issue was closed prematurely, but it is not fixed. I switched back to debug@3 until the issue will get some attention and will be fixed. I suggest you to do the same thing.
Please, there's no reason to post in two separate places about a closed ticket. Keep all discussion about that there - posting on the roadmap issue isn't going to get my attention any faster, I look at all issues regardless of urgency.
Just to confirm, the 5.x roadmap stipulates that the module will use console.debug for Node.js environments as well, correct? The description in the OP here is different than that of the linked issue.
@getsnoopy It'll be configurable. If you want to use something other than console.debug you would make your own log handler. That's defined in #556.
@MRCnicolas Votre commentaire n'a rien 脿 voir avec ce d茅p么t Git. De plus, je ne parle pas fran莽ais.
Most helpful comment
@OllieJennings #705 please search next time.