Core Concepts | React on Rails

📄️ How React on Rails Works (with Shakapacker)

Note, older versions of React on Rails pushed the Webpack bundles through the Asset Pipeline. This older method has many disadvantages, such as broken sourcemaps, performance issues, etc. If you need help migrating to the current way of bypassing the Asset Pipeline, email Justin.

📄️ Client-Side Rendering vs. Server-Side Rendering

Also, see our React server-rendering documentation.

📄️ React Server Rendering

📄️ Render-Functions and the Rails Context

Render-Functions

📄️ React on Rails Render-Functions: Usage Guide

This guide explains how render-functions work in React on Rails and how to use them with Ruby helper methods.

📄️ Auto-Bundling: File-System-Based Automated Bundle Generation

To use the automated bundle generation feature introduced in React on Rails v13.1.0, please upgrade to use Shakapacker v6.5.1 at least. If you are currently using Webpacker, please follow the migration steps available v6 upgrade. Then upgrade to Shakapacker 7 using v7 upgrade guide.

📄️ Webpack Configuration: custom setup for Webpack or Shakapacker?

Webpack vs. Shakapacker

📄️ ExecJS Limitations

React on Rails uses ExecJS as the default server-side rendering engine. ExecJS provides a common interface to several JavaScript runtimes (Node.js, mini_racer, etc.) and works well for basic server rendering, but it has important limitations to understand.

📄️ Performance Benchmarks

The point of this page is not to admire numbers. It is to help you make a page measurably