Not working if used along with extract-text-webpack-plugin
See original GitHub issueweird bug if used along with extract-text-webpack-plugin… i tried to fix… but no luck…~
example.
new ExtractTextPlugin({
filename: '[name].css',
allChunks: true, <-- if set to false then fontmin-webpack will works fine...
})
files are not being matched… probably extract-text modifies compilation.modules… don’t know ~
Issue Analytics
- State:
- Created 7 years ago
- Comments:11 (7 by maintainers)
Top Results From Across the Web
Not working with webpack 4 #801 - GitHub
The extract-text-webpack-plugin toward Webpack 4 doesn't work. it means when Webpack is run for building or developing, it falls in error.
Read more >extract-text-plugin not working with Webpack 3 - Stack Overflow
You shouldn't use the extract-text-plugin in development mode. The extract-text-plugin is used in productiont mode.
Read more >Solution - "extract-text-webpack-plugin" loader is used without ...
Recurring problem in Webpack's extract-text-webpack-plugin package, used to extract CSS (Cascading Style Sheets) references from JavaScript sources and ...
Read more >extract-text-webpack-plugin > JavaScript for PHP Geeks
Ignore the fallback key for a moment. Basically, the extract() function is a fancy way to prepend the loaders in use with a...
Read more >ExtractTextWebpackPlugin | webpack
:warning: ExtractTextPlugin generates a file per entry, so you must use [name] , [id] or [contenthash] when using multiple entries. #extract. ExtractTextPlugin.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@patrickhulce Thanks man! It works perfect now. where did you get docs on webpack? i constantly find myself trying to solve this kinds of issues but cant find enough docs on it… going on the source code direcly takes too much time…
OK @Milewski I think I have a fix. It should publish as v1.0.1 once it passes CI. If you can give it a go to see if it fixes your issue, that’d be awesome.