The v5 plugin API was not updated to support cssnano v4

[jzempel]

v5.0.0 was a breaking change in that it was updated to depend on cssnano v4.0.2. However, this plugin was not updated to receive options per the PostCSS 6.x breaking change described by cssnano.

Please see https://cssnano.co/guides/presets/ for updated API details.

For example, attempt the following:

new OptimizeCSSAssetsPlugin({
  cssProcessorOptions: { /* update API to receive a cssPluginOptions? */
    preset: [
      'default',
      {
        cssDeclarationSorter: false,
        normalizeWhitespace: false
      }
    ]
  }
});

Result: declarations will still be sorted and whitespace will be compressed by cssnano 4.

Reference:

• https://github.com/postcss/postcss/blob/master/CHANGELOG.md#60-marquis-orias
• http://api.postcss.org/postcss.html#.plugin vs. https://github.com/NMFR/optimize-css-assets-webpack-plugin/blob/v5.0.0/src/index.js#L62 ... 2nd parameter is processOptions; 3rd parameter is pluginOptions.

[rofrol]

To disable certain plugins, you need to do it in package.json:

  "cssnano": {
    "preset": [
      "default",
      {"cssDeclarationSorter": {"exclude": true}}
    ]
  }

or in postcss.config.js:

module.exports = {
    plugins: [
        require('cssnano')({
            preset: ['default', {
                cssDeclarationSorter: {
                    exclude: true,
                },
            }],
        }),
    ],
};

Disabling in webpack.config.js or cssnano.config.js like descibed here, doesn't work.

[jzempel]

I see what you're saying @rofrol. But the plugin's API could be updated to receive cssPluginOptions, right? If so, then it would continue to function in the manner it did prior to v5.0.0 where inlined options were applied to the cssnano transform.

[rofrol]

But your plugin's API

@jzempel It's not my plugin

[NMFR]

#73 solved this.

If not tell me so i can reopen the issue.