React Boilerplate with testing is a starter kit for React 0.13 apps written in ES6. Its README lists the parts: Babel 5 for ES6, webpack 1 and its dev server for bundling, React Hot Loader “for tweaking React components in real time”, and Karma for unit tests. The webpack config explains each of its options in comments. The app itself is one component that renders “Hello, World!”.
All three commits are from September 19, 2015, and the repository hasn’t changed since.
What’s in it
npm startrunsserver.js, a webpack-dev-server with hot module replacement on port 5000. Edit a component while it runs and React Hot Loader swaps it into the page without a reload. That still works today.npm testruns Karma once in PhantomJS, with Jasmine, karma-webpack to bundle the specs through Babel, istanbul-instrumenter-loader for coverage, and a spec reporter.npm run test_watchkeeps Karma running and reruns the specs on every change. There’s an empty test that always passes, plus three that render the app and check its text and one of its methods.npm run lintruns ESLint 0.21 with babel-eslint and eslint-plugin-react rules.npm run builduses a separate production config with UglifyJS andNODE_ENVset to production. Its Babel loader points at ascriptsfolder instead ofsrc, so the build stops at the first line of JSX.

src goes through React Hot Loader and Babel.react.chat.v2
Eleven minutes after the last commit here, react.chat.v2 started from these same files: its first commit matches this repository file for file. Its README only says “React Chat V2”, and its package.json describes it as “FireBase react-chat-v2”, though it never got any Firebase code. In October 2015 it added react-router 1.0’s release candidate, a Sass loader, Home and About routes, and a sidebar of rooms with a filter box, and it stopped there. Its name points to React Chat, which had started two months earlier.
Running it today
With Node 6, npm install --ignore-scripts installs everything but skips PhantomJS’s binary download. Karma then runs in headless Chromium instead, through a small config that wraps karma.config.js and swaps the PhantomJS launcher for karma-chrome-launcher, and all four specs pass. The dev server still starts, and hot reloading works as the README describes.
The creation date shown here is the GitHub repository’s UTC creation date. The terminal capture shows a real run of the test suite today, and the code card shows the project’s own source.