Emitting 'error'-event

There is this line 228 in the main file in onErrored:

self.emit('error', err);

As the error is emitted, this causes the whole process to end, if the error isn’t listened on elsewhere. This can lead to server crashes if Papertrail cannot be connected to. I thought maybe this should be mentioned in the docs. 😃

[freezy]

So I’ve come across this as well.

This is the worst to debug. Without longjohn Node just crashes with a connection error, without any hint at all where the problem could be (stacktrace is a threeliner). This took me hours to find.

@matteocontrini: Are you seriously suggesting to keep your “Usage” example? This will crash the whole Node process in case something goes wrong.

For the record, there is nothing wrong with emitting your errors on your own stream. Or publish a library with a streaming API. But this is no streaming API. It’s a drop-in replacement for a logging transport. This needs at least documentation. Also examples that don’t crash the process would probably be a good idea.

[troy]

@dmiddlecamp’s #61 has been released to NPM in 1.0.4. If anyone experiences this or believes they have, please make sure you’re running >= 1.0.4; it may mitigate this issue to the point of eliminating it.