README.md

postcss-compare-packs

Compare most popular PostCSS packs like cssnext, rucksack and PreCSS

PostCSS Plugin	postcss-cssnext	rucksack	PreCSS
autoprefixer	✅	✅
laggard		✅
pixrem	✅
pleeease-filters	✅
-advanced-variables			✅
-alias		✅
-atroot			✅
-calc	✅
-clearfix		✅
-color-function	✅		✅
-color-gray	✅
-color-hex-alpha	✅
-color-hwb	✅
-color-rebeccapurple	✅
-color-rgba-fallback	✅
-custom-media	✅		✅
-custom-properties	✅		✅
-custom-selectors	✅		✅
-easings		✅
-extend			✅
-font-variant	✅
-fontpath		✅
-hexrgba		✅
-initial	✅
-input-style		✅
-media-minmax	✅		✅
-mixins			✅
-nested			✅
-nesting	✅		✅
-partial-import			✅
-position		✅
-property-lookup		✅	✅
-pseudo-class-any-link	✅
-pseudoelements	✅
-quantity-queries		✅
-responsive-type		✅
-selector-matches	✅		✅
-selector-not	✅		✅

What does it mean if a plugin exists in more than one pack?

Assuming that each pack should focus on just one topic, it's an indicator that one of the pack did not achieve this strategy or the aspect of the topic was chosen wrongly. Read more in the PostCSS Plugin Guideline - Do one thing, and do it well

Can I use multiple packs at once?

Yes. You might need to figure out in which order you need to use them.

If I use multiple packs does the order matter?

It depends on the plugin(s). Some plugins contains a note in the Readme like postcss-import. If you want to use precss and cssnext, precss need to be loaded before cssnext.

What does happen to the output if a plugin is executed by more than one pack?

It depends on the plugin. But the autoprefixer for instance doesn't do anything if it will process the data a second time.

Can I disable particular plugins within a pack?

Every pack should provide an options argument to disable particular plugnis.
cssnext provides a browsers option to enable/disable features automatically based on the caniuse database.