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
{{ message }}
This repository was archived by the owner on Jul 27, 2021. It is now read-only.
If you use webpack-hot-middleware, that is done by setting the log option to a no-op. You can do something sort of like this, depending upon your setup:
_Thanks to [webpack-dashboard](https://github.com/FormidableLabs/webpack-dashboard) for this piece of info._
57
+
13
58
## Demo
14
59
15
60
### Build success
@@ -45,7 +90,7 @@ new FriendlyErrorsPlugin({
45
90
// should the console be cleared between each compilation?
46
91
// default is true
47
92
shouldClearConsole:true,
48
-
93
+
49
94
// add formatters and transformers (see below)
50
95
additionalFormatters: [],
51
96
additionalTransformers: []
@@ -84,7 +129,7 @@ new NotifierPlugin({
84
129
### Transformers and formatters
85
130
86
131
Webpack's errors processing, is done in four phases:
87
-
132
+
88
133
1. Extract relevant info from webpack errors. This is done by the plugin [here](https://github.com/geowarin/friendly-errors-webpack-plugin/blob/master/src/core/extractWebpackError.js)
89
134
2. Apply transformers to all errors to identify and annotate well know errors and give them a priority
90
135
3. Get only top priority error or top priority warnings if no errors are thrown
0 commit comments