Amitav Khandelwal

> I think I found the culprit. We replicated the same behavior with WinSW v2.11 and WinServer 2016. We saw that we had the service configured with log -- autoRollAtTime...

> > I think I found the culprit. We replicated the same behavior with WinSW v2.11 and WinServer 2016. We saw that we had the service configured with log --...

@prateekjain98 and I managed to fix this by deleting our `yarn.lock` and installing dependencies again. Not sure what exactly fixed it, but my guess is that there was a mix...

Added in a PR (#30) to address the retrofit example. Can update the rest once the that goes in.

@FrancoSabadini I didn't end up finding a good way for this. Yours seems like the kind of approach we'd want to take. Ideally we'd just be passing in a flag...