Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upAutoprefixer is now deprecated #196
Comments
|
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? |
|
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. |
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.
As a workaround for console spam, I've temporarily updated my
Gemfileto explicitly require Autoprefixer (even though I don't use it) v9.8.5.