You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I configure PostCSS to run postcss-mixins before postcss-preset-env and I define a mixin that uses syntax that needs to be transformed by postcss-preset-env, I expect the mixin's output to be processed by later plugins properly.
But right now I get the raw mixin definition printed into my output CSS without the mixin definition being altered by later plugins.
If I have a stylesheet that defines a mixin like this:
module.exports={// The order of plugins is important.plugins: {'postcss-mixins': {},// Add support for experimental (stage 1) and higher W3 specs.// See https://cssdb.org/'postcss-preset-env': {stage: 1,},},};
The text was updated successfully, but these errors were encountered:
You need to open the issue in postcss-nesting. It should use PostCSS 8 events to transform nested rules after every CSS AST change (seems like right now it transforms it only once).
If I configure PostCSS to run postcss-mixins before postcss-preset-env and I define a mixin that uses syntax that needs to be transformed by postcss-preset-env, I expect the mixin's output to be processed by later plugins properly.
But right now I get the raw mixin definition printed into my output CSS without the mixin definition being altered by later plugins.
If I have a stylesheet that defines a mixin like this:
The output has invalid CSS where the mixin is used, while the rest of the file is correct:
But I expect the correct output:
This is my postcss.config.js:
The text was updated successfully, but these errors were encountered: