How should I implement verbose logging in an npm package?
I have created an npm package (for internal use) that can be used as follows. Note the verboseLogging option.
import * as q from 'q'
var client = q.createClient({verboseLogging: true})
I have implemented the verboseLogging as plenty of console.log(...) statements.
This works well when the consumer of the package is a NodeJS command line application, but not as well when the consumer of the package is a browser.
When I consume this package in a browser application, I have needed to do something like the following to get the logs displayed to the user:
const originalConsoleLog = console.log;
console.log = function() {
// extract log message and save somewhere to be shown in DOM
originalConsoleLog.apply(this, arguments)
}
Is there maybe a better way to enable logging in an npm package that is accessible to both command line apps and browser apps?
node.js logging npm
asked Nov 21 '18 at 8:23
user1283776user1283776
3,1752155107
add a comment |
I have created an npm package (for internal use) that can be used as follows. Note the verboseLogging option.
import * as q from 'q'
var client = q.createClient({verboseLogging: true})
I have implemented the verboseLogging as plenty of console.log(...) statements.
This works well when the consumer of the package is a NodeJS command line application, but not as well when the consumer of the package is a browser.
When I consume this package in a browser application, I have needed to do something like the following to get the logs displayed to the user:
const originalConsoleLog = console.log;
console.log = function() {
// extract log message and save somewhere to be shown in DOM
originalConsoleLog.apply(this, arguments)
}
Is there maybe a better way to enable logging in an npm package that is accessible to both command line apps and browser apps?
node.js logging npm
asked Nov 21 '18 at 8:23
user1283776user1283776
3,1752155107
1
what issue is it causing?
– vibhor1997a
Nov 21 '18 at 8:30
@vibhor1997a: The only issue is that I must monkey patch console.log
– user1283776
Nov 21 '18 at 9:44
add a comment |
I have created an npm package (for internal use) that can be used as follows. Note the verboseLogging option.
import * as q from 'q'
var client = q.createClient({verboseLogging: true})
I have implemented the verboseLogging as plenty of console.log(...) statements.
This works well when the consumer of the package is a NodeJS command line application, but not as well when the consumer of the package is a browser.
When I consume this package in a browser application, I have needed to do something like the following to get the logs displayed to the user:
const originalConsoleLog = console.log;
console.log = function() {
// extract log message and save somewhere to be shown in DOM
originalConsoleLog.apply(this, arguments)
}
Is there maybe a better way to enable logging in an npm package that is accessible to both command line apps and browser apps?
node.js logging npm
asked Nov 21 '18 at 8:23
user1283776user1283776
3,1752155107
I have created an npm package (for internal use) that can be used as follows. Note the verboseLogging option.
import * as q from 'q'
var client = q.createClient({verboseLogging: true})
I have implemented the verboseLogging as plenty of console.log(...) statements.
This works well when the consumer of the package is a NodeJS command line application, but not as well when the consumer of the package is a browser.
When I consume this package in a browser application, I have needed to do something like the following to get the logs displayed to the user:
const originalConsoleLog = console.log;
console.log = function() {
// extract log message and save somewhere to be shown in DOM
originalConsoleLog.apply(this, arguments)
}
Is there maybe a better way to enable logging in an npm package that is accessible to both command line apps and browser apps?
node.js logging npm
node.js logging npm
asked Nov 21 '18 at 8:23
user1283776user1283776
3,1752155107
asked Nov 21 '18 at 8:23
user1283776user1283776
3,1752155107
asked Nov 21 '18 at 8:23
user1283776user1283776
3,1752155107
asked Nov 21 '18 at 8:23
user1283776user1283776
3,1752155107
asked Nov 21 '18 at 8:23
user1283776user1283776
3,1752155107
3,1752155107
1
what issue is it causing?
– vibhor1997a
Nov 21 '18 at 8:30
@vibhor1997a: The only issue is that I must monkey patch console.log
– user1283776
Nov 21 '18 at 9:44
add a comment |
1
what issue is it causing?
– vibhor1997a
Nov 21 '18 at 8:30
@vibhor1997a: The only issue is that I must monkey patch console.log
– user1283776
Nov 21 '18 at 9:44
1
1
what issue is it causing?
– vibhor1997a
Nov 21 '18 at 8:30
what issue is it causing?
– vibhor1997a
Nov 21 '18 at 8:30
@vibhor1997a: The only issue is that I must monkey patch console.log
– user1283776
Nov 21 '18 at 9:44
@vibhor1997a: The only issue is that I must monkey patch console.log
– user1283776
Nov 21 '18 at 9:44
add a comment |
1 Answer
1
active
oldest
votes
One of possible solutions is to check if window variable id defined. Since it only presents in a browser, you can try something like this:
if (typeof window === 'undefined') {
// we're server side, let console.log as is
} else {
// browser environment, DOM is accessible, additional logging goes here
}
answered Nov 21 '18 at 9:06
Anton PastukhovAnton Pastukhov
1978
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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%2f53407837%2fhow-should-i-implement-verbose-logging-in-an-npm-package%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
One of possible solutions is to check if window variable id defined. Since it only presents in a browser, you can try something like this:
if (typeof window === 'undefined') {
// we're server side, let console.log as is
} else {
// browser environment, DOM is accessible, additional logging goes here
}
answered Nov 21 '18 at 9:06
Anton PastukhovAnton Pastukhov
1978
add a comment |
One of possible solutions is to check if window variable id defined. Since it only presents in a browser, you can try something like this:
if (typeof window === 'undefined') {
// we're server side, let console.log as is
} else {
// browser environment, DOM is accessible, additional logging goes here
}
answered Nov 21 '18 at 9:06
Anton PastukhovAnton Pastukhov
1978
add a comment |
One of possible solutions is to check if window variable id defined. Since it only presents in a browser, you can try something like this:
if (typeof window === 'undefined') {
// we're server side, let console.log as is
} else {
// browser environment, DOM is accessible, additional logging goes here
}
answered Nov 21 '18 at 9:06
Anton PastukhovAnton Pastukhov
1978
One of possible solutions is to check if window variable id defined. Since it only presents in a browser, you can try something like this:
if (typeof window === 'undefined') {
// we're server side, let console.log as is
} else {
// browser environment, DOM is accessible, additional logging goes here
}
answered Nov 21 '18 at 9:06
Anton PastukhovAnton Pastukhov
1978
answered Nov 21 '18 at 9:06
Anton PastukhovAnton Pastukhov
1978
answered Nov 21 '18 at 9:06
Anton PastukhovAnton Pastukhov
1978
answered Nov 21 '18 at 9:06
Anton PastukhovAnton Pastukhov
1978
1978
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%2f53407837%2fhow-should-i-implement-verbose-logging-in-an-npm-package%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
1
what issue is it causing?
– vibhor1997a
Nov 21 '18 at 8:30
@vibhor1997a: The only issue is that I must monkey patch console.log
– user1283776
Nov 21 '18 at 9:44