Skip to content
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

Autoprefixer is now deprecated #196

Closed
pond opened this issue Aug 4, 2020 · 5 comments
Closed

Autoprefixer is now deprecated #196

pond opened this issue Aug 4, 2020 · 5 comments

Comments

@pond
Copy link

pond commented Aug 4, 2020

In version 9.8.6 and 9.8.6.1 of the Autoprefixer gem, deprecation warnings are now printed to the console. Aside from the large amounts of console spam, the gem documentation now makes it very clear that anyone using the gem is meant to move off it.

DEPRECATION WARNING: autoprefixer-rails was deprected. Migration guide:
https://github.com/ai/autoprefixer-rails/wiki/Deprecated (called from [...])

As a workaround for console spam, I've temporarily updated my Gemfile to explicitly require Autoprefixer (even though I don't use it) v9.8.5.

@aseroff
Copy link

aseroff commented Aug 12, 2020

Seems like unless this wrapper is refactored to use a different prefix library, rails applications are looking at a forced conversion from asset pipeline to webpacker, just to use babel? Or am I missing something?

@pond
Copy link
Author

pond commented Aug 12, 2020

I don't know or particularly care. The JavaScript / "asset management" crowd seem to think up new, even more complicated ways to do simple things every day of the week; all I know is that Bootstrap started spewing warnings because it depends on Autoprefixer, which is now end-of-life.

It's Bootstrap pulling in the dependency, not our application. So I don't care what it uses instead; it just can't keep using a gem that's now been killed off.

@ilikepi
Copy link

ilikepi commented Sep 10, 2020

We ran into this issue yesterday as well. On further investigation, it looks like someone has offered to take over maintainership (ai/autoprefixer-rails#168). In the meantime, we eliminated the warnings by locking autoprefixer-rails to version 9.8.5, which was the last release before the warnings were added. The changelog mentions something about fixing an "env option" in 9.8.6, but it's not immediately clear what that is. Otherwise all the more recent releases appear to have dealt with introducing the warnings.

Alternatively, it seems like it would be fairly trivial to monkeypatch the method that outputs the deprecation warning...looks like it's in lib/autoprefixer-rails/processor.rb.

@ilikepi
Copy link

ilikepi commented Sep 15, 2020

autoprefixer-rails 9.8.6.4 was released after ai/autoprefixer-rails#177 was merged to remove the deprecation warnings.

@glebm glebm closed this as completed Feb 26, 2021
@pond
Copy link
Author

pond commented Feb 27, 2021

Thanks for the updates on this & dealing with the various AutoPrefixer versions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants