Server side rendering in react and react router is a thing that greatly helps in Search Engine Optimization(SEO) and improving the overall speed of the website. In this article I am going to show you how you can perform server side rendering in react router v4 very easily. We are also going to use the react router. As of server I am going to use Express js framework of node as in this example but you may use anything you like. So lets start.
Notice the data-react attributes. That is enough to prove that component was rendered in the server.
The react component that I used is the same that is in using react router v4 blog. You may see that blog if wanna know how I made it. But it has a slight change. I have a if statement before
ReactDOM.render() function. It is so as to stop it to execute in the server as there is no DOM in the the server. To check the DOM we check if the window exists. Also I have wrapped the
BrowserRouter component down in the render as it also needs a DOM.
The main story is in the server. It is a simple express server. First I have imported all the dependencies and our component. Notice I have used ES6. It is so as we have to transpile it using babel as we have used JSX. I recommend
babel-register for it. I have linked to repository of this project down in which I have done so. Then we have a function returning simple html using ES6 template literals. Then we defined a catch all route
/* as to render all the routes using
react-router. Than we have a context variable which to to be passed to
StaticRouter is a component introduced in react-router v4 which requires no DOM. It need the location which we are passing using
request.url.The context is used to deal with any redirects . As we don't have any redirects I have skipped that portion. Then we are using
renderToString function of react-dom server to render our component to a string. In this we are passing our component wrapped in
StaticRouter. Then we are passing this to our templating function with our component rendered into string. Then we are responding with this data. Lastly we are starting our server at port 3000.