You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3-1Lines changed: 3 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -26,6 +26,8 @@ The default appender has been changed from `console` to `stdout` - this alleviat
26
26
27
27
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.
28
28
29
+
log4js also no longer supports node versions below 0.12.x.
30
+
29
31
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:
30
32
31
33
```javascript
@@ -95,7 +97,7 @@ You can configure the appenders and log levels manually (as above), or provide a
95
97
configuration file (`log4js.configure('path/to/file.json')`), or a configuration object. The
96
98
configuration file location may also be specified via the environment variable
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`.
99
101
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.
0 commit comments