<commit_before># Logger #

Logging module supporting built-in and custom transports, Express 4 response mixins, and chainable method syntax for creating log events.

Includes support for formatted logging to the following transports:

* console (default)
* file (specify path) - logs as a JSON array
* [SOS Max](http://www.sos.powerflasher.com/developer-tools/sosmax/home/) - _SOS max is the POWERFLASHER Socket Output Server - a fast and helpful programmer tool with graphical
user interface to display log messages for debugging purpose._

On startup the logger is set to the console transport, but the console transport is not yet activated.
All log messages are queued until you start the current transport or set a different transport.
Once you start the current transport with ```startLogger``` the console will begin to output log messages.
Instead you can set a different transport using ```setLogger``` and then logging, including queued log messages,
will begin being output to the new transport.
<commit_msg>Added comment pointing to v2 in develop branch<commit_after># Logger #

Logging module supporting built-in and custom transports, Express 4 response mixins, and chainable method syntax for creating log events.

Version 2 is currently [under development in the develop branch](https://github.com/jpravetz/epdoc-logger/tree/develop). 
It is recommended you use the alpha of version 2 rather than using 1.9.x.

Includes support for formatted logging to the following transports:

* console (default)
* file (specify path) - logs as a JSON array
* [SOS Max](http://www.sos.powerflasher.com/developer-tools/sosmax/home/) - _SOS max is the POWERFLASHER Socket Output Server - a fast and helpful programmer tool with graphical
user interface to display log messages for debugging purpose._

On startup the logger is set to the console transport, but the console transport is not yet activated.
All log messages are queued until you start the current transport or set a different transport.
Once you start the current transport with ```startLogger``` the console will begin to output log messages.
Instead you can set a different transport using ```setLogger``` and then logging, including queued log messages,
will begin being output to the new transport.

{'fraction_non_alphanumeric': 0.05599647266313933, 'fraction_numerical': 0.0030864197530864196, 'mean_word_length': 4.817948717948718, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 1, 'lorem ipsum': 0, 'www.': 2, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1479405', 'n_tokens_mistral': 565, 'n_tokens_neox': 544, 'n_words': 313}