* adding a note on how to resolve "Could not find a required file." deployment errors because of deleted or ignored files
* Tweak
* Unrelated style nits
Use the configured appBuild value in paths.js instead of hard-coding it to 'build'. This is helpful for the ejected case where the appBuild path is changed to another folder name.
* Enable eslint caching in development
POC for https://github.com/facebookincubator/create-react-app/issues/740. Haven't found any problem, build times improved about 1s on my project and machine.
* Bump eslint-loader to 1.6.3
* move @remove-on-eject block to persist cache config on eject
* Added a how-to on react-snapshot
Added a section with a short description and link to a tutorial on generating static html pages with react-snapshot, and also linked to it from the section on managing the page title.
* Updated link title for react-snapshot overview
* Explained pre-rendering in a more generic way
* Added link to top level README.md, and removed specifics from overview
* Updated html -> HTML
* Updated quotes and apostrophes
* html -> HTML
* Fix link
* add npm-link support
* - remove extra veriable
- simplify condition
* update code after review:
- remove utils/isReactScriptsLinked
- add appPath and ownPath to paths.js (but only for "before eject" export case)
* update code after review:
- remove utils/isReactScriptsLinked
- add appPath and ownPath to paths.js (but only for "before eject" export case)
* update code after review:
- remove utils/isReactScriptsLinked
- add appPath and ownPath to paths.js (but only for "before eject" export case)
- remove "if" block for fs.removeSync(ownPath) at ejec.tjs
* change ownPath value
* Install react and react-dom along with react-scripts
- Install react, react-dom and react-script in a same time
- Move react-scripts to devDependencies.
* Check if react, react-dom has been already installed
- To backward compatibility with old CRA’s cli
- In case old CRA doesn’t install react, react-don along with
react-scripts
* Use packageName to find script dependency
- use packageName to find dependency
- fix pathExists.sync
* Check dependencies.react in package.json instead of actual files
* Process exit when dependencies not found
- Show error and exit when dependencies not found.
- Log install show custom package name
* Remove template string
* Install dependencies if template is preseted
* Remove dangling comma
Resolves#1239
* Add note for using CHOKIDAR_USEPOLLING in virtual machines to enable HMR
* Use br in react-scripts template README md
* Use br in md for new line breaks
* Update troubleshooting HMR to allow for VMs running Windows
* Fix up the instructions
* Disable require.ensure
* Replace require.ensure with import
* Add babel plugin for parsing import()
* Get the default
* Upgrade babel-eslint to support dynamic import
* Fix dep
* Update deps
* update CSS preprocessor instructions
- Windows shell users should note that running two programs simultaneously is not supported.
* fix the order of SASS build step
- the suggested build step with integrated CSS preprocessing is wrong. The SASS preprocessor should run first, then the react-scripts build will pick the up-to-date final CSS
* Add tweaks from PR discussion
* Add SASS support documentation #1007
* Change SASS section title to more generic label
* Fix link in Table of Contents
* Chain build-css with watch-css script, fix typos
* Update Sass and Less naming style
* Fix wording, remove offensive words
* Slightly rewite
* Make build exit with error code when interrupted
This addresses issue #1493.
Current behavior is that `npm run build` exits code 0 without creating a bundle when interrupted. This change makes the build script catch catchable interruptions and exit with the appropriate error code.
* Better error messages for kill signals
* Don't catch SIGINT
Ctrl+C should exit silently, and already produces a non-zero exit code when sent to the console while `npm run build` is running. Exit code 0 is produced if SIGINT is sent directly to the `node build.js` process, but this is unlikely to happen. A SIGINT handler in `build.js` will also be triggered by Ctrl+C in the console, potentially producing unnecessary noise.
* Style fix
* No changes needed to build.js
Problem is coming from the parent process, `react-scripts`
* Make react-scripts script handle signals
* Clarify context
* Add Advanced Configuration section
* Reference package.json instead
* Add HOST, HTTPS, and CI
* Switch wording from Amazon to a CDN
* Add test runner comment
* Add top-level README link
* Simplify wording
* Link to relevant docs
* Link to apps
* Add .env link
* Simpler links
* Add a CI flag note
* Fix paths in CSS files when homepage is set to "./"
In the production build, ExtractTextPlugin is used to generate a separate CSS file instead of injecting style through JavaScript. This plugin does not work well by default with nested output structure. To fix it, we give it a relative publicPath pointing to the build folder.
* Add section in README to explain how to make builds deployable anywhere
* Apply review requested change
* Apply review changes 2
* Make all vars accessiable in index.html
* Fix wrong env provieded to DefinePlugin
* Separate results from getClientEnvironment
* The `string` should be object instead of string
* Fix accessing wrong field
* Changed variables naming to `raw` and `stringified`
* Remove trailing commas
