You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During debug tracing, for development, we put a message that SSR ran, but in fact it didn't. This seems to happen if the server bundle is created but doesn't have runnable code (?)
Not a high priority bug.
Easy to see that SSR did not run by looking at the page source.
Also, if the development mode is configured to throw errors on server rendering failure, then the error is obvious.
Best to configure config/initializers/react_on_rails.rb:
During debug tracing, for development, we put a message that SSR ran, but in fact it didn't. This seems to happen if the server bundle is created but doesn't have runnable code (?)
Not a high priority bug.
Easy to see that SSR did not run by looking at the page source.
Also, if the development mode is configured to throw errors on server rendering failure, then the error is obvious.
Best to configure config/initializers/react_on_rails.rb:
and not just always false.
The text was updated successfully, but these errors were encountered: