Running this plugin stops all other loaders
See original GitHub issueI am running “svg-spritemap-webpack-plugin”: “^2.0.0-rc.4” on webpack 4.1.1. My config for this plugin is:
new SVGSpritemapPlugin({
src: 'assets/gfx/*.svg',
filename: 'spritemap.[contenthash].svg',
prefix: 'fablr-',
}),
But when this is active, all other files (JS, CSS, etc) are not emitted anymore. So it’s unusable for me. I’m not able to see what happens, except that everything is back to normal when I comment out SVGSpritemapPlugin. Any pointers?
Issue Analytics
- State:
- Created 6 years ago
- Comments:18 (10 by maintainers)
Top Results From Across the Web
How to handle multiple loaders with different plugins using ...
Hi, I have the full issue here. The problem is that the user needs to run different plugins on different loaders.
Read more >Loaders - webpack
Loaders are transformations that are applied to the source code of a module. They allow you to pre-process files as you import or...
Read more >Plugin not unload-safe because class loader cannot be ...
Hello,. I'm developing the HasteIt plugin for IDEA-based IDEs and I'm trying to figure out, why my plugin can't be unloaded correctly.
Read more >Issues with making plugin loader for a java app - Stack Overflow
I have made the plugin structure dependency and have test plugins, the part that I am having problems with is the plugin loading...
Read more >Webpack explained simply – plugins, loaders and Babel
If you tried to run this code in the browser as it is, it would certainly fail. That's why we need to use...
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
looks fine here as well. other plugins prevent me from migrating to webpack 4 right now, so i cant see if it actually works, but it looks like its fine right now. thanks 😃
I tested the master version and it seems to fix it! Thanks!