search

debug-js / debug

A tiny JavaScript debugging utility modelled after Node.js core's debugging technique. Works in Node.js and web browsers
MIT License
11.15k stars 940 forks source link

not getting any output #837

Open twhitbeck opened 3 years ago

twhitbeck commented 3 years ago

We upgraded to 4.3.2 and are all of a sudden not getting logs in stderr (using in a node script). The regressions seems to have been caused by #799

Admittedly we're perhaps using the library not exactly in a way that it was intended to be used. We aren't setting DEBUG environment variable, so process.env.DEBUG is undefined, but our namespaces are named example-namespace* with a trailing *. These were previously logging, now they're not.

Qix- commented 3 years ago

example-namespace*

FWIW this isn't really supported, and dare I say deprecated; you should attempt to remove those ASAP.

I'll have to take a look and see, but you're the only one reporting this so I have to assume (without checking) that it's related.

ulysses2000 commented 3 years ago

ok

alexanmaddielrya commented 4 months ago

Hi, the docs debug.js say

Conventions If you append a "*" to the end of your name, it will always be enabled regardless of the setting of the DEBUG environment > variable. You can then use it for normal output as well as debug output.

If this is deprecated i would remove it.