You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 27, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Aug 27, 2026. It is now read-only.
@alexander-akait What about making config.output.cssFilename as a fallback?
If the filename is passed to new MiniCssExtractPlugin({ filename }), it takes precedence, and we always use that, and config.output.cssFilename is ignored.
And if config.output.cssFilename is specified, mini-css-extract-plugin can fallback to that.
And if neither is specified, mini-css-extract-plugin falls back to the built-in default.
If we always prefer filename is passed to new MiniCssExtractPlugin({ filename }) (the highest priority), this should avoid breaking existing users.
@SukkaW I am fine with it, but I would like to add experiments.css is mostly ready (around 95% things are implemented), so you can try to use built-in css solution (we are planning to finish it completely by January)
@SukkaW I am fine with it, but I would like to add experiments.css is mostly ready (around 95% things are implemented), so you can try to use built-in css solution (we are planning to finish it completely by January)
My current use case is having a shared webpack config (doing something like module.exports = require('@acme/webpack').createWebpackConfig({ webpackExperimentalCss: boolean })) stuff, and I want to have multiple projects (no matter which css solution is used) with a consolidated cssFilename config in one place.
As for this issue, I will create a PR implementing #1041 (comment) since you gave it a go.
Activity
alexander-akait commentedon Jan 10, 2024
We can do it, but I am afraid it will be breaking change right now
SukkaW commentedon Dec 23, 2025
@alexander-akait What about making
config.output.cssFilenameas a fallback?If the
filenameis passed tonew MiniCssExtractPlugin({ filename }), it takes precedence, and we always use that, andconfig.output.cssFilenameis ignored.And if
config.output.cssFilenameis specified,mini-css-extract-plugincan fallback to that.And if neither is specified,
mini-css-extract-pluginfalls back to the built-in default.If we always prefer
filenameis passed tonew MiniCssExtractPlugin({ filename })(the highest priority), this should avoid breaking existing users.alexander-akait commentedon Dec 23, 2025
@SukkaW I am fine with it, but I would like to add
experiments.cssis mostly ready (around 95% things are implemented), so you can try to use built-in css solution (we are planning to finish it completely by January)SukkaW commentedon Dec 23, 2025
My current use case is having a shared webpack config (doing something like
module.exports = require('@acme/webpack').createWebpackConfig({ webpackExperimentalCss: boolean })) stuff, and I want to have multiple projects (no matter which css solution is used) with a consolidatedcssFilenameconfig in one place.As for this issue, I will create a PR implementing #1041 (comment) since you gave it a go.
alexander-akait commentedon Dec 23, 2025
@SukkaW Got it, I am fine with it, do you want to send a PR?
fix(webpack#1041): respect `output.cssFilename` and `output.cssChunkF…
SukkaW commentedon Dec 24, 2025
@alexander-akait #1151