Remove autoprefixer?

[madeleineostoja]

Toying with the idea of stripping out autoprefixing from Rucksack. I think nowadays Autoprefixer is mainstream enough that people already know about it as a solution to vendor prefixing, so a framework like this doesn't really need to include it out of the box.

If separated it also makes Rucksack more flexible, as Autoprefixer has to run after any other PostCSS plugin that uses prefixed features. Rucksack shouldn't have that restriction. At the very least we could set it to disabled by default.

If anyone has any strong thoughts on this please chime in.

[bedeoverend]

I'd say at least make it disabled by default, I think it's a nice feature to have, and given that it's in almost every project it's worth having, but given that it forces rucksack to be used at a certain position, it shouldn't be enabled by default, leaving the user to use it as they wish.

Having said that, would be interested to hear other people's feedback.

[JBValo]

I would second @bedeoverend's comments here. I have Autoprefixer already implemented in my workflow so it's not needed within Rucksack. I'm also thinking it should be disabled by default, but still an option if certain folks would like to use it.

[yeojz]

In my opinion, if autoprefixer starts hindering future development, then it should be left out.. Else no downsides in leaving it in.

As with above comments as well... Personally I always have autoprefixing in my work flow.

However it is nice to have just a toggle for small projects which do not need any complicated work flow and have autoprefixer as an option out of the box.

[jczimm]

+1 to disabled by default

[madeleineostoja]

Alrighty, I'm of the same mind. I'll set all addons (ie: Autoprefixer and legacy fallbacks) to disabled by default in the next major version bump - which will probably when #13 is closed.

As for what counts as an 'addon', basically any tranforms that are done to your entire codebase, without using a specific Rucksack feature. It's pretty obvious that these wouldn't be wanted by everyone, so I think it makes sense to disable them both by default out of the gate.