Closed LFFATE closed 2 years ago
Hi @LFFATE,
In old versions, there is no support for nested rules, so this is the difference between version 2 and version 3.
Could you create a small repo with a minimum reproducible example so I can look at the issue closer?
Regards
Could you create a small repo with a minimum reproducible example so I can look at the issue closer?
Yeah, I'll try as soon as possible but can't promise it will soon
Perfect @LFFATE, when you have time, no pressure. It is just that it would be easier for me to check what is happening and fix it if I can reproduce it easily. Regards and thanks.
@elchininet Hello again. I created a repro repo https://github.com/LFFATE/postcss-rtlcss-issue-122-repro
To start it follow these steps:
yarn
yarn parcel src/index.html
css located at src/style.css
postcss config located at postcss.config.js
compiled css will be created at dist/index.*.css
Thanks @LFFATE, I‘ll let you know when it is solved. Regards
Hi @LFFATE, version 3.5.3 solves this issue. Regards and thanks for all the help.
@elchininet Great! Thank you!
So the problem:
Initial code:
results to by a postcss-nested plugin:
Where
.b-product-single__main
just disappears after postcss-rtlcss.If I replace initial code with stright result of postcss-nested I cannot see the problem.
My env:
package.json:
postcss.config.js:
If I rollback to postcss-rtlcss@2 it works. So may be version 3.x has some conflicts with other postcss plugins? And another way to make it work:
In this way the code results to:
And a last way to make it work is to remove all trailing left-right specific rules:
Result:
Well
.b-product-single__main
doesn't disappears now. Magic.There is no errors due to a build process. I tested it with webpack and rollup, so loaders and bundlers doesn't matters.