This enables us to ship them now, and find a way to resolve runtime path without webpack later.
See https://github.com/facebookincubator/create-react-app/issues/255

https://docs.npmjs.com/files/package.json#files

Fixes #260

This seems to work best, both on Windows, OS X, and Linux

Add aik as possible alternative for create-react-app

* Display JS and CSS bundle sizes after build

* Print gzipped filesize, address nits

* Use filesize for human readable output.

* Improve error handling in E2E script

* Expose e2e.sh as npm test script

* Enable generators

* Opt out of using helpers

Also fixes #194

Some libraries rely on it, and they work fine with browserify.
Let’s just do the right thing here by default.

These work regardless of whether you already have a gh-pages branch.

It has a sane default port, gzip, and doesn’t aggressively cache index.html.
Perfect.

It has gzip built-in so the size numbers are closer to real world. Thanks @ForbesLindesay for the tip!
Related to #228

* Use keyword `warn` in eslint config

We can use the keyword `warn` for rule configuration instead of a number.

* Fix comment which where WARNING was replaced

* Remove extra apostrophe

This is frustrating with shells like `fish` that track directory moves

It helps to maintain consistency with React docs

allow 2 * x + 1

This way the one generated by `init.js` doesn’t get overwritten later.
This fixes #149 which got broken as part of #94

update webpack css include path, allow files to be loaded from the project root node_modules folder. (#178)

This project is a really good use case to apply some accessibility
rules to the lint config. For beginners getting started with React, we
can also teach/enforce basic accessibility rules in the web at author
time.

For now, I’ve just applied to the rules that are listed in
`eslint-config-airbnb` because these are most real-world tested, and we
can continue to add.

Happy to help if there are any questions/issues/concerns about the
plugin!