Comments (7)
@DylanPiercey you'll need to apply the plugin to the the multi compiler returned from webpack
, e.g. https://github.com/60frames/react-boilerplate/blob/master/server/routes/webpack.js#L20
const multiCompiler = webpack([config1, config2]);
multiCompiler.apply(new FriendlyErrorsWebpackPlugin());
from friendly-errors-webpack-plugin.
Hi @richardscarrott, I'll accept any PR with tests 😄
Thanks for taking the time to document this issue!
from friendly-errors-webpack-plugin.
What does the config look like to use this with a multi compiler? Do I add the plugin to both compilers?
from friendly-errors-webpack-plugin.
Okay, I've discovered applying the plugin to both compilers separately doesn't really work because the console may read 'DONE' because the most recent compilation succeeded but it obviously doesn't take into account the other compilation which may still be in an error state.
Would you be open to a PR for this?
from friendly-errors-webpack-plugin.
Fixed in #9
from friendly-errors-webpack-plugin.
@richardscarrott awesome - thanks! Gonna try this out now.
from friendly-errors-webpack-plugin.
It works perfectly :D.
from friendly-errors-webpack-plugin.
Related Issues (20)
- Blank error when only webpackError property populated
- module is undefined
- show time even if warning appears
- Missing Error Filtering Feature
- Stylelint output does not show the name of the file where warnings occur
- Cannot read property 'request' of undefined at transform HOT 2
- Cannot read property 'some' of undefined
- Missing error report for failed compilation
- Can this plugin work with ForkTsChecker plugin when clearConsole is true? HOT 7
- Is 2.x ready for release? HOT 2
- compilationSuccessInfo.message not show HOT 1
- Peer Dependency issue with Webpack v5.x HOT 4
- Type 'FriendlyErrorsWebpackPlugin' is not assignable to type 'WebpackPluginInstance'.
- Forget update the Readme on NPM HOT 1
- Cannot read property 'startsWith' of undefined HOT 2
- should not output warning when the count of warnings is 0 HOT 4
- Support for displaying compilationSuccessInfo only on initial compilation HOT 1
- Does not work with Node.js v12 HOT 2
- recommending a different eslint-loader formatter in the docs
- Compilation is always succesful when it should not be HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from friendly-errors-webpack-plugin.