#719 - Support decoration with process information

[dbo]

Implements #719

Feedback welcome.

[coveralls]

Coverage increased (+1.9%) to 89.547% when pulling dfe3ae1 on dbo:master into 5c7c61d on visionmedia:master.

[coveralls]

Coverage increased (+2.1%) to 89.789% when pulling d92b3f9 on dbo:master into 5c7c61d on visionmedia:master.

[Qix-]

Really not a fan of adding more environment variables - this is what #556 is aimed to solve. Otherwise, every logging combination under the sun would scope-creep this package into oblivion.

[dbo]

@Qix- Apparently it's not really about my own logs only (which I could customize with what is aimed in #556), but about 3rd party NPMs that I use in my process. Moreover, environment variables don't require to execute any custom code which is sometimes not possible when plugging into frameworks that use their own startup scripts. Since all debug env variables are scoped to DEBUG_ I don't see any collision.

[Qix-]

It's not about collision, it's about API cleanliness. The idea behind #556 is that it'd be globally enforced and entirely backwards compatible. You wouldn't have to modify code, but instead use -r to inject a non-default reporter.

In the case of PID's, #582 could include PID as a variable.

[dbo]

@Qix- I agree, reading on #582 I think it's what I look for, since I could streamline all logs to carry the PID (needs some %P or whatever extension though) or define a readable process title.