-
Notifications
You must be signed in to change notification settings - Fork 755
uninitialized constant React::ServerRendering #498
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
do you have the whole stack trace? could you share it? |
(the stack trace includes really useful information, like what code is triggering the error and what code path made it happen!) |
Hey thanks for replying, here is our stack trace
|
Hmm so it doesn't event start, this is Rails 3.2 .... |
Our tests run |
I wonder if swapping the https://github.com/reactjs/react-rails/blob/master/lib/react-rails.rb#L2-L3 The line in question is inside |
Hey, Our ruby version is 1.9.3 & rails is 3.2.12. We will try changing the require order. If that fixes it we will let you know. Thanks, |
Hey, We altered the order of the require statements and it fixed one of the problems. Before when we were in the console and we went require 'react-rails' we would get the error that I posted earlier. Now we get 'true' back, but our broken page gives this error. undefined method `react_component' for #<#Class:0x000000061219b0:0x007f5b44a95410>> Thanks for your quick replies! |
Full stack trace? |
Hi, just stepping in for @reinkaos as he is busy
|
That line 5 is |
Hmmm it should come from the https://github.com/reactjs/react-rails/blob/master/lib/react/rails/view_helper.rb#L19 Which gets included by the Railtie: https://github.com/reactjs/react-rails/blob/master/lib/react/rails/railtie.rb#L43 I wonder why it's not there ... |
The same page works without issues in development and test environments. The gem is bundled correctly on the staging server but it seems like it's not being loaded correctly as when I open a rails console and go |
Does that mean it's used for Could you try moving it out of the assets group? |
We've tried that but now we're getting a different error
|
😢 a new surprise around every corner! That's the same error we saw earlier, but only with Sprockets 3! #443 (comment) |
I hope you were able to find something that works for you! |
Hey,
We are getting an issue on our staging server where this gem appears to not be loading correctly. It is giving us this error.
uninitialized constant React::ServerRendering
The gem is working fine on development.
Thanks,
The text was updated successfully, but these errors were encountered: