8000 updated with node version support · mKoder/log4js-node@c951546 · GitHub
[go: up one dir, main page]

Skip to content

Commit c951546

Browse files
author
Gareth Jones
committed
updated with node version support
1 parent 3a62714 commit c951546

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

README.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,8 @@ The default appender has been changed from `console` to `stdout` - this alleviat
2626

2727
I'm also trying to move away from `vows` for the tests, and use `tape` instead. New tests should be added to `test/tape`, not the vows ones.
2828

29+
log4js also no longer supports node versions below 0.12.x.
30+
2931
NOTE: from log4js 0.5 onwards you'll need to explicitly enable replacement of node's console.log functions. Do this either by calling `log4js.replaceConsole()` or configuring with an object or json file like this:
3032

3133
```javascript
@@ -95,7 +97,7 @@ You can configure the appenders and log levels manually (as above), or provide a
9597
configuration file (`log4js.configure('path/to/file.json')`), or a configuration object. The
9698
configuration file location may also be specified via the environment variable
9799
LOG4JS_CONFIG (`export LOG4JS_CONFIG=path/to/file.json`).
98-
An example file can be found in `test/log4js.json`. An example config file with log rolling is in `test/with-log-rolling.json`.
100+
An example file can be found in `test/vows/log4js.json`. An example config file with log rolling is in `test/vows/with-log-rolling.json`.
99101
You can configure log4js to check for configuration file changes at regular intervals, and if changed, reload. This allows changes to logging levels to occur without restarting the application.
100102

101103
To turn it on and specify a period:

0 commit comments

Comments
 (0)
0