mini-css-extract-plugin VS webpack-merge

mini-css-extract-plugin

In my production file I'm using mini-css-extract-plugin to create a final css file rather than have them loaded in my bundle.js file.

The css webpack extract plugin gets 12 million downloads per week https://www.npmjs.com/package/mini-css-extract-plugin

This shouldn't be the case, at least not if you're doing it "properly". For dev builds, sure, but for production, it's better to use something like mini-css-extract-plugin to extract the bundled CSS into separate files. Then for files in your main entrypoint, the CSS will be loaded via tags, and files loaded via code-splitting, the tags will be added to the DOM dynamically.

Since I'm using Webpack 4, I am also using mini-css-extract-plugin. I started down the path of creating a splitChunks in my webpack config.

When in Webpack entry are defined style files like SCSS/SASS and used the mini-css-extract-plugin then will be generated unexpected empty js files.

According to its Github page this is deprecated and you should use this instead https://github.com/webpack-contrib/mini-css-extract-plugin

npm WARN deprecated [email protected]: Deprecated. Please use https://github.com/webpack-contrib/mini-css-extract-plugin

If you have a webpack configuration for production then you'll need a different configuration for using CSS. At first, install mini-css-extract-plugin

I'm using Webpack 5 with webpack-merge so I can have separate config files for prod and dev with a common file for settings that both prod and dev share.

You can try installing https://www.npmjs.com/package/webpack-merge or see if that merge is in your config.js or somewhere else.

webpack-merge - Simplify development/production configuration