Support for Winston 3.0?
See original GitHub issueWinston 3.0 is going to be released soon. It has some breaking changes for transports which makes winston-papertrail incompatible.
For example, log
is now called with a single info
object containing message, level
instead of a few separate variables.
@kenperkins or @troy would you be so kind to adjust the plugin for the new winston version?
Issue Analytics
- State:
- Created 6 years ago
- Reactions:23
- Comments:7 (1 by maintainers)
Top Results From Across the Web
Announcing winston@3.0.0! — GoDaddy Engineering Blog
Announcing winston@3.0.0! · Replace the winston internals with Node. · Empower users to format their logs without changes to winston itself. · Modularize...
Read more >3.0.0 - winston - npm
A multi-transport async logging library for Node.js. Latest version: 3.8.2, last published: 3 months ago. Start using winston in your ...
Read more >Using Winston 3 for Logging in Node.js - Loggly
With the Winston 3.0 update, one of the biggest changes is the ability ... Loggly is a perfect target for Winston, since it...
Read more >winston | Yarn - Package Manager
winston. owner winstonjs36.7mMIT3.8.2TS. A multi-transport async logging ... v3.8.2. Patch-level changes. Add .js to main entry point in package.json in ...
Read more >Developers - Support for Winston 3.0? - - Bountysource
Winston 3.0 is going to be released soon. It has some breaking changes for transports which makes winston-papertrail incompatible.
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
@markdascher Hi Mark, any news about https://github.com/winstonjs/winston-transport/issues/27 ?
I actually haven’t seen any crashing with winston 3.0 in my own tests. The usage example works with just one change: replace
new winston.Logger
withwinston.createLogger
. This nice compatibility layer takes care of the rest: winstonjs/winston-transport. There is a warning message emitted, but otherwise it works fine:Only wrinkle is that JSON is being appended to each message (on a second line), but I’ve opened winstonjs/winston-transport#27 about that.
Am I overlooking something? As long as it still works, I’d probably favor either leaving this transport as-is or performing a complete overhaul as described in UPGRADE-3.0.md. Something more targeted (e.g. #78) would just seem to break backward compatibility without actually getting the benefits of winston 3.0.