Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Plugin is not respecting the default sourcemap output #101

Open
enmanuelduran opened this issue Apr 12, 2019 · 2 comments
Open

Plugin is not respecting the default sourcemap output #101

enmanuelduran opened this issue Apr 12, 2019 · 2 comments

Comments

@enmanuelduran
Copy link

enmanuelduran commented Apr 12, 2019

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.

@galvarez421
Copy link

Perhaps related to #53 (comment), the plugin does not seem to respect general webpack configuration options related to source maps.

@galvarez421
Copy link

Related to #91.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants