* Install React Bootstrap Dependency - section added

* Updated with short intro clarification

* Moved React Bootstrap after Add Images

Adds the [`dev-toolkit` npm package](https://github.com/stoikerty/dev-toolkit) to the list of Alternatives.

After some suggestions in my last PR https://github.com/facebookincubator/create-react-app/pull/292, I've changed my project to provide better command-line utilities for initializing an app. Managed to get rid of babel's dev-dependencies as well, so this is now a dependency-free project just like `create-react-app`.

* Accept version when loading fonts e.g. font-awesome

* Add query string support to mp4/webm

Add missing word "see"

* Add note that router doesn't work with gh-pages

* Update note about using router with gh-pages

* Use /static paths for assets

* Fix e2e test

* Symlink-friendly path resolution

I was having difficulties using a local copy of `react-scripts` and `npm link`ing it into a real world project. This change resolves paths relative to the current working directory (that is, most likely the directory of the app) rather than assuming a certain directory structure.

* Fix relative paths in post-eject case

because I'm an idiot

* Renamed resolveLib to resolveOwn

I think this should solve #258

* Update CHANGELOG.md

* Update the changelog

* Update CHANGELOG.md

This is the one people are converging on, and flow-vars may get deprecated.

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.