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

Open
pond opened this issue Aug 4, 2020 · 2 comments
Open

Autoprefixer is now deprecated #196

pond opened this issue Aug 4, 2020 · 2 comments

Comments

@pond
Copy link

@pond 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 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 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.

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

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.