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
{{ message }}
This repository has been archived by the owner on Dec 19, 2024. It is now read-only.
Some people include cssnext after other plugins, but since cssnext handle import by default, it should be the first so, if possible:
if cssnext has default options || import to true && import hasn't been piped yet, should throw if not the first plugin
if cssnext has default options || import to true && import has already been piped, should disable import (& should emit a warning ?) if not the first plugin
if cssnext has import to false, just check nothing, people probably know what they are doing
That would avoid people doing mistake.
The text was updated successfully, but these errors were encountered:
I have nested and nested-props running on each import, which is why I also have nested and nested props running before cssnext. Basically, I don't want it trying to unwrap nested syntax more than once for the same code, so it unwraps nesting on the non-imported code first, then unwraps nesting on each import as they come.
Some people include cssnext after other plugins, but since cssnext handle import by default, it should be the first so, if possible:
That would avoid people doing mistake.
The text was updated successfully, but these errors were encountered: