You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
winston3
nodejs 10.16
Windows 10
Chrome 75.0.3770.142
This just started yesterday or today, I am not longer getting output from Winston in the Chrome Devtools console window -- the output is still showing in my PowerShell terminal window.
This is really annoying... I'm guessing it may have been a Chrome update ( nothing in my node app has changed since it was working yesterday, and I am running the same version of node as yesterday. ) The only possible change I can think of is that Chrome updated. This is happening on both of my development machines...
Has anybody else run into this and do you know how to fix it?
Additional info: It is possible I just noticed this behavior, as I just recently converted most of my app to using Winston instead of console.
I was able to work around this by using the code here: #1305
for when I am running in debug mode.
The text was updated successfully, but these errors were encountered:
winston3
nodejs 10.16
Windows 10
Chrome 75.0.3770.142
This just started yesterday or today, I am not longer getting output from Winston in the Chrome Devtools console window -- the output is still showing in my PowerShell terminal window.
This is really annoying... I'm guessing it may have been a Chrome update ( nothing in my node app has changed since it was working yesterday, and I am running the same version of node as yesterday. ) The only possible change I can think of is that Chrome updated. This is happening on both of my development machines...
Has anybody else run into this and do you know how to fix it?
Additional info: It is possible I just noticed this behavior, as I just recently converted most of my app to using Winston instead of console.
I was able to work around this by using the code here: #1305
for when I am running in debug mode.
The text was updated successfully, but these errors were encountered: