How to turn off logging for superagent in node.js?
up vote
0
down vote
favorite
besides monkeypatching console.log and ignoring lines with superagent, is there a way to disable built-in logging in superagent when running in node?
currently, it always logs something like this:
superagent GET https://example.com/test?query=blah -> 200 +5ms
I can't find this in the docs.
javascript node.js console superagent
add a comment |
up vote
0
down vote
favorite
besides monkeypatching console.log and ignoring lines with superagent, is there a way to disable built-in logging in superagent when running in node?
currently, it always logs something like this:
superagent GET https://example.com/test?query=blah -> 200 +5ms
I can't find this in the docs.
javascript node.js console superagent
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
besides monkeypatching console.log and ignoring lines with superagent, is there a way to disable built-in logging in superagent when running in node?
currently, it always logs something like this:
superagent GET https://example.com/test?query=blah -> 200 +5ms
I can't find this in the docs.
javascript node.js console superagent
besides monkeypatching console.log and ignoring lines with superagent, is there a way to disable built-in logging in superagent when running in node?
currently, it always logs something like this:
superagent GET https://example.com/test?query=blah -> 200 +5ms
I can't find this in the docs.
javascript node.js console superagent
javascript node.js console superagent
edited Nov 19 at 6:40
asked Nov 19 at 6:06
FlavorScape
4,89365492
4,89365492
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
As many Node packages, superagent uses debug to show debugging information. The problem likely occurs because debugging was enabled for all namespaces (*).
As the documentation explains, if all namespaces are included with a wildcard, some can be excluded:
process.env.DEBUG = '*,-superagent';
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
As many Node packages, superagent uses debug to show debugging information. The problem likely occurs because debugging was enabled for all namespaces (*).
As the documentation explains, if all namespaces are included with a wildcard, some can be excluded:
process.env.DEBUG = '*,-superagent';
add a comment |
up vote
0
down vote
As many Node packages, superagent uses debug to show debugging information. The problem likely occurs because debugging was enabled for all namespaces (*).
As the documentation explains, if all namespaces are included with a wildcard, some can be excluded:
process.env.DEBUG = '*,-superagent';
add a comment |
up vote
0
down vote
up vote
0
down vote
As many Node packages, superagent uses debug to show debugging information. The problem likely occurs because debugging was enabled for all namespaces (*).
As the documentation explains, if all namespaces are included with a wildcard, some can be excluded:
process.env.DEBUG = '*,-superagent';
As many Node packages, superagent uses debug to show debugging information. The problem likely occurs because debugging was enabled for all namespaces (*).
As the documentation explains, if all namespaces are included with a wildcard, some can be excluded:
process.env.DEBUG = '*,-superagent';
answered Nov 19 at 6:59
estus
64k2194201
64k2194201
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53369146%2fhow-to-turn-off-logging-for-superagent-in-node-js%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown