-
Notifications
You must be signed in to change notification settings - Fork 942
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature] enable/disable debugging dynamically #433
Comments
Please try out v3.0.0, which includes bf88540. |
Thanks, will do! Initial feedback in the meantime:
All the same, thank you for considering and implementing my request :-) |
I use debug via browserify-as-a-service build(version 3.1.0) and set localStorage. What should I do to disable debug when publish on line? |
Is it possible to do something like that by for example re-exporting debug env. variable ? |
@tasoss No, as that is a limitation of the operating system. You cannot change an environment variable from outside a process. |
Often when one is investigating a 'live' issue, one would rather not restart node to enable debugging: this might make the problem disappear until it is triggered again later. Instead debug configuration should be alterable dynamically through some kind of listener (e.g. file watch, socket –the implementation of the listener is not the purpose of this issue, though that would make a nice addition!).
Support for such dynamic changes would be easy to add in
debug.js
, here the output ofdiff -n
for the current codebase:With above one can change the debug settings from any place in the code using the same values as passed through the
DEBUG
environment variable at initialization time:See also issue #419 (and possibly #416 and #425).
The text was updated successfully, but these errors were encountered: