question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

issue when npm start

See original GitHub issue

G:\react\myapp>npm start

myapp@0.1.0 start G:\react\myapp react-scripts start

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.

The react-scripts package provided by Create React App requires a dependency:

“babel-loader”: “8.1.0”

Don’t try to install it manually: your package manager does it automatically. However, a different version of babel-loader was detected higher up in the tree:

G:\node_modules\babel-loader (version: 8.0.6)

Manually installing incompatible versions is known to cause hard-to-debug issues.

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.

To fix the dependency tree, try following the steps below in the exact order:

  1. Delete package-lock.json (not package.json!) and/or yarn.lock in your project folder.
  2. Delete node_modules in your project folder.
  3. Remove “babel-loader” from dependencies and/or devDependencies in the package.json file in your project folder.
  4. Run npm install or yarn, depending on the package manager you use.

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:

  1. If you used npm, install yarn (http://yarnpkg.com/) 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.

  2. Check if G:\node_modules\babel-loader is outside your project directory. For example, you might have accidentally installed something in your home folder.

  3. Try running npm ls babel-loader in your project folder. This will tell you which other package (apart from the expected react-scripts) installed babel-loader.

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.S. We know this message is long but please read the steps above 😃 We hope you find them helpful!

npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! myapp@0.1.0 start: react-scripts start npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the myapp@0.1.0 start script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:14

github_iconTop GitHub Comments

5reactions
Tsioriantenainacommented, Jun 27, 2020

You must just create .env file in your app folder and add SKIP_PREFLIGHT_CHECK=true run yarn start or npm start It’s work for me .

4reactions
vbasooncommented, Jul 10, 2020

I just create .env file in my app folder add SKIP_PREFLIGHT_CHECK=true. It’s work. Thanx Tsioriantenaina.

Read more comments on GitHub >

github_iconTop Results From Across the Web

How to fix npm start command not working - Nathan Sebhastian
How to fix npm start command not working · Check if you have a package.json file in your project · Check if you...
Read more >
npm start giving error in node.js - Stack Overflow
The error suggests that the ./bin/www directory is not found. Paths specified with a dot are relative to the current directory, ...
Read more >
npm start not working, tried many solves :| #1328 - GitHub
derweili commented on Jan 17, 2019 · Delete the node_modules folder. · Open the package.json · Search for "gulp": "gulpjs/gulp#4.0", and replace it ......
Read more >
npm start issue in vs code : r/reactjs - Reddit
npm start issue in vs code ... Any help would be appreciated! ... Solved! I had to go one more layer into my...
Read more >
Common errors | npm Docs
Some strange issues can be resolved by simply running npm cache clean and trying again. · If you are having trouble with npm...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found