Getting optimisation issue with some CSS about css-loader HOT 9 CLOSED

PostCSS is backed by Autoprefixer, so it's probably developed more actively. 👍

from css-loader.

postcss 4 is really fast (just run this to check it out https://github.com/postcss/postcss/tree/master/benchmark ) & even support CSS specs that are not implemented in browsers. So seems a really good choice indeed.

from css-loader.

Yes, write a PR... I've already tried to use an alternative library in the rework branch.
Check that all test pass and maybe add some for the new stuff.

The rework branch doesn't work out, because it removed the whitespace from css and this would break SourceMap.

from css-loader.

rework is kind of unmaintained (last commit is from august 2014).
More & more people are switching to postcss now that the ecosystem start to be consistent.

from css-loader.

yeah... I'm fine if you do a PR with postcss.

from css-loader.

Since a rewrite with PostCSS is probably rather expensive, we should add a quickfix for the status quo because the current problem renders the css-loader useless.

from css-loader.

A rewrite with postcss should be pretty quick since postcss-import can do the inline & postcss-url can do accept a callback to handle what to do with the url.
A "quickfix" should be to fix the parser, which seems heavier to me than using postcss-import + url plugins...

from css-loader.

Oh just saw you fix. Ouch.

from css-loader.

Closing since you now use postcss

from css-loader.