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
Bump autoprefixer-rails #39
Conversation
Problem ------- `autoprefixer-rails` v 9.x was reporting deprecation warnings everytime you did a build or serve. ``` DEPRECATION WARNING: autoprefixer-rails was deprected. Migration guide: https://github.com/ai/autoprefixer-rails/wiki/Deprecated (called from load at /Users/jon/.rbenv/versions/2.6.5/bin/middleman:23) ``` Some futher investigation makes me think it's not in fact deprecated but has picked up some new owners and is still in development. Solution --------- Bump to the new version (10.0.1) to suppress the error message. I tested this locally by building a current middleman project and the css that came out was identical to the previous version. Also your tests still pass.
It looks like the new version of autoprefixer wants a more modern version of Node - more modern than what's on Travis. Will you support that bump as well? |
Wait... nevermind. This does not work because of a typo fix in |
I'll leave this one until autoprefixer get's that fix in. |
The issue I was seeing is fixed on |
I think adding the following to the travis config will help those errors:
|
This reverts commit f9819a6.
Merged this manually here: f9efe59 Will get a release out soon. |
Problem
autoprefixer-rails
v 9.x was reporting deprecation warnings everytimeyou did a build or serve.
Some futher investigation makes me think it's not in fact deprecated but
has picked up some new owners and is still in development.
Solution
Bump to the new version (10.0.1) to suppress the error message.
I tested this locally by building a current middleman project and the
css that came out was identical to the previous version. Also your
tests still pass.