Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing PostCSS vs Pleeease, the Slant community recommends PostCSS for most people. In the question“What are the best CSS preprocessors/postprocessors?” PostCSS is ranked 4th while Pleeease is ranked 12th. The most important reason people chose PostCSS is:
PostCSS is 3-30 times faster than Sass (including libsass), Less, and Stylus
Question Ranking
Pros
Pro Fast
PostCSS is 3-30 times faster than Sass (including libsass), Less, and Stylus
Pro Flexible
PostCSS allows you to opt-in to the features you need with plugins. This allows you to set it up to behave exactly like Sass, with nesting, mixing, extends, and more. On the other hand, it allows you to use plugins by themselves for things like auto-prefixing, minification, and more. You can even set up your own custom "stack" of plugins to do exactly what you like.
Pro Doesn't force designers to learn a new syntax
Rather than learn a different syntax, PostCSS allows you to write in pure CSS.
Pro JavaScript-based out of the box
Since it's basically CSS extended through JavaScript it works in the browser directly without the need to compile it beforehand.
Pro All-in-one post processor
preprocess CSS (experimental)
adds prefixes, based on Autoprefixer
provides fallbacks for rem unit, CSS3 pseudo-elements notation
adds opacity filter for IE8
converts CSS shorthand filters to SVG equivalent
packs same media-query in one @media rule
inlines @import styles
minifies the result
generates sourcemaps from pre- to postprocessors
Pro Combines media queries into single rules
If you have repeated media queries in your stylesheet, Pleeease will pack them into a single media query when compiled.
Pro Rem fallback
Rem unites are not supported in IE8 and below, so Pleeease provides a pixel fallback.
Pro Uses Autoprefixer
Pleeease uses Autoprefixer to add vendor prefixes based on which browsers you want to support (prefixes are added based on information from caniuse.com.
Cons
Con Harder to install and keep working
The immense flexibility of PostCSS plus its current rapid evolution makes it harder to install, configure and keep running than the more monolithic and mature preprocessors.
Con Outdatet, plugins are often based on different postcss versions and don't work together properly
Con Some plugins need to run in a certain order
Some plugins can only work if initialized after some other plugins. For example, transforming and applying CSS variables needs to run before running a plugin which uses these variables inside conditional transformations.
Con Not very popular
Pleeease is not very popular. This may make finding guides, tutorials or resources outside the official ones difficult.
