• Motivation
• Goals
• Features
• Installation
• Usage
• Tricks
  • Client side version (opt-in)
  • Component scaffolding using plop
  • 📕 Storybook support
  • Keep your project up to date
  • Avoid source map generation for faster builds
  • Change the port of the dev environment
  • Import SVGs as ReactComponent
• Caveats
• Todo
• Changelog

This is just another React Starter Project as there are literally hundreds of others out there. The reason I created this one was to have one central repo I can base my own future projects on, which contains most of the packages I usually use, is easily extendable, easy to understand, supports server side rendering, and uses all the configs and settings I made good experiences with in the past.

Another reason I created my own starter project was because I was setting up two new long term projects and I wanted to be able to use Webpack 4 and Babel 7 long before it was stable. None of the bigger and well known starter projects were supporting both by the time I created this starter project. So the idea was born to create my very own. And here we are 🎉

A few things might be familiar when you've worked with other starter projects before. I borrowed many ideas (and will continue to do so) from Create React App, React Starter Kit and other great starter projects because my intention was to create an up-to-date starter project for myself based on best practices and not to completely reinvent the wheel in every possible way just for the sake of it.

My goal is to provide a well-tested, regularly maintained, easily configurable and adjustable React Starter Project with support for server side rendering that gives you a good basis to start your own project on. As minimal as possible with as much functionality as necessary.

I use this Starter Project in several real-word projects so it is battle-tested and everytime I fix a bug or add a feature I find useful I will also update this Starter Project. I will also keep the dependencies up-to-date on a regular basis and will also stay updated with all the latest and greatest best practices in the React world and integrate them if possible and useful!

If you have any questions you can always open an issue on Github or reach out to me on Twitter!

This project has out-of-the-box support for the following things:

• General Setup
  • 🔥 Babel 7
  • 🔥 Webpack 4
  • 🔥 ESLint 5 (with a set of custom rules which may be mostly identical to AirBnB with some personal flavor added)
  • 🔥 Flow Type
  • 🔥 Prettier
  • 🔥 Jest 24
  • ✅ Server side prerendering with Express
  • ✅ Hot Module Reloading (HMR)
  • ✅ CSS Modules
  • ✅ PostCSS
  • ✅ Precommit hooks via lint-staged + Husky
  • ✅ Optional static deployment without the need for Node.js on the server
  • 📕 Support for Storybook (>= 4.0.0)

• Libs and Dependencies
  • ⚛ React 16.x (latest), with Hooks!
  • ✅ Redux + Thunk middleware
  • ✅ Immer
  • ✅ Reselect
  • ✅ React Router 4
  • ✅ React i18next for multi language support
  • ✅ React Helmet

Since it's only using standard APIs so far it is ready to be used with the new React Suspense feature coming in React 17!

As a general recommendation you should create a fork of this project first so you can adjust it to your own needs, add all the dependencies you need and commit everything back into your repository.

Once you've forked the repository here on Github, clone it, cd into the directory and run yarn (or npm install) on your command line to install all the dependencies. You're ready to go now!

There are npm scripts for all the relevant things. The server will always be started on port 8500 unless otherwise specified in process.env.PORT. You can use a .env file to specify env vars. If you want to use them in your client side code, don't forget to add them in config/env.js.

Noteworthy npm scripts:

Starts the app in development mode: creates a new client and server dev build using webpack, starts the Express server build (for both file serving and server side pre-rendering) and keeps webpack open in watchmode. Updates the app (if possible) on change using HMR.

Creates a new build, optimized for production. Does not start a dev server or anything else.

Run all tests using jest.

Update all Jest snapshots (if there are any)

Run plop to create new React components or Redux reducers via CLI

There are a few environment variables you can set to adjust the setup to your needs

Beginning with v1.3.0, a static index.html is also generated and written to your clientBuild directory. You are now able to deploy the build/client directory to a static webhost (such as Netlify or AWS S3) and serve your application from there!

For the generation of the index.html the server side build gets started right after building, a headless Chrome then visits the site and writes the content of the server side response to your client directory. So you still need the src/server directory and the server side build but you're now flexible and can decide on your own whether you want to have the full server side experience or only deploy your completely static app somewhere.

Along with this starter kit comes plop - a great command line tool to keep the structure of your Redux components and Redux reducers consistent. Run yarn plop (or npm run plop) to have components and Redux reducers created for you automatically! Just enter a name, answer a few questions and you're ready to go! You can of course adjust everything to your needs. All Plop templates can be found in the config/plop directory.

I've successfully tested Storybook and it integrates seamlessly and without any issues into this setup. If you want to add Storybook to your project, install Storybook ^4.0.0 and run getstorybook to have the basic setup created for you. You must then replace all the content in .storybook/webpack.config.js with the following line:

module.exports = require('../config/webpack.config.js/storybook');

Afterwards you should be able to run yarn storybook to start the Storybook Dev Server.

If you want your project to stay up to date with recent changes to this project, you can add React SSR Starter as remote to your local git repo. Use the following line:

git remote add upstream git@github.com:manuelbieh/react-ssr-setup.git

More on that can be found on Github: Syncing a fork.

In some cases you might not want to generate source maps for the generated files. In this case you can set the OMIT_SOURCEMAP environment variable to true. No source map files will be generated then. This works no matter if you're in devmode or building for production.

By default if you run yarn start the development server will use port 8500. You can change this by specifying a PORT environment variable.

You can import SVG files as React components exactly the way you can do it in Create React App 2.0:

import { ReactComponent as Logo } from './Logo.svg';

Then you can use it in JSX like <div><Logo /></div>.

Here is a video that explains that a bit more.

• [1] MiniCSSExtractPlugin doesn't play nicely with consecutive builds in Webpack's watchmode yet (Github issue here). So I'm using ExtractTextWebpackPlugin until this is fixed Fixed! 490e6e9
• [2] Hot Module Replacement is still a bit buggy. Not all components have been configured and updated to play nicely with HMR (namely Redux and React-Router) Seems to be fixed (still validating) 66875a1
• Running the build in production: I strongly recommend to serve your static assets using Nginx or Apache instead of the Express.static middleware. That's how I usually do it and that's why you won't see any assets when starting the production server build with Node. If you still want to use Express.static in production despite the warning, have a look at the first few lines of ./src/server/index.js. There's a short comment with a description what you need to do.

• Replace ExtractTextWebpackPlugin with MiniCSSExtractPlugin once it's working properly
• Get HMR working (done, mostly)
• Add HMR for Redux
• Add HMR for CSS Modules (depends a bit on MiniCSSExtractPlugin) (using ExtractTextWebpackPlugin)
• Add React Error Overlay from Create-React-App
• Add react-loadable or react-universal-component (or both, still investigating what makes most sense). Update: react-loadable is out due to questionable license change Just use React.lazy which was introduced in React 16.6.
• Improve server side template
• Add (and use) react-helmet
• Add/improve server side chunk loading
• Add test setup using Jest
• Add optimize-css-assets-webpack-plugin and postcss-safe-parser similar to how CRA 2 is doing it
• Modify svg-loader babel-loader so SVGs can be imported as React component (see CRA 2)
• Add proper offline support using Workbox
• Fine tuning different minor things (ongoing task)

Moved to its own file: CHANGELOG.md

MIT.