Question 1

How do I add React to an existing Rails app?

Accepted Answer

Run `bundle add react_on_rails --strict && rails g react_on_rails:install` from the README, then use `<%= react_component("HelloWorld", props: { name: "World" }) %>` in Rails views. This sets up the integration without separate API calls.

Question 2

React on Rails vs Next.js for a Rails backend?

Accepted Answer

React on Rails keeps Rails as the main app with React integrated into views, ideal for incremental upgrades. Next.js is better for React-first SPAs with Rails as an API, but requires splitting frontend/backend concerns and loses Rails' cohesive conventions.

Question 3

Does React on Rails support React 18 and server components?

Accepted Answer

Yes, v16 adds enhanced React Server Components support in the Pro version, but the OSS version uses ExecJS for SSR which is slower. The README notes Pro includes Node renderer for faster SSR and RSC.

Question 4

What's the difference between OSS and Pro versions?

Accepted Answer

OSS includes basic SSR, hot reloading, and Rspack support. Pro adds React Server Components, streaming SSR, fragment caching, and Node-based rendering for 10-100x faster performance, as shown in the feature matrix.

Question 5

How to handle state management with Redux?

Accepted Answer

React on Rails has built-in Redux integration with server-side rendering support, allowing state to be hydrated from Rails. The README mentions this under 'Router & State Integration' for complex state needs.

Question 6

Is server-side rendering fast with the open-source version?

Accepted Answer

OSS uses ExecJS for SSR, which is slower than Node.js; the README admits Pro's Node renderer is 10-100x faster. For high-traffic apps, this performance gap might necessitate upgrading to Pro.

react_on_rails

What is react_on_rails?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions