Winston 3 Console Transport removing whitespace
See original GitHub issueI have come across this this while trying out winston 3.
OS: Macos 10.13.4 Terminal: iTerm2 or Terminal.app Winston: 3.0.0-rc5 Node: 8.11.1
I am using a custom formatter that is setting options[Symbol.from('message')]
before returning it to winston. I am providing to that transport the following string (an example):
\u001b[36m\u001b[4m*INFO * ↳ \u001b[24m\u001b[39m pid: \u001b[33m13071\u001b[39m
But sometimes both newlines and initial whitespace are being ignored when writing to the console. This doesn’t seem to happen when running on linux.
Issue Analytics
- State:
- Created 5 years ago
- Comments:10 (3 by maintainers)
Top Results From Across the Web
nodejs winston - Logging with multiple arguments
Since Winston API doesn't work like console.log , therefore a workaround would be to create a wrapper function which utilizes util.format in ...
Read more >How to use the winston.remove function in winston - Snyk
To help you get started, we've selected a few winston.remove examples, based on popular ways it is used in public projects.
Read more >Winston Logger Filename Error Undefined - ADocLib
For one there's no way to disable console.log calls. used to send log messages to their destination is known as a transport and...
Read more >kiS - River Thames Conditions - Environment Agency - GOV.UK
Pakistan air force pilots, Nacional 3 defensor 0 clausura 2011, Cryptsetup luksopen, ... Toms shoe sizing tiny, Degrassi season 14 frankie and winston?...
Read more >Changelog - Cypress Documentation
Cypress has made several configuration option changes including renaming options, removing options, and only allowing some options within a specific testing ...
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
Here’s what I’m experiencing; maybe its related?
When I don’t use uppercase method on info.level I get logs on console as expected
but when I use uppercase method
Code (Typescript)
I was developing on macos