kapost / weeds

weeds

The Kapost React/Redux boilerplate

What is this?

It's a universal React/Redux boilerplate to share some of the the client code we use at Kapost. You can check our blog for different articles explaining some patterns and tools within the suite. If you are curious what major tools we use, please see

It isn't a great way to learn how to use React or Redux. It might be helpful when you are trying to setup your own server-rendered app though.

Similar Projects

• React Redux Universal Hot Example
• Universal React + Redux Boilerplate

A huge thank you to the maintainers of these projects for being a huge inspiration.

Recommended Reading

Below is a recommended list of resources to get familiar with the tools and base project inspiration.

1. React tutorial (if you aren't already familiar)
2. Dan Abramov's video introduction to redux (should take ~30min)
3. The redux docs (Many helpful guides on testing, server rendering, middleware, etc.. This project was heavily inspired on these guides.)
4. The react-router guides
5. Async redux actions — why you might want to use redux-thunk
6. Dan Abramov's videos on using these tools in React Applications
7. ES6 Promises
8. Organizing React apps by pods

Also, the internal documentation.

1. Pods
2. Testing
3. Using API utils

If there is any confusion or missing documentation please contribute or let us know!

Setup

You will want a version of node and npm that matches the package.json. If you have node installed already, installing n will help to manage node versions.

npm install -g n

You should setup a way for .env to be sourced on changed directory. direnv is an nice and safe cross-shell solution. On OSX, you can install with homebrew (brew install direnv).

Once the correct version of node and you have the enviroment loaded, install dependencies with:

npm install

To run the client app alongside an example server, run these commands in separate terminals:

npm run api:start
npm run development # or one of the other commands below.

and then you can navigate to lvh.me:5000.

Optionally, you can setup eslint and scss_lint in your editor of choice. Atom has the linter-eslint and linter-scss-lint packages which work great with the root configuration files (.eslintrc and .scss-lint.yml).

Development

You can run the app with any of the following commands:

npm run development                       # run with server and webpack watching
npm run development:hot                   # run with server and webpack hot loading (updates JS without refresh)
npm run development:no-server-rendering   # same as `npm run development` but without server rendering. Useful for debugging.
npm run production                        # run app with same build configuration as production environments (heroku)

You should be able to navigate to <subdomain>.localhost/canvas with any of the above commands.

Unit Tests

The unit test suite can be run through the following commands:

npm run test                    # Run all tests in suite
npm run test:debug              # Run all tests in suite with node debugger
npm run test -- -g "<App />"    # Run all tests by block (string match of `describe` or `it` blocks)

Deployments

Deployments require Ruby 2.3.0 and the environment variable HEROKU_DEPLOY_API_TOKEN to be set (add the result of heroku auth:token to .env.local)

To promote from demo to production, use:

rake promote

Test Coverage

Istanbul is used to calculate the code coverage of the repo. The total percentage is reported to CodeClimate on master builds in CircleCI. To see what code coverage is locally, run the following command:

npm run test:coverage

Major Tools

JS apps can be particularly intimidating to get started with. It's hard to know what major dependencies are just looking at a package.json, (many dependencies are minor extensions to these major tools). Below are the list of the tools at the foundation of the app.

App tools

Build tools

Test tools

See the testing documentation for testing tools.