* Added the alias for profiling and output change to keep the classNames and functionNames for human readbility
* defined isEnvProductionProfile with other isEnv checks
* moved the keep_classnames and keep_fnames to terserOptions scope
* resolve merge conflict for yarn.lock.cache
* revert yarn.lock.cache to master yarn.lock.cache
- git checkout origin/master -- packages/create-react-app/yarn.lock.cached
* Comment and Boolean Check
- I clarified the comment and specified the use case
- Changed the environment check to check for the specific true rather than
the assumed primitive value as before.
* Replaced env with flag
- Per suggestion --profile flag used instead of env variable PROFILE_APP
* documentation in available scripts section with suggested information
* resolved a local git issue. Fixed documentation error.
* moved documentation to suggested file
- Added a brief summary of profiling in available scripts section.
The summary references the production-build document. Which is the
file I moved the new documentation into under a new Header for production support.
* Update production-build.md
Co-authored-by: Ian Sutherland <ian@iansutherland.ca>
This closes#7359 by making IMAGE_INLINE_SIZE_LIMIT=0 actually disable image inlining.
We use url-loader's `limit` option to set the line at which images will be inlined, and we basically expose this option to our end users via the IMAGE_INLINE_SIZE_LIMIT environment variable. Most people using it want to disable inlining images all together (the major motivator for adding it at all was I think for strict CSP), and our documentation said setting the value to zero would do that. However, it did the opposite: url-loader treated zero as "no limit".
The update to 2.x fixes this; zero means nothing gets inlined. The other changes from the version bump shouldn't affect us:
- minimum node version is 8.9.x, we already require 8.10.x
- the limit was "greater than", is now "greater than or equal to"
