Any interest in a node renderer for reactjs/react-rails?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 18/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript, node.js, rails, react
- Domain
- backend
Research direction
The issue names no files or tests. Start by reviewing the existing renderer and how react-rails uses ExecJS, then assess the scope of a Node.js renderer. The issue does not define acceptance criteria, so the implementation boundaries and tests would need to be agreed before work starts.
Written by the indexing model from the issue text.
Description
I've had a proper node renderer for quite some time for React on Rails Pro.
It's becoming increasingly useful to use NodeJS and not ExecJS for server-side rendering. Here are a few reasons:
- loadable-components and CSS in JS Emotion just work when using a proper node server and a build target of
node(and notweb). I suspect many other libraries are the same in this regard. - Better for memory management
- Maybe better performance (and certainly if your Ruby process is running out of memory due to JS leaks)
- Options to debug using the Chrome dev tools.
- Ability to have SSR code read the file system, make asynch calls, and really anything a proper node program can do.
If there was sufficient interest, I could look into a port of the renderer that worked for react-rails.
- Dominant language
- JavaScript
- Stars
- 6.8k
- Forks
- 739
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from reactjs/react-rails
-
Documentation
Difficulty 4/5 3-5 days Newbie friendliness 45/100
reactjs/react-rails#1380 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
reactjs/react-rails#1355 · 1 comment · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
reactjs/react-rails#1351 · 4 comments · 10 reactions ·
-
discussion
Difficulty 4/5 3-5 days Newbie friendliness 35/100
reactjs/react-rails#1341 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
reactjs/react-rails#1338 · 3 comments ·
All issues in reactjs/react-rails
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
avniproject/avni-client#2135 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
babalae/bettergi-scripts-list#3674 ·
-
A-Release-Notes C-Editing D-Modest S-Ready-For-Implementation
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
bevyengine/bevy-website#2595 ·
-
ecosystem wording
Difficulty 1/5 Under an hour Newbie friendliness 90/100
matrix-org/matrix.org#3649 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
vadimdemedes/ink#1029 ·