ReactJS + ExpressJS with Hot Reloading and Server-side Rendering

Image for post
Image for post
React Redux Router

If you are a JavaScript expert, chances are you will love this ReactJS and ExpressJS duo. The problem is, just like any other JavaScript framework, it requires a lot of boilerplate code. Thanks to the open source community, we have got a huge amount of boilerplate codes ready for us to use when we are starting a project. This blog is about a boilerplate project that I recently updated. There is a lot of libraries bringing this project together and it is worth to write a proper explanation for all of those.

Here is the link to the code if you are impatient:

App Structure

As mentioned before, the core of this project is ReactJS and ExpressJS. Among them, React depends on a lot of libraries. These are explained in details in the later part of this blog.

For React, we use:

  1. Redux for state management

For ExpressJS, we use EJS templates.

To bring all of these together, we use Webpack.

Eslint is used to lint the javascript code.

To know about how webpack compiles and creates the distributable files, please navigate to the last section of this blog.

Directory Structure

As always, file structure depends a lot on personal preferences. I tried my best to structure it in a way that is acceptable for both ReactJS and ExpressJS community. Here it is:

Image for post
Image for post

Let’s discuss the 3 root directories first.

Client directory includes files for ReactJS (Redux, React Router v4) and static resources (images, sass etc). It has two subfolders — res and src. If you have used redux before then the structure inside the src folder should be familiar to you. res folder includes static resources and sass. Any other static files you have should also come here.

Server directory includes files for ExpressJS and EJS templates.

Webpack directory includes Webpack configurations for webpack-dev-server and production build for server and client.

Files in the root directory are typical for a npm project. We have two extra eslint configuration files.

Client Side (ReactJS)

In the client directory, we have a simple app which views a list of items and their description. The idea is to set you up with a very small amount of boilerplate code, that is the reason why I did not use a todo or a complex redux app.

Image for post
Image for post
The App

Apart from the typical redux structure, we have a const directory. It holds some important constants like default states for reducers and action types for redux actions. It also contains the list items to be shown in the app (as illustrated in the picture above).

The application simply loads the list items from a file and shows them in the app. You can navigate the items and see a preview. Inside the preview, if you click “Read More”, it shows the full text in a separate route.

Again, as simple as possible just to set you up with the react router and redux structure.

Hot reloading is enabled in this project. So you can run npm run dev and start developing with hot reload.

Server-side (ExpressJS)

Server side is pretty simple. ExpressJS uses EJS templates for server-side rendering. An Important note is that the server side code is also compiled using webpack and babel. Which means that you can use es6 modules and other stage-1 features in the server side code.

When rendering on the server, we dispatch a redux action to add an item to list items. This is to demonstrate that we can add extra items in redux state during server-side rendering. This initial state for redux is then added as a global variable in window. This global variable called INITIAL_STATE is then used as the initial state for redux store in the client side application.

Build Tools (Webpack)

Webpack as always uses couple of libraries to get things done. I will highlight the important bits here. There is three different webpack configuration file: This is used to developing the react app with hot reloading. It uses:

  • React Hot Loader for hot reloading and These two compiles server-side and client-side code for distributing in production. It uses:

  • extract-text-webpack-plugin for extracting the css code from css-loader to a css file. It creates a main.css file in the server/public/css directory.

That’s it folks! Please create an issue or pull request to improve the project. Or give it a start if you think it’s perfect!

Written by

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store