The detailed explanation could be found in the README.md of the postcss-nested-once plugin i've made to overcome the issue. It was intially written for the internal usage, but, as there is a chance it could help someone facing the same issue, I decided to publish.
It would be great if you could mention it somewhere in the docs.
Another great option would be if you could reimplement the same approach behind another setting (i.e. nested: boolean | NestedOptions) as it's done for import/url.
Good day! Firts of all, thanks for the great work on this plugin!
I've discovered a wired "bug" using it with postcss-nested plugin. In short, the following style:
Results in:
The detailed explanation could be found in the README.md of the postcss-nested-once plugin i've made to overcome the issue. It was intially written for the internal usage, but, as there is a chance it could help someone facing the same issue, I decided to publish.
It would be great if you could mention it somewhere in the docs. Another great option would be if you could reimplement the same approach behind another setting (i.e.
nested: boolean | NestedOptions
) as it's done for import/url.