Do not pass errors to the external code
At least make such option.
This is great script, very simple and convenient! Though one thing is inconvenient - library pushes developer to handle errors. This is not likely what i (as average developer) would like to do. I'm fan of business logic, not fan of low abstract level (i would code on C or ASM in this case :1234: :) ) So it is logical, that all errors simply should go to winston or rollbar and if they will occur sometimes - it will be known from logs and fixed - either code bag eliminated, or db farm extended, etc..
Because whatever what may happen (in most of web applications) - it should be handled by people in real world - so why challenge developer with guessing what to do with this err?
Or i am mistaken? Is there any examples of common case when you do need error handling other, than sending it to logs?