search

BlessCSS / bless

CSS Post-Processor
blesscss.com
MIT License
282 stars 60 forks source link

Consider using PostCSS #36

Open paulyoung opened 10 years ago

paulyoung commented 10 years ago

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.

Grawl commented 9 years ago

:+1:

paulyoung commented 8 years ago

@BlessCSS/contributors I think this is still valid.

mtscout6 commented 8 years ago

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 commented 8 years ago

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 commented 8 years ago

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 commented 8 years ago

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

mtscout6 commented 8 years ago

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

paulyoung commented 8 years ago

@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 commented 8 years ago

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

paulyoung commented 8 years ago

Done :+1: