Use console.debug() instead of console.log() where available (e.g. browsers)
See original GitHub issueCurrently debug
output in the browser gets console.log()
'd.
However, browsers have a console.debug()
call (nonexistent in Node.js, of course) that would group all debug
output into its own category, perhaps making it easier for debugging in the browser when trying to look at regular application output.
Relevant lines:
https://github.com/visionmedia/debug/blob/master/src/browser.js#L112-L114
Thoughts?
Issue Analytics
- State:
- Created 5 years ago
- Comments:12 (6 by maintainers)
Top Results From Across the Web
Use console.debug() instead of console.log() where available ...
Currently debug output in the browser gets console.log() 'd. However, browsers have a console.debug() call (nonexistent in Node.js, ...
Read more >console.debug() - Web APIs - MDN Web Docs
The console.debug() method outputs a message to the web console at the "debug" log level. The message is only displayed to the user...
Read more >How to stop using console.log() and start using your browser's ...
In order to debug this in Chrome, you need to get used to using DevTools. To open Chrome Developer Tools, press Command+Option+I (Mac)...
Read more >Using console.log() debugging in Visual Studio Code
Using the new in-built JavaScript debugger in Visual Studio code you can use the browser developer tools Console right inside the editor.
Read more >Chrome: console.log, console.debug are not working
log statements to my Javascript, and nothing was displaying in the console. Problem turned out to be due to browser caching... it wasn't...
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 FreeTop 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
Top GitHub Comments
console.debug()
is available in Node from version 8, and would also be filterable with inspector tools if node is run with--inspect
.@PieerePi That is definitely chrome’s problem, not ours. This library isn’t built for only chrome.
Locking this as I don’t think there’s much more discussion to be had here.