-
Notifications
You must be signed in to change notification settings - Fork 755
Can't install it.. - Rails 4.2 #331
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
Comments
Could you post your gemfile.lock? I think it's a conflict with a Sprockets/sprockets-rails version |
@dyatlov this is fixed on master. Can you give it a try? |
@vipulnsward thanks, trying |
@vipulnsward unfortunately, vagrant@vagrant:/vagrant$ rails g react:install |
Same here, but a different error from one of my initializers. Seems a class loading issue, as that initializer works fine when loading the app normally. I will install manually... |
Btw.: To avoid name clashes I would call the folder rather react_components than components. |
One more thing: :) The generator assumes the manifest is called |
Ah, turns out the generator error here is not limited to the generator.
|
Fixed it, had to include the will_paginate gem before the react-rails gem in the gemfile. |
Wow, how strange! I never heard of an order dependency in a Rails Gemfile before! |
Yep, odd. But I did have it before. :) I think it probably has to do with what react-rails does when it is required. It seems to load my initializers - not every gem does that. And if the will_paginate gem is not loaded first, the initializer breaks. |
Seeing the same thing with |
This looks like the commit that changed it #347. Weird that we're both running into issues with I've also been able to fix it by requiring in the will_paginate initializer: require 'will_paginate/view_helpers'
require 'will_paginate/view_helpers/action_view' |
I can confirm a similar load order issue with the mobile-fu gem. |
I can confirm similar issue with
regarding to RolifyCommunity/rolify#156 there's something wrong in the react-rails initializer |
Sorry, it's been quite a while since I heard about an instance of this issue. If someone finds it again, please let me know and I'll see if any changes to our railtie can fix it! |
rails g react:install
The text was updated successfully, but these errors were encountered: