title: "babel-eslint" can't let me install react
body: <p>I am setting up a new react App, having installed it, i then added a name to the react app i begin to have a <code>babel-eslint</code> issue</p>
  
  <blockquote>
    <p>portfolio@0.1.0 start C:\Users\Samson Adedayo\Desktop\portfolio<br>
    react-scripts start</p>
  </blockquote>
  
  <p>There might be a problem with the project dependency tree.
  It is likely not a bug in Create React App, but something you need to fix locally.</p>
  
  <p>The react-scripts package provided by Create React App requires a dependency:</p>
  
  <p>"babel-eslint": "10.0.2"</p>
  
  <p>Don't try to install it manually: your package manager does it automatically.
  However, a different version of babel-eslint was detected higher up in the tree:</p>
  
  <p>C:\Users\Samson Adedayo\Desktop\node_modules\babel-eslint (version: 10.0.1)</p>
  
  <p>Manually installing incompatible versions is known to cause hard-to-debug issues.</p>
  
  <p>If you would prefer to ignore this check, add SKIP_PREFLIGHT_CHECK=true to an .env file in your project.
  That will permanently disable this message but you might encounter other issues.</p>
  
  <p>To fix the dependency tree, try following the steps below in the exact order:</p>
  
  <ol>
  <li>Delete package-lock.json (not package.json!) and/or yarn.lock in your project folder.</li>
  <li>Delete node_modules in your project folder.</li>
  <li>Remove "babel-eslint" from dependencies and/or devDependencies in the package.json file in your project folder.</li>
  <li>Run npm install or yarn, depending on the package manager you use.</li>
  </ol>
  
  <p>In most cases, this should be enough to fix the problem.
  If this has not helped, there are a few other things you can try:</p>
  
  <ol start="5">
  <li><p>If you used npm, install yarn (<a href="http://yarnpkg.com/" rel="nofollow noreferrer">http://yarnpkg.com/</a>) and repeat the above steps with it instead.
   This may help because npm has known issues with package hoisting which may get resolved in future versions.</p></li>
  <li><p>Check if C:\Users\Samson Adedayo\Desktop\node_modules\babel-eslint is outside your project directory.
   For example, you might have accidentally installed something in your home folder.</p></li>
  <li><p>Try running npm ls babel-eslint in your project folder.
   This will tell you which other package (apart from the expected react-scripts) installed babel-eslint.</p></li>
  </ol>
  
  <p>If nothing else helps, add SKIP_PREFLIGHT_CHECK=true to an .env file in your project.
  That would permanently disable this preflight check in case you want to proceed anyway.</p>
  
  <p>P.S. We know this message is long but please read the steps above :-) We hope you find them helpful!</p>
  
  <p>npm ERR! code ELIFECYCLE
  npm ERR! errno 1
  npm ERR! portfolio@0.1.0 start: <code>react-scripts start</code>
  npm ERR! Exit status 1
  npm ERR!
  npm ERR! Failed at the portfolio@0.1.0 start script.
  npm ERR! This is probably not a problem with npm. There is likely additional logging output above.</p>
  
  <p>npm ERR! A complete log of this run can be found in:
  npm ERR!     C:\Users\Samson Adedayo\AppData\Roaming\npm-cache_logs\2019-09-11T18_30_41_153Z-debug.log</p>