Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Debug logs not showing in console
See original GitHub issueWith a standard installation INFO/WARN/ERROR/TRACE logs are showing in the console but DEBUG logs are not
code to test
this.logger.updateConfig({ level: NgxLoggerLevel.TRACE });
this.logger.info("login handle info");
this.logger.debug("login handle debug");
this.logger.trace("login handle trace");
console.log("console log");
console output
ngx-logger.js:237 2018-10-01T18:21:31.290Z INFO [main.js:2056] login handle info
ngx-logger.js:240 2018-10-01T18:21:31.291Z TRACE [main.js:2058] login handle trace
push../node_modules/ngx-logger/esm5/ngx-logger.js.NGXLogger._logModern @ ngx-logger.js:240
push../node_modules/ngx-logger/esm5/ngx-logger.js.NGXLogger._log @ ngx-logger.js:285
push../node_modules/ngx-logger/esm5/ngx-logger.js.NGXLogger.trace @ ngx-logger.js:161
push../src/app/app/login/login-form.component.ts.LoginFormComponent.handleLogin @ login-form.component.ts:27
(anonymous) @ LoginFormComponent.html:11
handleEvent @ core.js:10258
callWithDebugContext @ core.js:11351
debugHandleEvent @ core.js:11054
dispatchEvent @ core.js:7717
(anonymous) @ core.js:8161
(anonymous) @ platform-browser.js:995
push../node_modules/zone.js/dist/zone.js.ZoneDelegate.invokeTask @ zone.js:421
onInvokeTask @ core.js:3815
push../node_modules/zone.js/dist/zone.js.ZoneDelegate.invokeTask @ zone.js:420
push../node_modules/zone.js/dist/zone.js.Zone.runTask @ zone.js:188
push../node_modules/zone.js/dist/zone.js.ZoneTask.invokeTask @ zone.js:496
invokeTask @ zone.js:1540
globalZoneAwareCallback @ zone.js:1566
login-form.component.ts:28 console log
version 3.3.2
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Chrome: console.log, console.debug are not working
Click “Default levels” and make sure that "Verbose" is checked. By default it is only set to show Errors and Warnings.
Read more >Debug Logs - NOT Showing up any entries
Debug log - Not showing any entries, i was wondering if anyone else faced similar issue before. I can confirm the settings is...
Read more >Developer Console Not Showing Debug Logs
- Console shows nothing! We unticked the checkbox and it showed our logs, but in another org it did not.
Read more >Console not outputting from Debug.Log() - Unity Answers
Check to see if that particular output has been enabled in the console. You can hide certain types of messages. ... Debug.Log not...
Read more >Console app not showing info and debug logs
Console app not showing info and debug logs ... I have a Swift 3 Cocoa application that uses Apple's Unified Logging, like this:...
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
@davidfuhr, thanks for the insight. I’ve disabled the console.debug() in the project and debug messages will now be logged through console.log();
@ThisNetWorks, can you install ngx-logger@3.3.3 and see if that resolved your issue?
I think this is a similar issue like #77.
In Chrome (69.0.3497.100) TRACE messages are expanded by-default and DEBUG messages are hidden.
If you enable “Verbose” Logging in Chrome, the DEBUG message is shown, but not expandable (stack trace is not shown)
I find this behaviour confusing and, if itended, should be stated in the README.