Skip to content
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

Open
paulyoung opened this issue Jun 24, 2014 · 10 comments
Open

Consider using PostCSS #36

paulyoung opened this issue Jun 24, 2014 · 10 comments
Assignees

Comments

@paulyoung
Copy link
Contributor

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.

@paulyoung paulyoung self-assigned this Jun 24, 2014
@paulyoung paulyoung added this to the Version 4 milestone Jun 24, 2014
@paulyoung paulyoung added the v4 label Jun 24, 2014
@paulyoung paulyoung removed the v4 label Apr 26, 2015
@Grawl
Copy link

Grawl commented Jul 2, 2015

👍

@paulyoung
Copy link
Contributor Author

@BlessCSS/contributors I think this is still valid.

@mtscout6
Copy link
Member

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.

@paulyoung
Copy link
Contributor Author

There might be something better in the works that I can't discuss yet.

Wanted to make a note as a reminder for later.

@tomchentw
Copy link

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?

@paulyoung
Copy link
Contributor Author

Hi @tomchentw! I've added some information to #17, but probably best to coordinate with @mtscout6.

@mtscout6
Copy link
Member

@paulyoung Is this absolutely required for 4.0? Or can we kick it out of the v4 milestone?

@paulyoung
Copy link
Contributor Author

@mtscout6 I don't think it's a prerequisite for a 4.0 release. In theory it should be a backwards-compatible change anyway.

@mtscout6
Copy link
Member

Ok, do you mind if we drop it from the milestone then?

@paulyoung paulyoung removed this from the v4.0 milestone Sep 25, 2015
@paulyoung
Copy link
Contributor Author

Done 👍

@mtscout6 mtscout6 modified the milestone: v4.0 Sep 25, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants