Remove Autoprefixer from cssnano

[ai]

css-loader contains cssnano to compress CSS. cssnano by default contains Autoprefixer to remove all prefixes. It works great when you undertand what you want to do. But because css minifier feature is hidden inside webpack many people don’t expect that webpack will remove prefixes.

Right now I have so many issues in Autoprefixer repo about this issue.

So I suggest to remove autoprefixer rule from cssnano in css-loader.

@ben-eb do you agree as cssnano author?

@sokra we have problem right now, because in latest Can I Use update iOS 8 was removed from default last 2 versions browsers list and many people are in pain.

[ai]

Of course, there is a much better way. Put browserslist config to project root, so every tool will use same browsers (Autoprefixer, cssnano, doiuse, cssnext). But many people don’t know about it.

I posted a tweet about this solution. But your know, people don’t read a docs.

[ai]

I added this question to Autoprefixer FAQ, but I still think that we should fix it in css-loader too

[ben-eb]

Sure, if it is causing confusion. 👍

I plan to remove this option anyway for version 4 but it's a while away.

[dmiller9911]

@ai I am curious if the browserslist still works. I created one, and it seems to be ignored. After doing some digging I found that the path being sent to browserslist is something along the lines of:

c:\css-loader!c:\src\node_modules\postcss-loader\index.js!c:\src\node_modules\less-loader\index.js!c:\src\foo.less

The c:\css-loader seems to be coming from here

The problem with this is that browserslist will tick down each dir until it finds the config file, but with this path it will never find one unless it is sitting in c:.

loader config below:

{ loader: 'style!css!postcss!less', test: /.less$/ }

[ai]

@dmiller9911 it is a bad place for other issue :). Could you:

1. Check that you use latest version of postcss-loader (I fixed path issue in previous release)
2. Create a issue in postcss-loader if you still have a issue.

[robwierzbowski]

Second this removal. I highly prefer single responsibility packages used as peers. Lessons from the grunt do everything for everyone days.

[ai]

@sokra do you need PR for it? (It is just one small option).

[ai]

@sokra ping

[ai]

@sokra could you say anything? :) It is very sad to have no feedback.

This issue is very important for me, because users write me about it.

[SpaceK33z]

@ai, sokra has limited time atm since he has holidays. I agree with you here. I can push the fix, but since I don't maintain css-loader (do have permissions though) I want to get feedback from at least one other member of the core team.

[ai]

@SpaceK33z done #361

[ai]

Still waiting for release 😉.

Users still report a issue and I need to spend time to explain problem
webpack-contrib/postcss-loader#134

[ai]

Other example of issue, where we spend time, because this issue is not released webpack-contrib/postcss-loader#81

[ai]

@SpaceK33z please, write anything about this issue. It is very painful when everyone just ignore you :(.

The new issue in Autoprefixer about this issue: postcss/autoprefixer#747

Please release it. I know that open source developers always don’t have time. But right now I spend my time, because of this issue.

[SpaceK33z]

@ai, I'm really sorry. I didn't have npm publish permissions and it took me a while to get them. I have them now and I'll release a new version today.

[SpaceK33z]

@ai, published 0.26.0. Sorry again, I fully understand your frustrations about how we handled this.

[ai]

Thanks! 😊