This is more a kind of question:
- Would it make sense if
postcss-calc transformations were based on the browsers support configured through browserlist?
- How would this affect
postcss-calc?
- If
postcss-calc is not the correct repository to implement such logic, which one would be? Would it be cssnano-preset-default or a different one?
For example by using cssnano-preset-default we can define this configuration in postcss.config.js:
module.exports = {
plugins: [
require('cssnano')({
preset: ['default', {
calc: false,
}]
}),
],
};
This is more a kind of question:
postcss-calctransformations were based on the browsers support configured throughbrowserlist?postcss-calc?postcss-calcis not the correct repository to implement such logic, which one would be? Would it becssnano-preset-defaultor a different one?For example by using
cssnano-preset-defaultwe can define this configuration inpostcss.config.js: