Skip to content

Bug: [BUG] Firefox logs do not interpret char codes #317

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.

Sign up for GitHub

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

Jump to bottom
Open
wsw70 opened this issue Apr 18, 2025 · 1 comment
Open

Bug: [BUG] Firefox logs do not interpret char codes #317

wsw70 opened this issue Apr 18, 2025 · 1 comment
Labels
bug Something isn't working

Comments

@wsw70
Copy link

wsw70 commented Apr 18, 2025 •
edited
Loading

Describe the bug
When logging client-side, the logs show ANSI sequences (car sequences for colors, font weights, ...) instead of the the effect of that sequence (like it is on server side)

To Reproduce

Log on a client page

Screenshots

This is what is visible verbatim in the console:

�[37m2025-04-18 12:07:09.687�[39m�[0m�[0m	�[32m�[1mDEBUG�[22m�[39m�[0m�[0m	�[37m/_nuxt/node_modules/.cache/vite/client/deps/tslog.js:926�[39m�[0m�[0m�[1m�[37m�[39m�[22m�[0m�[0m	route sequence: /date → /events

Additional context

The same problem is on Safari: #297

Node.js Version
v22.14.0

OS incl. Version
Windows 11, Firefox 137
@wsw70 wsw70 added the bug Something isn't working label Apr 18, 2025
@wsw70 wsw70 mentioned this issue Apr 18, 2025
Open
@wsw70
Copy link
Author

wsw70 commented Apr 18, 2025

Also see #277 (comment)

@wsw70 wsw70 mentioned this issue Apr 18, 2025
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@wsw70