Consider switching from rework to postcss

[joeybaker]

We're using autoprefixer which is based on postcss. It would be nice to not have to parse the CSS twice – which we could do by switching rework for postcss. https://github.com/postcss/postcss/blob/master/README.md#plugins

[serapath]

I tried to understand the difference between the two, but actually i dont.
A quick search gives 283 results for ‘postcss-’ and https://www.npmjs.com/search?q=rework- on npmjs

I think i remember that they use the same css parser underneath? ...
Does it make sense about the variety of "features" in both eco-systems to compare them and see what they bring to the table?

[joeybaker]

They're tools that to do pretty much the same thing. rework uses css under the hood (that's the direct competitor to postcss AFAIK).

Good point on a feature comparison.

• both parse css and compile into a file
• plugins we use:
  • https://github.com/conradz/rework-assets becomes https://github.com/borodean/postcss-assets
  • https://github.com/cellvia/rework-bower becomes https://github.com/postcss/postcss-import
  • https://github.com/reworkcss/rework-npm also becomes https://github.com/postcss/postcss-import
  • https://github.com/reworkcss/rework-vars becomes https://github.com/postcss/postcss-custom-properties

Plus, we get the benefit of treating autoprefixer as a plugin instead of an additional parse + build step.

[serapath]

sounds great :-)