Examples and migration references

Use concrete repos and concrete guides when deciding whether React on Rails fits.

These links are for evaluation, migration, upgrade, and validation work. They are supporting material for the docs, not a parallel docs track.

Start with a decision path

Choose the guide that matches your migration or evaluation goal.

Evaluator path

Read the evaluator guide first to compare React on Rails with Hotwire/Turbo, Inertia Rails, and react-rails.

Migration path

Follow a migration sequence that now accounts for both Webpacker-era apps and newer Vite-style `react-rails` repos.

Upgrade path

Use the upgrade guide when the app already depends on React on Rails and you need the current preflight before version bumps.

Reference repos

React on Rails app on an older Webpacker-era stack that exposed `pg` lockfile issues before the upgrade could begin.

Modern Rails + Shakapacker + React on Rails app used to validate upgrade preflight guidance and exact-version expectations.

React-rails app with a newer frontend toolchain that proved the migration docs needed a clearer Vite-era branch.

React-rails + Webpacker app that hit an old `nio4r` compile failure before any React on Rails migration steps could run.

Small vite_rails app used to validate `packageManager`, env-var, and generator-boot preflight notes.