The API is intentionally transparent. The idea is that you're still writing in the CSS language (even if with non-spec features), rather than a DSL. So if you ever did want to rip Rucksack out and go back to-spec, you'd just run it and grab the output. Your overall structure, logic, and code would look pretty much the same, just with the (expanded) additions of the individual features Rucksack added. This often isn't the case when you're writing in a preprocessor, especially on a big project the input often ends up looking very little like the output.

And to clarify, yep Rucksack certainly isn't to-spec (present or future). It's a collection of handy features and shortcuts, like the compass/nib/bourbon of PostCSS. As timdorr points out, you could absolutely use it with cssnext (we do exactly that over at Simpla), you'd probably just want to disable autoprefixing, since cssnext does that for you.

Do you mean cssnext? http://cssnext.io/

If so, that is also built on PostCSS and could be combined with this pack. Rucksack is just a packaging of other PostCSS plugins: https://github.com/simplaio/rucksack/blob/master/index.js#L6...

Yeah we're thinking of enabling users to pass through option blocks to the individual plugins (like how precss and cssnext does things), the problem is that not all features match 1:1 with plugins. Legacy Fallbacks, for instance, is a sub-collection of 5 plugins, and passing a nested object to each of these would be awkward. Also most of the plugins used (and all of the ones I built for it) are pretty straightforward and don't take any options.

But feel free to chuck an issue up on github, this behaviour probably needs to be accounted for sooner or later.