Skip to content
A React starter. Router, Webpack, Sagas, and more.
JavaScript Other
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.


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

What is this?

A React starter project based on React 16, React Router v4, Webpack 4, Redux, and Redux-Saga.


git clone project-name
cd project-name
rm -rf .git/
git init


Below you'll find a list of most packages included with a brief description what they do and why they're useful. I'm skipping some of the more obvious packages like React and Babel.



I like CSS modules over CSS-in-JS. This is a great little package that lets you combine class names:

const buttonClasses = classNames(css.button, css[`button_${type}`], { 
  css.button_active: isActive, 


The descendant of react-router-redux for React Router v4. It allows you to connect your router to your redux store and dispatch history methods (push, replace, etc).


PostCSS plugin to minify CSS.


The date and time package for JS. If you're familiar with Python, this is akin to arrow.


PostCSS plugin to handle @import directives in CSS files. Useful for importing Google Fonts from your CSS files. I also like to have a constants.scss file that I @import from other CSS, keeps everything nice and tidy and prevents code duplication.


PostCSS plugin that transforms your modern CSS into backwards compatible CSS. The level of compatibility is determined by the browserslist you define in your package.json.


Awesome package to manage <head> across your application. The title template feature is particularly useful. Also, it's amazing that how appropriately the package is named given that it's made by the NFL!


Can't overstate how amazing this package is. Code splitting used to be particularly painful, but this package makes it incredibly simple. A good understanding of the splitChunks optimization of webpack will also go a long way to making smaller bundles.

const LoadableComponent = Loadable({
  loader: () => import('./my-component'),
  loading: Loading,


Ever wanted to inspect your store at runtime? This is what you've been waiting for. Also includes a nice timeline of actions and the state difference after each action.


A beautiful alternative to redux-thunk. While it may feel like a lot of boilerplate early on, I use sagas on all actions that fetch from APIs. There's tons of advanced features like task forking and cancelling as well. From their readme, look how intuitive and easy to read the following is:

function* fetchPosts() {
  yield put(actions.requestPosts())
  const products = yield call(fetchApi, '/products')
  yield put(actions.receivePosts(products))


Opinionated CSS reset. Also consider normalize.css as an alternative.


A polyfill for window.fetch. A small library to include to support IE11.



This will add a displayName to all your React components. Yes, it will increase your bundle size, but it will make reading your Sentry errors a lot easier.


Sure, you could import the lodash methods you want manually to minimize your bundle size:

import pick from 'lodash/pick'

Or you could use this plugin that will cherry-pick all your imports.


Snapshot tests are pretty useful for testing UI components. It can be easy to overuse them, and they can be a bit annoying when you're changing defaultProps of components, but overall I think they have their place and can be useful.


You're splitting your bundle into a vendor.js, main.js, and runtime.js. This plugin lets you inline any chunks into your HTML, which is especially useful for runtime.js since it's particularly small and you can save a round-trip request.


Surprisingly simple but useful plugin for snapshot testing. Instead of creating a blank mock for all your styles, you can use this plugin which will return the object you're using from your styles as-is. For example:

<div className={css.wrapper} />

Would normally have an empty className in your snapshots. With this plugin, however:

exports[`test matches snapshot 1`] = `


If you haven't yet checked out Sass, it's a really great addition to CSS. Comments? Check. Nested Rules? Check. Variables? Check.

"But, but, CSS variables exist now." Yes, but they have no IE support at all. With PostCSS and sass-loader your variables will be substituted at build time, so you don't have to worry about browser compatibility.

You'll also have access to a ton of useful functions like transparentize and lighten. For example:

$primary-button-background-color: #17BEBB;
$primary-button-background-color-disabled: transparentize($primary-button-background-color, 0.5);

Ever wanted functions in CSS?



$button-width: 200px;
$button-width-large: $button-width * 2;

There's tooons of features.


This module really helps you understand the makeup of your bundle and what's taking up so much space. It will help you optimize your bundle and give you an idea of what you should be splitting up with react-loadable and Webpack's splitChunks.

You can’t perform that action at this time.