Yet there is one problem—so far, all of our work using Pleeease is PostCSS-based; what if we had been using a processor such as SASS as the basis for producing our code?

Unfortunately, this is where Pleeease falls down—although it does include support for SASS, Stylus, and Less, it is still very experimental. An example of where this causes an issue is in nesting; Pleeease has yet to support nesting when configured to use SASS. This reduces the appeal of using Pleeease—after all, one of the key reasons for using PostCSS is to remove any dependency on libraries such as SASS!

To get around this means using the gulp-sass plugin. This is a wrapper for the libsass library. To achieve this, we would add a task such as this to our Gulp task file:

When using this method, we can pre-compile our SASS code to valid CSS before transforming it with PostCSS plugins. The trouble is, it seems an inefficient way to compile our code—there is a better alternative, in the form...