-
Notifications
You must be signed in to change notification settings - Fork 126
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
[FEATURE] webpack.config.js for server-side rendering #36
Comments
Hi Tizian, Thanks for the question. I have planned to integrate server-side rendering for a long time. Unfortunately, I don't have time to do it very soon. Relay doesn't support server-side rendering out of the box. You might need to take a look at isomorphic-relay-router. A PR would be also very welcomed |
The Relay 2 (release date supposedly soon but not yet confirmed) approach to SSR might be of interest here: "Our overall approach with the new core has been to build simple primitives that can be built upon in user space. So for example, there is a clear separation of the React integration layer and the core - the former being implemented entirely via the public API of the latter. It might take a few releases to refine and document this, but i expect that it will be easy for the community to build upon this to make a server rendering module for Relay." source: facebook/relay#1369 |
Hello!
First of all, I'd like to thank you for this awesome work! This really got us kickstarted quite well and we'll be able to work with this as a solid base for our React projects! It's awesome!
Still, I found one major concern with the current state of the project and it's mainly SEO.
So, with webpack it is possible to render the HTML staticaly (https://github.com/webpack/react-webpack-server-side-example) but I haven't figured out how to configure my relay-fullstack instance to do that, at all.
Here's my webpack.config.js, maybe you can tell me what is wrong or maybe suggest a way to do it properly?
Regards
Tizian
webpack.config.js:
'use strict';
The text was updated successfully, but these errors were encountered: