-
Notifications
You must be signed in to change notification settings - Fork 134
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
Uncaught ReferenceError: ReactDOM is not defined #42
Comments
I had this issue and it turned it to be caused because I was trying to use the graphiql gem on an API only rails project. |
i had a same issue! what is the solution? |
Which middlewares to add ? |
I had a play with the graphiql-rails gem. I tried bumping the graphiql version and re ordering the assets with no luck. Then I added a 500ms delay so the assets are all loaded. It's not elegant but it's a temporary fix.
|
Also I just noticed the error trace has turbolinks in it. Does this happen on a direct visit to |
Yes @rmosolgo, that fixed it. I disabled turbolinks in my rails 5.2 app with:
Thanks team! |
@Spots did you manage to get this working using an API only project? |
Hey Team,
I'm getting a
Uncaught ReferenceError: ReactDOM is not defined
error when trying to load/graphiql
in my app. Hitting refresh fixes the problem. The issue occurs on multiple browsers and with extensions disabled.I've tried updating to the latest gem versions.
And the console error is
Any suggestions for further troubleshooting?
Cheers Team!
The text was updated successfully, but these errors were encountered: