Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

React Express Boilerplate

React Express Boilerplate with React, Node (Node 8.11.3)

React Node Jest

  • This repo holds the entire front end code base for React Express Boilerplate.The code is written in React 16, with node express server to act as a proxy layer between back-end and front-end.
  • We are using passport for google authentication
  • We are using ant design for styling our page
  • This repo was bootstrapped with CRA(CREATE-REACT-APP) and has been ejected.
  • For styling we are using normal css with flex box
  • Test cases are written in Jest and snapshot tests in Enzyme

πŸŒ† Snapshots of the app

πŸ“¦ Table of Contents

  1. Requirements
  2. Installation
  3. Running the Project
  4. Project Structure
  5. Routing
  6. Development Tools
  7. Building for Production

πŸ’Ό Requirements

  • node ^8.11.3
  • yarn ^1.7.0 or npm ^3.10.10

πŸ’Ύ Installation

After confirming that your environment meets the above requirements, you can start this project by following the steps mentioned below:-

$ git clone
$ cd react-express-boilerplate

When that's done, install the project dependencies. It is recommended that you use Yarn for deterministic dependency management, but npm install will suffice.

$ yarn install # Install project dependencies (or `npm install`)

▢️ Running the Project

After completing the installation step, you're ready to start the project! When you are running this project for the first time, you need to follow these steps:-

Since the project relies on a lot of environment variables, one needs to create a copy of the properties_sample.env file inside config folder and save as properties.env

# For development environment

$ cp env/properties.sample.env env/properties.env # Make a properties.env file from properties.sample.env

Make changes in it according to the environment variables you need, we use dotenv which will read all environment variables from properties.env and set them on process.env

For generating google oauth client id and client secret

Step 1: Go to the developer console:

Step 2: Look up β€˜oauth credentials’ in the search bar, and click the single option that pops up.

Step 3: Try to find the β€˜Create credentials’ button. If you find it, go ahead and click on it. Choose β€˜Oauth Client Id’ (figure 1).

For application type, choose web application. Authorized origins and redirect URLs are a bit confusing, so I’ve just copy pasted a bunch of different options (figure 2) that have worked for me in the past. For production settings, you’ll probably want to be a bit more specific.

Step 4: Click save, and copy down the Client Id and Client Secret values that are hiding somewhere on the same page.

Step 5:

  • Replace your DASHBOARD_APP_GOOGLE_CLIENT_ID with your own gmail client id in your properties.env file
  • Replace your GOOGLE_CLIENT_SECRET with your own gmail client secret in your properties.env file

For react and express project execution

# For development environment

$ yarn dev:build-client # Build the client bundles (or `npm run dev:build-client`)
$ yarn dev:server # Runs the nodemon server to start express server (or `npm run dev:server`)
$ yarn dev # Run the client build and server in watch mode and start the nodemon server(all in parallel) (or `npm run dev`)
# For development environment

$ yarn start # In production we would just run this command to start our node or pm2 servert

While developing, you will probably rely mostly on `yarn start`; however, there are additional scripts at your disposal:

|`yarn <script>`                                |Description|
|`yarn start`                                   |Starts node app at `localhost:8000` by default|
|`yarn dev`                                     |Starts client build and nodemon server in parallel|
|`yarn dev:build-client`                        |Runs webpack in watch mode and serves react app at `localhost:3000`|
|`yarn dev:server`                              |Runs nodemon server at localhost:3000 for express app|
|`yarn build`                                   |Builds the app in production mode and serves files from build folder|
|`yarn lint-staged`                             |Runs prettier and eslint fixes|
|`yarn build:staging`                           |Builds the app in staging mode and serves files from build folder|
|`yarn eslint:fix`                              |Runs all eslint fixes|

✏️ Project Structure

The project structure using CRA directory structure where folders are grouped into containers and components and since we are using redux, we do have actions, reducers, selectors, hocs, store and helpers. This structure is only meant to serve as a guide, it is by no means prescriptive. That said, it aims to represent generally accepted guidelines and patterns for building scalable applications. To understand what goes inside components and what inside containers, please check out this component-state-vs-redux-store by Vivek Nayyar.

