Public Service Announcement: Because of an issue with postcss-nested, if you are trying to use bothpostcss-nested and this plugin, you need to use this plugin first.
However, (1) that issue has been closed, and (2) using postcss-extend first as suggested causes a different issue described in (the initial report of) #25:
Putting postcss-nested before postcss-extend results in the expected CSS. (The remaining comments of #25 meander to a different issue that seems to have since been fixed, but this one remains.)
Should the README.md suggestion be reversed, or does this count as another bug in one of the plugins?
According to
README.md
:However, (1) that issue has been closed, and (2) using
postcss-extend
first as suggested causes a different issue described in (the initial report of) #25:Putting
postcss-nested
beforepostcss-extend
results in the expected CSS. (The remaining comments of #25 meander to a different issue that seems to have since been fixed, but this one remains.)Should the
README.md
suggestion be reversed, or does this count as another bug in one of the plugins?