update ma' fork

.eslintignore

@@ -0,0 +1,6 @@
+node_modules/
+build
+my-app*
+packages/react-scripts/template
+packages/react-scripts/fixtures
+fixtures/

.eslintrc

@@ -1,3 +1,17 @@
 {
-  "extends": "react-app"
+  "extends": "eslint:recommended",
+  "env": {
+    "browser": true,
+    "commonjs": true,
+    "node": true,
+    "es6": true
+  },
+  "parserOptions": {
+    "ecmaVersion": 2018
+  },
+  "rules": {
+    "no-console": "off",
+    "strict": ["error", "global"],
+    "curly": "warn"
+  }
 }

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,168 @@
+<!--
+  PLEASE READ THE FIRST SECTION :-)
+-->
+
+### Is this a bug report?
+
+(write your answer here)
+
+<!--
+  If you answered "Yes":
+
+    Please note that your issue will be fixed much faster if you spend about
+    half an hour preparing it, including the exact reproduction steps and a demo.
+
+    If you're in a hurry or don't feel confident, it's fine to report bugs with
+    less details, but this makes it less likely they'll get fixed soon.
+
+    In either case, please fill as many fields below as you can.
+
+  If you answered "No":
+
+    If this is a question or a discussion, you may delete this template and write in a free form.
+    Note that we don't provide help for webpack questions after ejecting.
+    You can find webpack docs at https://webpack.js.org/.
+-->
+
+### Did you try recovering your dependencies?
+
+<!--
+  Your module tree might be corrupted, and that might be causing the issues.
+  Let's try to recover it. First, delete these files and folders in your project:
+
+    * node_modules
+    * package-lock.json
+    * yarn.lock
+
+  Then you need to decide which package manager you prefer to use.
+  We support both npm (https://npmjs.com) and yarn (http://yarnpkg.com/).
+  However, **they can't be used together in one project** so you need to pick one.
+
+  If you decided to use npm, run this in your project directory:
+
+    npm install -g npm@latest
+    npm install
+
+  This should fix your project.
+
+  If you decided to use yarn, update it first (https://yarnpkg.com/en/docs/install).
+  Then run in your project directory:
+
+    yarn
+
+  This should fix your project.
+
+  Importantly, **if you decided to use yarn, you should never run `npm install` in the project**.
+  For example, yarn users should run `yarn add <library>` instead of `npm install <library>`.
+  Otherwise your project will break again.
+
+  Have you done all these steps and still see the issue?
+  Please paste the output of `npm --version` and/or `yarn --version` to confirm.
+-->
+
+(Write your answer here.)
+
+### Which terms did you search for in User Guide?
+
+<!--
+  There are a few common documented problems, such as watcher not detecting changes, or build failing.
+  They are described in the Troubleshooting section of the User Guide:
+
+  https://github.com/facebook/create-react-app/blob/master/packages/react-scripts/template/README.md#troubleshooting
+
+  Please scan these few sections for common problems.
+  Additionally, you can search the User Guide itself for something you're having issues with:
+
+  https://github.com/facebook/create-react-app/blob/master/packages/react-scripts/template/README.md
+
+  If you didn't find the solution, please share which words you searched for.
+  This helps us improve documentation for future readers who might encounter the same problem.
+-->
+
+(Write your answer here if relevant.)
+
+
+### Environment
+
+<!--
+  To help identify if a problem is specific to a platform, browser, or module version, information about your environment is required.
+  This enables the maintainers quickly reproduce the issue and give feedback.
+
+  Run the following command in your React app's folder in terminal.
+  Note: The result is copied to your clipboard directly.
+
+  `npx create-react-app --info`
+
+  Paste the output of the command in the section below.
+-->
+
+(paste the output of the command here)
+
+### Steps to Reproduce
+
+<!--
+  How would you describe your issue to someone who doesn’t know you or your project?
+  Try to write a sequence of steps that anybody can repeat to see the issue.
+-->
+
+(Write your steps here:)
+
+1. 
+2. 
+3. 
+
+
+### Expected Behavior
+
+<!--
+  How did you expect the tool to behave?
+  It’s fine if you’re not sure your understanding is correct.
+  Just write down what you thought would happen.
+-->
+
+(Write what you thought would happen.)
+
+
+### Actual Behavior
+
+<!--
+  Did something go wrong?
+  Is something broken, or not behaving as you expected?
+  Please attach screenshots if possible! They are extremely helpful for diagnosing issues.
+-->
+
+(Write what happened. Please add screenshots!)
+
+
+### Reproducible Demo
+
+<!--
+  If you can, please share a project that reproduces the issue.
+  This is the single most effective way to get an issue fixed soon.
+
+  There are two ways to do it:
+
+    * Create a new app and try to reproduce the issue in it.
+      This is useful if you roughly know where the problem is, or can’t share the real code.
+
+    * Or, copy your app and remove things until you’re left with the minimal reproducible demo.
+      This is useful for finding the root cause. You may then optionally create a new project.
+
+  This is a good guide to creating bug demos: https://stackoverflow.com/help/mcve
+  Once you’re done, push the project to GitHub and paste the link to it below:
+-->
+
+(Paste the link to an example project and exact instructions to reproduce the issue.)
+
+<!--
+  What happens if you skip this step?
+
+  We will try to help you, but in many cases it is impossible because crucial
+  information is missing. In that case we'll tag an issue as having a low priority,
+  and eventually close it if there is no clear direction.
+
+  We still appreciate the report though, as eventually somebody else might
+  create a reproducible example for it.
+
+  Thanks for helping us help you!
+-->

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,7 @@
+<!--
+Thank you for sending the PR!
+
+If you changed any code, please provide us with clear instructions on how you verified your changes work. Bonus points for screenshots!
+
+Happy contributing!
+-->

.gitignore

@@ -1,8 +1,13 @@
+.idea/
+.vscode/
 node_modules/
 build
 .DS_Store
 *.tgz
 my-app*
 template/src/__tests__/__snapshots__/
 lerna-debug.log
-npm-debug.log
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+/.changelog

.prettierrc

@@ -0,0 +1,5 @@
+{
+  "trailingComma": "es5",
+  "singleQuote": true,
+  "semi": true
+}

.travis.yml

@@ -1,11 +1,35 @@
 ---
+dist: trusty
 language: node_js
 node_js:
-  - 4
-  - 6
+  - 8
+  - 10
 cache:
+  yarn: true
   directories:
-  - node_modules
-  - packages/create-react-app/node_modules
-  - packages/react-scripts/node_modules
-script: tasks/e2e.sh
+    - .npm
+before_install:
+  - curl -o- -L https://yarnpkg.com/install.sh | bash -s -- --nightly
+  - export PATH="$HOME/.yarn/bin:$PATH"
+install: true
+script:
+  - 'if [ $TEST_SUITE = "simple" ]; then tasks/e2e-simple.sh; fi'
+  - 'if [ $TEST_SUITE = "installs" ]; then tasks/e2e-installs.sh; fi'
+  - 'if [ $TEST_SUITE = "kitchensink" ]; then tasks/e2e-kitchensink.sh; fi'
+  - 'if [ $TEST_SUITE = "kitchensink-eject" ]; then tasks/e2e-kitchensink-eject.sh; fi'
+  - 'if [ $TEST_SUITE = "old-node" ]; then tasks/e2e-old-node.sh; fi'
+  - 'if [ $TEST_SUITE = "behavior" ]; then tasks/e2e-behavior.sh; fi'
+env:
+  matrix:
+    - TEST_SUITE=simple
+    - TEST_SUITE=installs
+    - TEST_SUITE=kitchensink
+    - TEST_SUITE=kitchensink-eject
+    - TEST_SUITE=behavior
+matrix:
+  include:
+    - os: osx
+      node_js: 8
+      env: TEST_SUITE=behavior
+    - node_js: 4
+      env: TEST_SUITE=old-node