Scott Chapman
Scott Chapman
totally agree here. There really needs to be even a VERY simple example.
Tragically this makes this really unusable in production... I tried following the [Waiting for Winston logs to finish](https://github.com/winstonjs/winston#awaiting-logs-to-be-written-in-winston), but that flow doesn't seem to work. The `finished` event never gets...
Ah, the winston docs use `finished`. So, I do get that event. However, I close my client when I get it, but my app still never exits. Here's the code:...
Does anyone have an example where the app exits??
Since I can't figure this out, I've switched to using the `elasticsearch` client directly which works great... But would really like to use Winston for logging...
Right it should, but it doesn't (at least for me). Does anyone have any actual code example where you can log AND have the application exit?
See my code above, change `finished` to `finish`. It prints the "All Finished" line and then just hangs. 
I believe that's what my code above does; I create my own ES Client, use it to initialize the transport. And I close that client when I get the `finish`...
Yea, that seems like a rather unfriendly approach. I mean that can't be the right approach, this just seems like a bug. Seriously is that how folks are running with...
...disappointed. I'd rather see a simple solution for majority of cases (with limitations). People don't have to use it if it doesn't apply...