by badsyntax

badsyntax / react-seed

[not maintained] Seed project for React apps using ES6 & webpack.

438 Stars 86 Forks Last release: over 5 years ago (v0.0.7) MIT License 154 Commits 16 Releases

Available items

No Items, yet!

The developer of this repository has not created any items for sale yet. Need a bug fixed? Help with integration? A different license? Create a request here:

React seed Build Status

A boilerplate for building React apps with ES6 and webpack.

This is old. You should use create-react-app instead.

What you get

  • React 0.13
  • ES6, ES7 & JSX to ES5 via babel
  • webpack with react hot loader, and other useful loaders
  • Local CSS
  • Karma, mocha, chai & sinon for testing with mocking examples
  • Basic flux architecture with app actions, stores and example web API usage
  • React router (feature/react-router)
  • Material UI (feature/material-ui)

Getting started

Installing with git

git clone --depth=1 my-project

Installing with yeoman

  1. npm install -g yo
  2. npm install -g generator-react-seed
  3. Use the generator like so:
    yo react-seed

npm scripts

  • npm start
    - Build and start the app in dev mode at http://localhost:8000
  • npm test
    - Run the tests
  • npm run build
    - Run a production build


 Writing components:

// Filename: Menu.jsx

'use strict';

import styles from './_Menu.scss'; import React from 'react'; import MenuItem from './MenuItem';

let { Component, PropTypes } = React;

export default class Menu extends Component {

static defaultProps = { items: [] };

static propTypes = { items: PropTypes.array.isRequired };

render() { return (

    { => { return (); }, this)}
); } }

Writing tests:

// Filename: __tests__/Menu-test.jsx

'use strict';

import React from 'react/addons'; import { expect } from 'chai';

import Menu from '../Menu.jsx'; import MenuItem from '../MenuItem.jsx';

// Here we create a mocked MenuItem component. class MockedMenuItem extends MenuItem { render() { return (

  • {this.props.item.label}
  • ); } }

    // Here we set the mocked MenuItem component. Menu.Rewire('MenuItem', MockedMenuItem);

    describe('Menu', () => {

    let { TestUtils } = React.addons;

    let menuItems = [ { id: 1, label: 'Option 1' }, { id: 2, label: 'Option 2' } ];

    let menu = TestUtils.renderIntoDocument(

    ); let menuElem = React.findDOMNode(menu); let items = menuElem.querySelectorAll('li');

    it('Should render the menu items', () => { expect(items.length).to.equal(2); });

    it('Should render the menu item labels', () => {, (item, i) => { expect(item.textContent.trim()).to.equal(menuItems[i].label); }); })

    it('Should render the mocked menu item', () => { expect(items[0].className).to.equal('mocked-menu-item'); }); });

    Sass, CSS & webpack

    Sass and CSS files from within your JavaScript component files:
    // Filename: app.jsx
    import 'normalize.css/normalize.css';
    import styles from './scss/app.scss';
    • Note: If you're importing component Sass files from within your JavaScript component files, then each sass file will be compiled as part of a different compile process, and thus you cannot share global references. See this issue for more information.
    • Sass include paths can be adjusted in the
    • All CSS (compiled or otherwise) is run through Autoprefixer and style-loader. Any images/fonts etc referenced in the CSS will be copied to the build dir.
    • CSS files are combined in the order in which they are imported in JavaScript, thus you should always import your CSS/Sass before importing any other JavaScript files.
    • If not using local CSS, use an approach like BEM to avoid specificity issues that might exist due to unpredicatable order of CSS rules.

    HTML files

    All required

    files are compiled with lodash.template and synced into the
    // Filename: app.jsx
    import './index.html';
    • You can adjust the lodash template data in the


    • Use fat arrows for anonymous functions
    • Don't use
      . Use


    1. npm version patch
    2. git push --follow-tags
    3. npm login
    4. npm publish


    This project was initially forked from


    Copyright (c) 2015 Richard Willis

    MIT (

    We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.