* Adds the PnP plugin for Webpack to find dependencies when working under PnP
* Adds configuration for jest
* Adds an e2e test for when using PnP
* Avoids cra from crashing at the engine check
* Avoids cra from crashing when initializing react-scripts
* Makes the ownPath portable
* Fixes linting
* Bumps to pnp-webpack-plugin@1.1.0, removes symlinks: false
* Adds a --use-pnp option
* Pin version
* Create git repo with initial commit
* Fixe commit message
* Added the git repo to the docs
* Bail if we are in a mercurial repository
* Removed Chore from commit mesage
* Create repo after installing react and react-dom
* Removed docs
* Commit changes when ejecting
* Update after review
* git add -A instead of git add . after code review
* Offer to set browser defaults
* Catch error on no
* Add ending newlines
* Ensure we re-check to prevent defaults from leaking
* Reduce nesting
* Add defaults message
* More explicit
* Provide better defaults
* Let babel determine features to compile
* meh
* Remove setting of BABEL_ENV
* Revert "Remove setting of BABEL_ENV"
This reverts commit ee2db707faa8b9ada3e7a668e8a94944f5955a1e.
* Set browsers to ie9
* Fix for issue #1798: Suggested 'yarn build' versus 'yarn run build'
* remove 'run' from 'yarn test' command as well
* conditionally show 'run' if Yarn is not available
* 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
* Refactor start script into modules
* Move dev server config into config file
* Replace eject file whitelist with a "remove-file-on-eject" flag
* Move utils into scripts folder (for inclusion in ejection)
* Add missed changes
* Pass showInstructions as an argument
* Fix eject bug
* Don't eject babelTransform
* 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
* 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.
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.
* Forked react-scripts should retain the binary name
* Forked react-scripts should retain the binary name -- fixed issue with regex
* Forked react-scripts should retain the binary name -- fixed style nit
