@@ -91,12 +91,13 @@ recompile when files change, but rather on each request.
91
91
### logger
92
92
93
93
Type: ` Object `
94
- Default: [ ` log ` ] ( / webpack/webpack-dev-middleware /blob/master/lib/log .js)
94
+ Default: [ ` webpack- log` ] ( https://github.com/ webpack-contrib /webpack-log /blob/master/index .js)
95
95
96
96
In the rare event that a user would like to provide a custom logging interface,
97
97
this property allows the user to assign one. The module leverages
98
- [ ` loglevel ` ] ( https://github.com/pimterry/loglevel#documentation )
99
- for logging management by default, and any custom logger must adhere to the same
98
+ [ ` webpack-log ` ] ( https://github.com/webpack-contrib/webpack-log#readme )
99
+ for creating the [ ` loglevelnext ` ] ( https://github.com/shellscape/loglevelnext#readme )
100
+ logging management by default. Any custom logger must adhere to the same
100
101
exports for compatibility. Specifically, all custom loggers must have the
101
102
following exported methods at a minimum:
102
103
@@ -125,7 +126,7 @@ include:
125
126
126
127
Setting a log level means that all other levels below it will be visible in the
127
128
console. Setting ` logLevel: 'silent' ` will hide all console output. The module
128
- leverages [ ` loglevel ` ] ( https://github.com/pimterry/loglevel#documentation )
129
+ leverages [ ` webpack-log ` ] ( https://github.com/webpack-contrib/webpack-log#readme )
129
130
for logging management, and more information can be found on its page.
130
131
131
132
### logTime
@@ -159,7 +160,7 @@ Type: `Object`
159
160
Default: ` undefined `
160
161
161
162
Allows users to provide a custom reporter to handle logging within the module.
162
- Please see the [ default reporter] ( /webpack/webpack-dev-middleware/blob/master/ lib/reporter.js )
163
+ Please see the [ default reporter] ( /lib/reporter.js )
163
164
for an example.
164
165
165
166
### serverSideRender
0 commit comments