Otherwise it makes it an invalid path :(

* 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

* Don't hardcode react-scripts package name

Fixes issue described in https://github.com/facebookincubator/create-react-app/issues/682#issuecomment-248781486.

* Update eject.js

Change "configs" to "configuration files" .

* Improve the output of scripts/init.js

* Add semi-colons;

Fixes #532

* Update Jest

* Remove default snapshot test

* Fix a few things

* Add a simple default test

* App.spec.js -> App.test.js

* Fix e2e test

* Bump Jest

* Get latest version numbers of react and react-dom from npm before install.

* Run separate npm installs for react, react-dom, and react-test-renderer.

* Consolidate into a single npm install.

* Fix misplaced parenthesis, add missing semicolon.

* Add missing semicolon.

* Creating a new app in the current directory

* Fixed style mistakes

* Provide instructions on GH Pages deploy

* Add docs for GH Pages deployment

* Prevent incorrect paths in file-loader

* Minor message tweaks

* Update README.md

* Fix relative paths

* explicitly specify ESLint config path for editor plugins

* changed to use single quote

* Adds .gitignore file to default template

* Simplify renames

* Reference npm issue in comment

* Removing leading slash

* Recursively copy the template folder

* add fs-extra library

It is easier to add more scripts later this way.

* Add README to generated project

* add logo.svg

* syntax cleanup

Summary:

Test Plan:

Reviewers:

CC:

Task ID: #

Test Plan:

```
npm pack
node global-cli/index.js testing --scripts-version /Users/vjeux/random/react-getting-started/create-react-app-scripts-0.0.1.tgz
```

make sure it shows

```
Creating the app testing at /Users/vjeux/random/react-getting-started/testing
```