css-loader: [2.0.0] ValidationError: CSS Loader Invalid Options - options should NOT have additional properties

Same issue here

const cssLoader = {
    loader: "css-loader"
};

cssLoader.options = {
     minimize: true
 };

.........................
                {
                    test: /\.less$/,
                    use: [MiniCssExtractPlugin.loader,
                        cssLoader,
                    {
                        loader: "less-loader",
                        options: {
                            paths: [
                                path.resolve(__dirname, "node_modules")
                            ],
                            javascriptEnabled: true
                        }
                    }]
                }

And works fine if remove minimize: true.

Coming across this issue again on 3.0.0

For me, it was localIdentName not being in the options schema. Is this a bug?

localIdentName is mentioned all over the README and docs.

@p3x-robot minimize will be remove in 1 version, you don’t need this option, just remove

To those needing help, just change the key <-> pair like what @eric-miffre mentioned. Here’s an example:

Before: options: { modules: true, localIdentName: "[name]__[local]___[hash:base64:5]", },

After: options: { modules: { localIdentName: "[name]__[local]___[hash:base64:5]", },

Notice how now you have a modules Object within the options Object. Just put all your previous key <-> value pairs within the modules Object and you’ll be good to go

Had the same issue, but it is indeed explained in the breaking changes section of the v3 changelog:

modules option now can be {Object} and allow to setup CSS Modules options:

• localIdentName option was removed in favor modules.localIdentName option

Which did solve it for me.

I have this issue on version 2.1.0, without any options at all. Had to downgrade to 1.0.1, which has solved the issue.

• Proper solution should be the validator should throw easily understandable validation errors.
• Anybody who is still facing this issue just validate the options you have entered with the options schema mentioned under file node_modules\css-loader\dist\options.json.

To those needing help, just change the key <-> pair like what @eric-miffre mentioned. Here’s an example:

Before: options: { modules: true, localIdentName: "[name]__[local]___[hash:base64:5]", },

After: options: { modules: { localIdentName: "[name]__[local]___[hash:base64:5]", },

Notice how now you have a modules Object within the options Object. Just put all your previous key <-> value pairs within the modules Object and you’ll be good to go

Confirmed working. In my case I changed it from

options: { localIdentName: '[hash:base64:5][path]-[local]' }

to

options: { modules: { localIdentName: '[hash:base64:5][path]-[local]' } }

in my webpack/babel config.

Same problem with NextJs default config

Hi @mhauens

For NextJS, please check this file: …\node_modules@zeit\next-css\css-loader-config.js

from row 70 to 82

const cssLoader = { loader: isServer ? ‘css-loader/locals’ : ‘css-loader’, options: Object.assign( {}, { modules: cssModules, //minimize: !dev, sourceMap: dev, importLoaders: loaders.length + (postcssLoader ? 1 : 0) }, cssLoaderOptions ) }

and comment or remove minimize option.

no issue in 1.0.1

Solved. Feel free to feedback.

@fpsqdb please don’t write Same issue here, it doesn’t help to solve issue, better create minimum reproducible test repo @wanliyunyan thanks, will be fixed in near future

Unfortunately, I had to downgrade to 1.0.1 from 2.1.1 because this issue is still impacting my builds.

Same problem with NextJs default config

There is not shit like ‘minimize:true’ in my config.

I don’t know why, but it’s okay to upgrade to the latest 3.2.0.

@p3x-robot remove this line https://github.com/patrikx3/gitlist/blob/master/webpack.config.js#L211 (minimize will be removed in 1 version)

This worked for my VUE Js project:

Browse to the /build/utils.js file and in the object of the css-loader comment on the option that is marking you in the error. In my case I had to comment:

minimize: process.env.NODE_ENV === 'production',

            {
                test: /\.css$/,
                use: [
                    MiniCssExtractPlugin.loader,
                    {
                        loader: 'css-loader',
                        options: {
                            modules: {
                                localIdentName: "[path][name]__[local]--[hash:base64:5]"
                            }
                        }
                    }
                ]
            }

I have the same issue, I can confirm that in version 1.0.1 it works well