search

bdkjones / CodeKit2

CodeKit 2 Beta
97 stars 4 forks source link

Autoprefixer CLI is deprecated. Use postcss-cli instead. #576

Open Andreyco opened 9 years ago

Andreyco commented 9 years ago

screen shot 2015-08-13 at 21 09 16

https://github.com/postcss/autoprefixer#cli

Similar to #570, where they require to replace Autoprefixer with CSSNext.

nicholaspetersen commented 9 years ago

I'm having the same issue

johnchourajr commented 9 years ago

Me as well.

markhowellsmead commented 9 years ago

Same here.

bdkjones commented 9 years ago

You can safely ignore this warning. I'll make sure it's silenced in the next update.

ghost commented 9 years ago

Hi, Bryan.

I'm getting the same error, but I've looked at my compiled CSS and Autoprefixer isn't working.

Autoprefixer failed with this error: Autoprefixer CLI is deprecated. Use postcss-cli instead.

bdkjones commented 9 years ago

Please show me the output you're getting and what it should be. Thanks.

kylegillen commented 9 years ago

I'm having the same issue, but only ever since upgrading to OS X El Capitan 10.11. Also seeing the following warning alongside the aforementioned:

Ignoring ffi-1.9.6 because its extensions are not built. Try: gem pristine ffi --version 1.9.6

@bdkjones did mention that it may be conflicting gems, I uninstalled all system gems and am still having the same issue. Any ideas?

mauricenaef commented 8 years ago

Having the same issues as @nextriot. Any update on the problem? Looks like it has to to with the new way El Capitan handles System Integrity Protection (SIP)? Thanks.

bdkjones commented 8 years ago

Autoprefixer is not a Ruby-based tool; it's built on Node and JavaScript. The gem issues should not be related to AP.

jamiedumont commented 8 years ago

Ongoing issue for me too. Autofixer no longer works and produces the above error when enabled.

razorfever commented 8 years ago

I just had the same issue for the first time. I'm still running Yosemite though. screen shot 2015-10-14 at 10 37 08

bdkjones commented 8 years ago

Autoprefixer should be running just fine, despite the annoying warning. If AP is not generating the output you expect, please post a test file I can use over here and the A) Expected and B) Actual output you're getting. Please also be sure to specify the browser string you've set for AP in the project settings area.

bdkjones commented 8 years ago

Oh. Just saw the "internal error" in the screenshot above. That is not related to the warning about the CLI deprecation.

Usually, "internal error" means that your Browser String is invalid. (AutoPrefixer doesn't have the best error messages.) It can also show up if your CSS is not valid.

razorfever commented 8 years ago

@bdkjones Thanks for the reply. I managed to sort out my problems with the autoprefixer based on your advice above. I had commented the only line in my sass block like this:

.ui.grid-cell {
/* height: 56px; */
}

Commenting the whole block seems to have cleared the forementioned issue I was having. Still getting the warning about Autoprefixer CLI being deprecated, but it still runs through ok.