-
Notifications
You must be signed in to change notification settings - Fork 294
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
π Bug Report β console.log() behaviour changed, possibly unintentionally? #1344
Comments
Yep, I had a feeling it could be this. I was going to update this ticket if it did fix the issue once that version with your fix is done building on my fork but I guess you beat me to it. |
Hey! |
Happy to report it worked π, I'm also very happy to report I'm no longer seeing a dreaded AND...the output is now to stdout! No more stderr parsing for what is a log or error. |
Starting with version v1.20231023.0.
I noticed in #1294 that the console behavior had changed.
OS
This is on macOS, and I have not tested the behavior yet on Linux.
Description
Previously, when I did a console.log it would show up in stderr (explicitly mentioning that this did NOT output to stdout to avoid confusion).
Now, when I do a console.log, it does not show up at all, even with --verbose flag, and does not show up in stdout at all.
If I change this to console.error, it will show up in the stderr as it did before.
Questions for debug
Is this intended behaviour? If it should be showing up in stdout, let me know and I'll debug on my side as my usage of workerd could be the issue in this case as I do have an "odd" way to run workerd.
Should it now be showing up in stdout, or is there a different way intended way to handle logs now?
The text was updated successfully, but these errors were encountered: