-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider using PostCSS #36
Comments
👍 |
@BlessCSS/contributors I think this is still valid. |
Agreed, I'd rather approach this once we bring in the ES6 changes from #62 though. Should be equally simple to do with those changes. |
There might be something better in the works that I can't discuss yet. Wanted to make a note as a reminder for later. |
Hi @paulyoung I'd like to help out to make this happen. I really want this to be done in my postcss pipeline. Is there anything I could help with? Starting at #17? |
Hi @tomchentw! I've added some information to #17, but probably best to coordinate with @mtscout6. |
@paulyoung Is this absolutely required for 4.0? Or can we kick it out of the v4 milestone? |
@mtscout6 I don't think it's a prerequisite for a 4.0 release. In theory it should be a backwards-compatible change anyway. |
Ok, do you mind if we drop it from the milestone then? |
Done 👍 |
https://github.com/ai/postcss
In v4 it should be fairly trivial to switch parsers.
Look at this once #17 is complete.
Would address #33.
The text was updated successfully, but these errors were encountered: