This allows users to avoid CORS in simple projects that are hosted on the same server as backend.

Fixes #186

Ref: https://twitter.com/sprjrx/status/760481328886272004

Fixes #322

The problem has since been fixed upstream.

This reverts commit f7011e04.

This fixes #302 by temporarily forking `detect-port`.
Hopefully this fix will be merged into the original project, and we can refer to it again.

* Use /static paths for assets

* Fix e2e test

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

* Display JS and CSS bundle sizes after build

* Print gzipped filesize, address nits

* Use filesize for human readable output.

Also fixes #194

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

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

* Provide instructions on GH Pages deploy

* Add docs for GH Pages deployment

* Prevent incorrect paths in file-loader

* Minor message tweaks

* Update README.md

* Fix relative paths

* Don't assume the project is hosted at the root
* Require package.json in webpack.config.prod.js and use homepage if set; otherwise use '/'

* Fix package.json path and add sample package.json for tests

* Update publicPath to use relative path portion of URL defined in homepage

* Update successful bundle generation message

* Show bundle generation success message based on presence of homepage in package.json

* explicitly specify ESLint config path for editor plugins

* changed to use single quote

* Adds .gitignore file to default template

* Simplify renames

* Reference npm issue in comment

* Removing leading slash

* Recursively copy the template folder

* add fs-extra library

Related to #72, c2ba7a4a

* dogfood eslint config

* moved linting to e2e