Open
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.
Metadata
Metadata
Assignees
Labels
No labels