Michael Dungan
Michael Dungan
handling it in the Gemfile works fine for me.
Yes, exactly. I just put it in as the first line in the Gemfile and all is well.
oh, make sure it's `ENV['RB_USER_INSTALL'] = '1'` (i.e. '1' is a string)
@kmurph73 The `rails_6_1_4` branch works for us. We didn't run into the visibility issue that @serch mentions above.
Is this ever going to get merged? We're approaching 2 years now.
I've done some work and got this working on 3.1, at the cost of backward compatability, so I won't send a pull request, but the commit is [here](https://github.com/stipple/acts_as_archive/commit/e5461f23599ff27c7a37a23dbd5244f93c7bdeca).
We also use Apollo and Pusher, and also get this warning, but it doesn't cause compilation failures in our case. example trace: ``` 13:56:37 webpack-dev-server.1 | WARNING in ./node_modules/graphql-ruby-client/sync/prepareRelay.js 41:22-47...
@rmosolgo Serendipitously, my teammate @pvenable recently tweaked our configuration with the following:  and we now compile clean, without any warnings at all.
We also started seeing these after updating to sassc v.2.4.0.