-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mysterious output with webpack 4 and style related loaders #45
Comments
Hey @hieuhlc - yes, this is expected because of the way that the Extract plugins work. Let me deep-dive a little bit to get a more in-depth answer before giving you the exact reasons why (and if there's anything you can do to speed it up, I think the answer is "not really no, other than disabling the extract-plugin in development mode" off the top of my head, though) Where would you search for an answer like this, though? I'm not 100% sure where to put information like this, and I'm worried about polluting the terminal output too much |
Hi @stephencookdev , thanks for your answer. How webpack plugins work is still mystery to me but at least now I know I didn't have wrong configuration. |
I've raised #51 to hopefully address the root of this confusion |
I'm using latest versions of everything: webpack, loaders & speed-measure-webpack-plugin.
I run webpack build with production config and got this result
I don't understand why and what should I do to optimize (prevent duplicate???)
The text was updated successfully, but these errors were encountered: