optimize-css-assets-webpack-plugin icon indicating copy to clipboard operation
optimize-css-assets-webpack-plugin copied to clipboard

Plugin is not respecting the default sourcemap output

Open enmanuelduran opened this issue 6 years ago • 2 comments

I'm using this config to generate the sourcemaps on my site on production:

new OptimizeCSSAssetsPlugin({
    cssProcessor: require('cssnano'),
    cssProcessorOptions: {
        map: {
            inline: false,
            annotation: true,
        },
    },
}),

and webpack output sourceMapFilename is:

output: { 
    sourceMapFilename: sourcemaps/[file].map
}

But the plugin is sending the sourcemaps to the same folder in which the css output files are located instead of sourceMapFilename using the sourcemap folder.

Without using the plugin all the sourcemaps work as expected and go to the sourceMapFilename point but when adding the plugin it just ignores it.

enmanuelduran avatar Apr 12 '19 14:04 enmanuelduran

Perhaps related to https://github.com/NMFR/optimize-css-assets-webpack-plugin/issues/53#issuecomment-494830816, the plugin does not seem to respect general webpack configuration options related to source maps.

galvarez421 avatar May 22 '19 14:05 galvarez421

Related to #91.

galvarez421 avatar May 22 '19 14:05 galvarez421