-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is this still being maintained? #92
Comments
Yes. It's a mature system that's hasn't evolved for a while as its largely feature complete. Occasionally I'll make some minor changes to reflect React's API changes, but that's about it. Sporadically someone opens a PR to make a small change or bolt on something. Is there a particular problem that you want attention on? |
I am a little concerned about the fact that the last release is about 2 years old. I was hoping to use this as part of a large app and I am not very sure about how this would be scaling and if it is a good development practice to use it. |
Also, I believe that the documentation for this project is rather lacking considering its potential use case. |
I think you might misunderstand the scale of this lib. It's just some wiring that talks to a render server and shuttles data between them. If for some reason you need to reimplement this project, it'd take you an afternoon. There are also a variety of others implementations, for example: https://github.com/mic159/react-render.
TBH, I'd hope that good development practice is to not use SSR unless you really need it. It complicates a lot of things, including your codebase and infrastructure. Most of the time you can get a comparable experience + SEO boost by simply inlining the data that you'd be fetching asynchronously from your API.
You're welcome to ask questions. |
No description provided.
The text was updated successfully, but these errors were encountered: