Javier Julio

@cparker-ajla thanks! Now we are getting a different error. I think the problem may be related to the gemspec path and gemfiles based on what I look up for that...

No problem! Thanks for tackling this. Let me know if you have an update and/or need help. I'm not familiar with appraisals so I'm not sure why the builds are...

@jkimmeyer keep in mind ActiveAdmin may **not** be changing to sassc after all because it may not be necessary. The PR for that has updated info in comparison to the...

@pmichaeljones no need to do that dependency change: https://github.com/rails/sass-rails/pull/424

Ah sorry. In that case it will have to update. I wonder though if this should just rely on sass-rails instead since this is a Rails asset gem.

Just to follow up, `foundation-rails` should be updated to depend on either `sassc-rails` or `sass-rails`. The difference is that the latter is just a thin wrapper around the former with...

@lilliealbert that's great because before posting this we were talking about that on the RB NYC slack. They want to do the same thing, get our docs fork changes back...

@lilliealbert yes finding out now that its probably way way off whatever we decide to do. We'll see if we can figure that out. Although this doesn't change anything for...

@vfonic the wrong file was updated. At the top it'll have a comment that its an auto generated file. This is [the script you should update](https://github.com/activeadmin/activeadmin/blob/master/app/javascript/active_admin/lib/per-page.js) here.

@ananth99 I had a similar error and the following https://github.com/prontolabs/pronto/issues/103 resolved it for me. Give it a try.