`debug.enable()` flushes enabled namespaces
See original GitHub issueCalling enable
is disruptive to any enabled namespaces, which has changed in the recent minor version, caused by https://github.com/visionmedia/debug/pull/409
$ DEBUG=foo node -e 'var dbg = require("debug"); dbg.enable("bar"); console.log(dbg.enabled("foo"))'
=> false
Issue Analytics
- State:
- Created 7 years ago
- Reactions:4
- Comments:24 (10 by maintainers)
Top Results From Across the Web
debug.enable() flushes enabled namespaces #425 - GitHub
The new implementation allows full control (i.e. override of the original DEBUG settings), which seems desireable (even more in the context ...
Read more >Trace and debug - C# | Microsoft Learn
This article describes how to trace and debug in Visual C# and provides some sample steps to explain related information.
Read more >Debug-level NPM | npm.io
DEBUG, Enables/disables specific debugging namespaces ; DEBUG_LEVEL, ERROR, WARN, INFO, DEBUG, sets debug level ; DEBUG_COLORS, true/false, display colors (if ...
Read more >@dabh/diagnostics - npm
Tools for debugging your node.js modules and event loop. Latest version: 2.0.3, last published: 9 months ago. Start using @dabh/diagnostics in your project ......
Read more >keepalived — Debian testing
-s, --namespace=NAME: Run keepalived in network namespace NAME. ... --debug[=debug-options]]: Enables debug options if they have been ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@mblarsen Definitely not a wontfix, it’s just a breaking change and requires a lot of work.
The new implementation allows full control (i.e. override of the original
DEBUG
settings), which seems desireable (even more in the context of changing this dynamically later on, see issue #433 ). I submit that the main problem here is that public methodenable()
is not documented. Actuallydebug
lacks an API reference document – does obviously not prevent it from being appreciated and widely used, but makes integration with other tools more difficult…