β”œβ”€β”€ build                                           # All production ready files with minified JS, html and css files
β”œβ”€β”€ client                                          # All react related code will go here
β”‚   β”œβ”€β”€ config                                      # All CRA related config goes here including paths, environment variables and β”‚jest config goes here
β”‚   β”œβ”€β”€ public                                      # Static public assets used while in dev mode
β”‚   β”œβ”€β”€ scripts                                     # All webpack related code
β”‚   β”‚   β”œβ”€β”€ build.js                                # Script for making production bundle
β”‚   β”‚   β”œβ”€β”€ start.js                                # Script for development mode
β”‚   β”‚   β”œβ”€β”€ test.js                                 # Script for test mode
β”‚   β”œβ”€β”€ src                                         # Client Application source code
β”‚   β”‚   β”œβ”€β”€ helpers                                 # All api helpers, utils, local storage, analytics and config helpers go inside this folder
β”‚   β”‚   β”œβ”€β”€ components                              # Global Reusable Components
β”‚   β”‚   β”‚   β”œβ”€β”€ ComponentName                       # Component Name Folder and every component will have a index.js and css file
β”‚   β”‚   β”‚   β”‚   β”œβ”€β”€ index.js                        # Main file which exports the component
β”‚   β”‚   β”‚   β”‚	β”œβ”€β”€ ComponentName.js                # Main component code
β”‚   β”‚   β”‚   β”‚	β”œβ”€β”€ ComponentName.css               # Styling for the component
β”‚   β”‚   β”œβ”€β”€ pages                                   # Global Reusable Components
β”‚   β”‚   β”‚   β”œβ”€β”€ PageName                            # Component Name Folder and every component will have a index.js and css file
β”‚   β”‚   β”‚   β”‚   β”œβ”€β”€ index.js                        # Main file which exports the component
β”‚   β”‚   β”‚   β”‚	β”œβ”€β”€ PageName.js                     # Main component code
β”‚   β”‚   β”‚   β”‚	β”œβ”€β”€ PageName.css                    # Styling for the component
β”‚   β”‚   β”œβ”€β”€ assets                                  # Any images, fonts and icons which need to be cache bursted go here
β”‚   β”‚   β”œβ”€β”€ index.js                                # Application bootstrap and rendering
β”‚   β”‚   β”œβ”€β”€ constants                               # Folder for constants file
β”‚   β”‚   β”œβ”€β”€ Routes.js                               # All application client side routes using react-router
β”œβ”€β”€ env                                             # All environment variables to be configured from here
β”‚   β”œβ”€β”€ properties.sample.env                       # Sample file for setting up environment vars
β”œβ”€β”€ server                                          # Express application that provides webpack middleware
β”‚   β”œβ”€β”€ controllers                                 # All route controlling logic will go here for example authentication controller
β”‚   β”œβ”€β”€ middleware                                  # Middleware for checking JWT token in every api call 
β”‚   β”œβ”€β”€ models                                      # Schema for mongo db documents
β”‚   β”œβ”€β”€ router                                      # Main express route handlers
β”‚   β”‚   β”œβ”€β”€ BaseRouter.js                           # Base routes which the other routers extend
β”‚   β”‚   β”œβ”€β”€ Router.js                               # Express router for server side rendering the react app
β”‚   β”‚   β”œβ”€β”€ ApiRouter.js                            # API router for all back end api calls
β”‚   β”œβ”€β”€ constants.js                                # All server needed constants can be found here
β”‚   β”œβ”€β”€ index.js                                    # Entry point for the node js server
β”œβ”€β”€ webpack                                         # All front end and back end webpack config will go here
β”‚   β”œβ”€β”€                       # webpack file for dev environment
β”‚   β”œβ”€β”€                      # webpack file for prod environment
β”‚   β”œβ”€β”€              # webpack dev server for dev work
β”œβ”€β”€ .babelrc                                        # Babel file for es6 and react code transpilation
β”œβ”€β”€ .gitignore                                      # The name says it all
β”œβ”€β”€ .eslintrc.js                                    # This file maintains all end points of the back end routes
β”œβ”€β”€ .prettierrc                                     # Prettier config
β”œβ”€β”€ package.json                                    # All npm dependencies can be found here
β”œβ”€β”€                                       # Readme file for the whole app
β”œβ”€β”€ yarn.lock                                       # Yarn lock file for locking the dependency versions

πŸš€ Routing

We use react-router route definitions See the project structure section for more information.

βš™οΈ Development Tools


  • We use prettier for code formatting.Here is the link to downlod the same.Prettier

  • Make sure you are using vscode and your vscode user_settings has the following code:-

    "editor.fontSize": 12,
    "editor.formatOnPaste": true,
    "editor.formatOnSave": true,
    "prettier.eslintIntegration": true,

🚚 Building for Production


  • Deployment will always happen from the release branch on production.
  • Any production related environment variables need to be configured on env/properties.env.Take a copy of sample and edit values for prod environment
  • ci folder has a docker script to deploy all the code in a docker instance
  • yarn build will built the production build
  • yarn start will start the node server or pm2 server( which ever we chose to go with)


React, express boilerplate with eslint and prettier setup







No releases published


No packages published