Using winston while developing, how to flush the file transports when debug breaking

[JanFellner]

I am developing a signalling application that receives and sends messages to different entities.
While developing i have the need to debug break if unexpected behavior occurs.

Is there any possibility to let winston synchronously flush file logs to have all messages in the log right before debug breaking?

Or is the solution to implement my own file logger that drops all the log content to the file synchronously?

[wbt]

That is a great question! You might find more active answers on StackOverflow than here, but my strategy in that situation would generally be to add a console transport based on a development mode vs. production mode configuration switch. It's way easier than implementing a whole new file log, and you can probably even pipe the console to a file if you need that.