Yet Another React Starter Kit.
Everyone has one, here’s mine.
- React, of course.
- Webpack for asset bundling.
- Hot reloading enabled out of the box. Changes to React components will show in the browser immediately without a full reload thanks to react-transform-hmr.
- Babel for ES6+ transpilation.
- SASS (SCSS or Sass style), Less, and Autoprefixer enabled by default through Webpack.
- Image loaders setup and ready to go so you can reference your images as
require()statements in JS, or just use
url()as usual in CSS and Webpack will take care of the rest. See the Header component and the Application component stylesheet for examples of each.
- Karma + Mocha + Enyzme for testing. Istanbul and isparta are also activated with
karma-coveragefor code coverage analysis, even on your ES6 classes. See Testing below for more info.
- Production configuration with best practices applied for optimizing React file size. The bundled JS file produced from this example is right at 40KB minified and gzipped. See Building below for more info.
- Built-in command for publishing your app to GitHub pages. See Building below for more info.
- Optional support for ESLint via babel-eslint.
This kit is intentionally missing a specific Flux implementation, or any other non-essential library, as I use this as a base for experimenting with various parts of the React ecosystem.
In the wild
Fork this repo, then run:
npm install npm start
That will fire up a webpack dev server in hot mode. Most changes will be reflected in the browser automatically without a browser reload. You can view the app in the browser at
To generate a production build, run:
npm run build
The above command will generate a
dist folder with the appropriate index.html file along with the minified CSS and JS files.
You can also automatically publish to GitHub pages. Just run this instead of the regular build command:
npm run build:gh
You can then view your app at
http://[yourgithubusername].github.io/[reponame]. For example, you can load this demo at http://bradleyboy.github.io/yarsk.
Modifying the HTML
The HTML file is generated using the
conf/tmpl.html file. This file is used for both the development and production build.
The tests use Karma, Mocha and Chai through PhantomJS. See the example test in
app/components/Application/__tests__/index.js. The test suite can be run like so:
To run the tests in watch mode (tests will re-run each time a file changes), use this instead:
npm run test:watch
You can generate code coverage reports with:
npm run test:coverage
coverage directory once that command is completed.
Finally, the repo is Travis ready. The
.travis.yml file should work out of the box, just add your repo in Travis.
.eslintrc. I’ve included my own defaults, feel free to modify them to your own taste. For more information on configuring ESLint, consult its documentation. Linting is run before each webpack build when a
.eslintrc file is present.
.editorconfig.example to match your own preferences, then renamed the file to
.editorconfig and use an IDE or editor that supports EditorConfig.