You only need props hydration if you need SSR. However, there's no good reason to have your app make a second round trip to the Rails server to get initialization props.
Server-Side Rendering (SSR) results in Rails rendering HTML for your React components. The main reasons to use SSR are better SEO and pages display more quickly.
If you desire more advanced React-integration, like server-side rendering, SSR with react-router, SSR with code splitting, then you should consider these gems:
Gem | Props Hydration | Server-Side-Rendering (SSR) | SSR with HMR | SSR with React-Router | SSR with Code Splitting | Node SSR |
---|---|---|---|---|---|---|
shakacode/react_on_rails | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
react-rails | ✅ | ✅ | ||||
webpacker-react | ✅ |
Note, Node SSR for React on Rails requires React on Rails Pro.
If you're not concerned with view helpers to pass props or server-side rendering, you can do it like this:
<%# views/layouts/application.html.erb %>
<%= content_tag :div,
id: "hello-react",
data: {
message: 'Hello!',
name: 'David'
}.to_json do %>
<% end %>
// app/javascript/packs/hello_react.js
const Hello = props => (
<div className='react-app-wrapper'>
<img src={clockIcon} alt="clock" />
<h5 className='hello-react'>
{props.message} {props.name}!
</h5>
</div>
)
// Render component with data
document.addEventListener('DOMContentLoaded', () => {
const node = document.getElementById('hello-react')
const data = JSON.parse(node.getAttribute('data'))
ReactDOM.render(<Hello {...data} />, node)
})
Before turning HMR on, consider upgrading to the latest stable gems and packages: https://github.com/rails/webpacker#upgrading
Configure config/webpacker.yml
file:
development:
extract_css: false
dev_server:
hmr: true
inline: true
This basic configuration alone will have HMR working with the default webpacker setup. However, an code saves will trigger a full page refresh each time you save a file.
Webpack's HMR allows the replacement of modules for React in-place without reloading the browser. To do this, you have two options:
- Steps below for the github.com/pmmmwh/react-refresh-webpack-plugin.
- Deprecated steps below for using the github.com/gaearon/react-hot-loader.
github.com/pmmmwh/react-refresh-webpack-plugin
You can see an example commit of adding this here.
- Add react refresh packages:
yarn add @pmmmwh/react-refresh-webpack-plugin react-refresh -D
- Update
babel.config.js
addingplugins: [ process.env.WEBPACK_DEV_SERVER && 'react-refresh/babel', // other plugins
- Update
config/webpack/development.js
, only including the plugin if running the WEBPACK_DEV_SERVERconst ReactRefreshWebpackPlugin = require('@pmmmwh/react-refresh-webpack-plugin'); const environment = require('./environment') const isWebpackDevServer = process.env.WEBPACK_DEV_SERVER; //plugins if (isWebpackDevServer) { environment.plugins.append( 'ReactRefreshWebpackPlugin', new ReactRefreshWebpackPlugin({ overlay: { sockPort: 3035 } }) ); }
- Add the
react-hot-loader
and@hot-loader/react-dom
npm packages.
yarn add --dev react-hot-loader @hot-loader/react-dom
- Update your babel config,
babel.config.js
. Add the pluginreact-hot-loader/babel
with option"safetyNet": false
:
{
"plugins": [
[
"react-hot-loader/babel",
{
"safetyNet": false
}
]
]
}
- Add changes like this to your entry points:
// app/javascript/app.jsx
import React from 'react';
+ import { hot } from 'react-hot-loader/root';
const App = () => <SomeComponent(s) />
- export default App;
+ export default hot(App);
- Adjust your webpack configuration for development so that
sourceMapContents
option for the sass loader isfalse
:
// config/webpack/development.js
process.env.NODE_ENV = process.env.NODE_ENV || 'development'
const environment = require('./environment')
// allows for editing sass/scss files directly in browser
+ if (!module.hot) {
+ environment.loaders.get('sass').use.find(item => item.loader === 'sass-loader').options.sourceMapContents = false
+ }
+
module.exports = environment.toWebpackConfig()
- Adjust your
config/webpack/environment.js
for a
// config/webpack/environment.js
// ...
// Fixes: React-Hot-Loader: react-🔥-dom patch is not detected. React 16.6+ features may not work.
// https://github.com/gaearon/react-hot-loader/issues/1227#issuecomment-482139583
+ environment.config.merge({ resolve: { alias: { 'react-dom': '@hot-loader/react-dom' } } });
module.exports = environment;