Browser launch can still be suppressed using BROWSER=none

* Adds note on how to resolve file or directory not found errors for heroku deployments

* Style tweaks

* Add "Changing the Page Title" to User Guide

* Add link to main README

 - create-react-app@1.0.2
 - react-dev-utils@0.4.2
 - react-scripts@0.8.4

* Proxy rewrites Origin header to match the target server URL

* Added comments on rewriting Origin header by the proxy middleware

 - create-react-app@1.0.1
 - react-scripts@0.8.3

* Add syntax highlighting configuration guide.

* Update link.

 - babel-preset-react-app@2.0.1
 - eslint-config-react-app@0.5.0
 - react-dev-utils@0.4.1
 - react-scripts@0.8.2

* Let Jest handle all file types

* Update regexes

* Fix exclusion regex to also exclude files without extension
* Be over-cautious with Windows paths because I'm not sure how Jest handles them

* There is no automatic babel-jest discovery now that we use transsform

* Add Subresource Integrity support

* Pin dependency

* Remove path module from webpack config on eject.

Fixes #1174

* Move path module inclusion right after the other imports

Re: #1174

* Add deploy to Firebase CDN on template's README (Closes #374)

* Move section and minor tweaks

* Document what npm build does and pushState

* Fix typos, add express example

* Tweaks

* Update README.md

* Add "npm run build silently fails" to Troubleshooting

* Update README.md

In my tests, jsdom was throwing a "SecurityError" at HistoryImpl._sharedPushAndReplaceState (node_modules/react-scripts/node_modules/jsdom/lib/jsdom/living/window/History-impl.js:87:15)

This happens because document.URL defaults to "about:blank". Unfortunately, if you interact with the History object it tries and fails to parse the URL, causing a "SecurityError" to be thrown. Setting the default URL to "http://localhost" fixes this issue.

 - react-scripts@0.8.1

Jest matches moduleNameMapper regexes with module names, not the full
file path, so the negative lookahead doesn’t work for filtering out
JS files, because they can be imported without the extension. So paths
like `lodash.assign` and `../utils/range` were mislabeled as resources
with unknown file extensions because they have a dot in the name.

As a stopgap measure, revert the moduleNameMapper regex added in #1077.

 - babel-preset-react-app@2.0.0
 - create-react-app@0.7.0
 - eslint-config-react-app@0.4.0
 - react-dev-utils@0.4.0
 - react-scripts@0.8.0

* Added functionality to crash the build during CI whenever linter warnings are encountered.

* Updated the docs with a description on how to use the build in CI

* Fixed small typo

* Fixed description of build error.