We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Allow specifying custom options for PostCSS process, as https://github.com/NMFR/optimize-css-assets-webpack-plugin does (cssProcessorOptions option). The options object is defined here and cannot be extended.
cssProcessorOptions
Into Quasar Framework we use https://github.com/postcss/postcss-safe-parser via the parser PostCSS option.
parser
A possible patch would be to copy/paste the internal minify function into an external provided minify one, with the options we prefer
minify
The text was updated successfully, but these errors were encountered:
Yep, sounds good, PR welcome, let's name it as processorOptions
processorOptions
Sorry, something went wrong.
Are there any updates? If I want to use postcss-safe-parser now, is there any alternative?
Successfully merging a pull request may close this issue.
Feature Proposal
Allow specifying custom options for PostCSS process, as https://github.com/NMFR/optimize-css-assets-webpack-plugin does (
cssProcessorOptions
option).The options object is defined here and cannot be extended.
Feature Use Case
Into Quasar Framework we use https://github.com/postcss/postcss-safe-parser via the
parser
PostCSS option.A possible patch would be to copy/paste the internal minify function into an external provided
minify
one, with the options we preferThe text was updated successfully, but these errors were encountered: