-
-
Notifications
You must be signed in to change notification settings - Fork 188
should be able to return a postcss plugin #3
Comments
why not expose it like |
This issue was a reminder but can be handled this way (by return a postcss plugin). |
FYI, here is the blocker postcss/postcss#74 |
Well, we can forget this idea, people can use plugins by themselves. |
hmm, i think exposing it as a plugin would be pretty useful and easy. |
Can't be done for now. I'm waiting for a postcss change here to make this happen postcss/postcss#74 (please give your opinion over there @necolas :) |
Ok I've made a pr so postcss.use() can consume plugin of another postcss instance. This PR is merged in tokenizer branch (future v3).
I just need to return postcss instance when there is no string given has a first param to be ready for that :) |
This will be nice when postcss 3 will be released Ref #3
Done. |
The text was updated successfully, but these errors were encountered: