Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error of yarn, crap and eslint #40

Open
lemito opened this issue Dec 22, 2019 · 5 comments
Open

Error of yarn, crap and eslint #40

lemito opened this issue Dec 22, 2019 · 5 comments
Labels
bug Something isn't working help wanted Extra attention is needed

Comments

@lemito
Copy link

lemito commented Dec 22, 2019

`yarn run v1.19.1
$ react-scripts-parcel 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-parcel package provided by Create React App requires a dependency:

"eslint": "^4.19.1"

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

D:\react-parcel\node_modules\eslint (version: 4.19.1)

Manually installing incompatible versions is known to cause hard-to-debug 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 "eslint" 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 D:\react-parcel\node_modules\eslint is outside your project directory.
    For example, you might have accidentally installed something in your home folder.

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

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!

error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.`

@ogrotten
Copy link

ogrotten commented Dec 2, 2020

Welp, here I am a year later getting the same error.

Oh well.

@ogrotten
Copy link

ogrotten commented Dec 2, 2020

@MasterCpp if you're still interested, it was fixed by removing from node_modules the folders eslint, eslint-scope, eslint-visitor-keys.

Don't bother doing yarn next, just do yarn start. It will try to run, notice something is missing, install the right modules, then run again but successfully this time.

@lemito
Copy link
Author

lemito commented Dec 4, 2020

@MasterCpp if you're still interested, it was fixed by removing from node_modules the folders eslint, eslint-scope, eslint-visitor-keys.

Don't bother doing yarn next, just do yarn start. It will try to run, notice something is missing, install the right modules, then run again but successfully this time.

thank you)

@ogrotten
Copy link

ogrotten commented Dec 4, 2020

@MasterCpp Nevermind that.

I gave up on it. Even once it started working, it failed at random with the same error, AND there's a perpetual console "syntax error" in a file that I couldn't find . . . which probably means that it wouldn't build at any point.

So I gave up.

@assuncaocharles assuncaocharles added bug Something isn't working help wanted Extra attention is needed labels Dec 7, 2020
@xrv0
Copy link

xrv0 commented Mar 26, 2021

This is still a thing...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

4 participants