- 09 Aug, 2017 1 commit
-
-
Konstantin Tarkus authored
* Fix the order of arguments in spawned child proc * Update react-scripts.js * Remove a comma * Update react-scripts.js
-
- 02 Aug, 2017 1 commit
-
-
Kiho · Cham authored
The create-react-app need node >= 6, and node version 6 support a lot of ES6, and let's switch using '+' to concat string with template string.
-
- 22 May, 2017 1 commit
-
-
Pavol Madar authored
-
- 18 May, 2017 1 commit
-
-
Danil Shashkov authored
-
- 07 Mar, 2017 1 commit
-
-
Valerii Sorokobatko authored
* mv create-react-app/index.js -> create-react-app/creteReactApp.js * update to modern code style * var -> cosnt * set trailing-coma to es5 for prettier
-
- 06 Mar, 2017 1 commit
-
-
Dan Abramov authored
-
- 05 Mar, 2017 1 commit
-
-
Dan Abramov authored
* Lint internal scripts with eslint:recommended * Warnings r bad
-
- 12 Feb, 2017 1 commit
-
-
pd4d10 authored
-
- 11 Feb, 2017 1 commit
-
-
Brandon Istenes authored
* 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
-
- 19 Sep, 2016 1 commit
-
-
Ville Immonen authored
-