-
-
Notifications
You must be signed in to change notification settings - Fork 608
Getting optimisation issue with some CSS #36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
PostCSS is backed by Autoprefixer, so it's probably developed more actively. 👍 |
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. |
Yes, write a PR... I've already tried to use an alternative library in the The |
rework is kind of unmaintained (last commit is from august 2014). |
yeah... I'm fine if you do a PR with postcss. |
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. |
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. |
Oh just saw you fix. Ouch. |
Closing since you now use postcss |
When I use
webpack -p
, I'm getting a non helping error messageIn this index.css I just have some inlined
@import
, so this error is not really helping.Is there any way to improve that?
My first import is normalize.css and after taking a look in the
<style>
element I saw some empty:root
elements (due to the fact I use future proof CSS transformed via cssnext).It seems the parser you are using is kind of outdated for some part.
If you are using csso for minification, would you consider switch to a more fresh tool (csswring) based on an parser with an active development (postcss)?
The text was updated successfully, but these errors were encountered: