Added a reasonable config for autoprefixer (resolves #73)

[kripod]

No description provided.

[ghost]

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla - and if you have received this in error or have any questions, please drop us a line at [email protected]. Thanks!

[ghost]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks!

[mxstbr]

Why would we put that in a global file and not config/webpack.config.*.js?

[gaearon]

Yeah, this should be a part of Webpack configs.

[alexzherdev]

The original issue #73 mentions an issue with css-loader which could be fixed via a browser list file, but it also mentions an alternative fix, so maybe that one could be used here. (supplying an option to css-loader)

[kripod]

@mxstbr @gaearon I thought following the DRY principle was a better way to go instead of filling the same values in twice. I could change it tomorrow if you want, though.

[gaearon]

We want to be explicit. It’s unclear which tool would read a file called browserslist from the root folder. Somebody might delete it without realizing the consequence because search won’t show it’s imported anywhere.

We don’t really care about DRY here, we care about explicitness so you can see how everything in config ties together.

[kripod]

I updated the PR, trying my best to follow your great advices.

[gaearon]

Thank you!