BLblock_dagger·Dec 25, 2024
Try React on Rails [1]. I’ve found it to be a very pleasant development experience.
[1] https://github.com/shakacode/react_on_rails
In Ruby 3.4.0shakacode
react_on_rails
Ruby2015–2024
shakacode / react_on_rails
react_on_rails
Integration of React + Webpack + Rails including server-side rendering of React, enabling a better developer experience and faster client performance.
7Distinct people
11Mentions
1Explicit recommenders
5.2KGitHub stars
What to know before exploring
What it is
Integration of React + Webpack + Rails including server-side rendering of React, enabling a better developer experience and faster client performance.
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
React plus Rails is my favorite modern combo. Development bliss. https://github.com/shakacode/react_on_rails
block_dagger used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- reactjs/react-rails · linked in 2 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:03:16 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year11 dated mentions
Observed mentions: 2015-11-18 08:44:05 UTC to 2024-12-25 09:30:18 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 2 | 1 | 1 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 4 | 0 | 4 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 2 | 0 | 2 |
What Hacker News says
11 sourcesReact plus Rails is my favorite modern combo. Development bliss.
https://github.com/shakacode/react_on_rails
In Rewrite It in Railshey if stimulus and turbolinks are your jam then rock it!
I would at least give this a look though, it's super easy to use: https://github.com/shakacode/react_on_rails
In Stimulus.js 2.0Integration of React and Webpack and Rails
3 points · Open discussionDid anybody try https://github.com/shakacode/react_on_rails for this comparison?
In The Performance Cost of Server Side Rendered React on Node.jsYes, you certainly can. This is actually a topic that I've been exploring for a little while now.
http://www.openmindedinnovations.com/blogs/3-ways-to-integra... is a decent, although old article on the three different ways that it can be done.
I personally recommend https://github.com/shakacode/react_on_rails as the solution to this issue. Instead of merely providing you with React and React only like https://github.com/reactjs/react-rails does, it welds Node & Rails together to enable you to use the latest and greatest of the javascript ecosystem.
As for the benefits of doing so, having started my web development journey with Rails, I like to think that Rails provides an excellent convention for Backend MVC & ORM while Node gives you access to up-to-date javascript libraries & frameworks. Combining Node & Rails allows to you to exploit
Read the rest
the strengths of both systems in exchange for dealing with greater complexity.
React Rails[1] works fine: you just get React, and it's difficult to integrate other shiny React-associated stuff like Redux, but it makes it incredibly easy to build out an app, or even just sprinkle components throughout an existing Rails app. It's dead simple to get started, and I've found it generally Just Works; the whole team I work on has been using it for the last 4-5 months without any issues. Just add to Gemfile -> it sets up a components folder + a file that imports the file tree -> then optionally set initializer options (like include React Addons, or use stage-0 stuff). All exposed globals though, which is a pain, but that's generally expected with the asset pipeline unless you're very disciplined.
There's a pretty complete tutorial, but it's a bit out of date + uses CoffeeScript rather than JSX - I made a copy of the origina
Read the rest
l, with updates, for one of my colleagues, the gist is here (sorry, might be a little rough): https://gist.github.com/DanCouper/b6953544a34606617eb5
To get a bit deeper, there's React on Rails[2], which retains the same entry point, but moves all the JS to a separate folder at root, and uses Node to handle that side of things during development. The setup is batteries included, and pretty flexible, but I haven't used it a huge amount so can't give much detailed feedback.
1. https://github.com/reactjs/react-rails
2. https://github.com/shakacode/react_on_rails
Picking either in-office or "remote-first" is what matters most. Companies cannot optimally be both simultaneously.
I'm Justin Gordon, the founder of ShakaCode, http://www.shakacode.com. My article and video on telecommuting from Maui is still the number one google search result for "telecommuting maui": http://www.railsonmaui.com/blog/2014/05/06/remote-pair-progr....
I've been a full-time remote worker from Maui, since 2007, a remote freelancer since 2011, and over the last 2 years, I've run a remote consulting and product company. To brador, that says "Remote devs start to have mental health issues from the loneliness and lack of supervision in down times", I'd say that's total hogwash. We spend almost every day video chatting on Skype with people (team members and clients) around the world, and we are very often on ScreenHero sharing s
Read the rest
creens (often with Skype video), and always on Slack and github conversations. There is 100% no loneliness with this lifestyle. In fact, I'd say spending 1-2 hours a day commuting is a far bigger risk for physical and mental health issues!
Since I founded my company to be 100% remote-first, we've avoided many of the issues that face companies that are schizophrenic about remote work. I've heard numerous stories around Silicon Valley about how companies start allowing "work from home days" and then the senior managers see the parking lot 3/4's empty at 11am, and then there's an ultimatum that you have to work from the office unless you have specific management approval to work from home for one given day. And I'm NOT EVEN EXAGGERATING ONE BIT!
One of the keys to my firms success is to hire team members that love what they do, either programming or design, and that typically interact well on open source. To that end, I've found almost all my team members though our popular open source, https://github.com/shakacode/react_on_rails/ (1238+ stars), which is the number one package that integrates Ruby on Rails with React via Webpack and NPM.
https://github.com/shakacode/react_on_rails/ … over 900 ⭐! Help make it to 1000 ⭐!
In The React on Rails DoctrineI know of these two projects that offer some guidance to combining RoR with React:
https://github.com/shakacode/react_on_rails
https://github.com/netguru/react_webpack_rails
Basically, you introduce webpack as part of your dev/build pipeline, it interacts nicely with the asset pipeline.
In How to Structure React ProjectsReact_on_rails gem uses webpack, react, redux, server rendering
1 points · Open discussion