* Bump minimal Node version to 4.7.0
* Bump minimal Node version to 4.7.0
Modified additional files that needed a bump to 4.7.0 minimum node version
* Bump minimal Node version to 4.7.0
Reverse changes to packages/create-react-app/index.js as this file needs to continue to work on Node 0.10+
* Bump minimal node version to 6
* Bump minimal node version to 6
* Bump minimal node version to 6
* Allow creation of apps in empty mercurial repos
* Adding .hgignore to list of validFiles for isSafeToCreateProjectIn check
* Adding .hgcheck to list of validFiles for isSafeToCreateProjectIn check
* 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
* Properly extract package name
* Download package if need be ...
* Oops
* Add e2e test based on #1537, but without specific filename
* Pass packageName through promises
A little bit more verbose but explicit and doesn't rely on shared mutable state.
* Fix up directory name in test
* Tweak failure message
* Fix lint
* add --offline flag when we are using yarn and we are offline
* Revert changes to init script
We only run these commands for backward compat mode, in which we wouldn't receive the offline flag anyway
* Don't pass isOnline to init script because it doesn't need it
* Don't ping the Yarn registry if user doesn't have Yarn
* Remove unused/wrong arguments
* Move logs to error handler
* Fix error handling
* Report to the user that they're offline
* Implemented a version check of npm to give a soft tip during the install procedure
and fixed gitignore
* Moved NPM check to method, it is only executed when you use NPM and the version is < 3.
* Minor formatting tweaks
* Simplify the code
* Remove unnecessary change
* 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
* Use a more sophisticated template for end-to-end testing.
* Not publish integration tests to npm
* Use "commander" for cli argv handling
* Handle different scripts version forms and exits without a name given
* Prepare the commands for testing with a template
* Fix dev "template" path
* Add various features to test
* Test various features separately
* Test language features
* Comment unused e2e.sh lines
* Add "development" tests
* Test environment variables
* Test webpack plugins
* Replace kitchensink README
* Switch integration tests from jest to mocha
* Use `fs-extra`
* Use the correct folders
* Do some cleanup
* Print a better message for `--template`
* Test `npm start` with and without https
* Separate fast e2e testing from kitchensink testing
* Hide `--internal-testing-template` (former `--template`) CLI option
There’s a common tool included in Hadoop that also has a `yarn` command,
which created issues for users who had Hadoop installed:
* #1257
* #1363
Yarn also installs the command under `yarnpkg` alias (added in
cefa9a368d)
so we can use `yarnpkg` instead of `yarn` to make it more reliable.
This has no effect on users who don't have Hadoop installed, but those
who have won't see errors from falsely detecting Hadoop Yarn as Yarn
the package manager, and they can now also install Yarn to make use of
our Yarn support without the Hadoop Yarn interfering.
There’s a common tool included in Hadoop that also has a `yarn` command,
which created issues for users who had Hadoop installed:
* #1257
* #1363
Yarn also installs the command under `yarnpkg` alias (added in
cefa9a368d)
so we can use `yarnpkg` instead of `yarn` to make it more reliable.
This has no effect on users who don't have Hadoop installed, but those
who have won't see errors from falsely detecting Hadoop Yarn as Yarn
the package manager, and they can now also install Yarn to make use of
our Yarn support without the Hadoop Yarn interfering.
* Use "commander" for cli argv handling
* Handle different scripts version forms and exits without a name given
* Revert comment about min supported node version
* Check sooner for the minimal node version
* Add travis test for node <4
* Parse stderr in node versions <4
* Remove the “‘yarn’ is not recognized as an internal or external
command, ...” message on Windows
* Simplify the detection code: just run `yarn --version` – if it
succeeds use `yarn`, if it fails use `npm`.
In the `create-react-app` command, try to install packages using Yarn.
If Yarn is not installed, use npm instead.
In `react-scripts`, detect if the project is using Yarn by checking if
a `yarn.lock` file exists. If the project is using Yarn, display all
the instructions with Yarn commands and use Yarn to install packages
in `init` and `eject` scripts.
* Add supports for prelease tags version
* Add comment to regex
* Cut everything after the first -\d
* Make semver version optional, so just package name get parsed correctly
* Support passing scoped package names to --scripts-version arg
* Factor out bitwise operator in indexOf test
* Comment on stripping only version or tag from package name arg
