debug
debug copied to clipboard
debug-js
A tiny JavaScript debugging utility modelled after Node.js core's debugging technique. Works in Node.js and web browsers
I would just like to point out to the fact that when required, debug package will remove the DEBUG env variable if empty. I think it would be nice if...
Using `debug` with or without `esm` produces different formatted output using `%o` or `%O`: ```bash $ DEBUG=topic node -r esm -p 'require("debug")("topic")("out: %o", { foo: "?date=2020-01-29T14%3A24%3A44.806Z" })' topic out: {...
Ref #573, #565, #553, #456, #453, #402, #578, #526, #525, #488 Right now it's very clear that `debug` takes a subjective stance on its output format. This is unsuitable for...
Calling `enable` is disruptive to any enabled namespaces, which has changed in the recent minor version, caused by https://github.com/visionmedia/debug/pull/409 ```bash $ DEBUG=foo node -e 'var dbg = require("debug"); dbg.enable("bar"); console.log(dbg.enabled("foo"))'...
`DEBUG_DEPTH` env var has no effect. I tried values of `10`, `100`, `null`. No matter what I always get the following display: ``` 2020-02-08T22:17:01.423Z SCOPE STRING [ { email: '[email protected]',...
I made this function which console logs and writes to file but I'm not able to have the console with colors and the file output without colors ```javascript process.env.DEBUG =...
One problem we're going to be facing, now that I'm thinking about it: We will be introducing the ability to specify a custom output format with #582. This new output...
Just a minimal message to let devs know that their DEBUG_x variable couldn't be parsed
I've been using `=y` without realizing that doesn't work
The docs state that, when running `debug.disable()`, it will return the namespaces currently enabled and skipped. They are, however, often malformed. This seems to be because the `toNamespace` method only...
