-
-
Notifications
You must be signed in to change notification settings - Fork 190
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
ESLint behaves differently on different system #4540
Comments
Comment thread where two more people experienced this: #4506 (comment) In my case, it was something about my local dev environment that was off. Unfortunately, I didn't document the fix that ended up working, and haven't been able to repro the bug. It wasn't a complex fix. It might have been removing |
I did several variations of the following to no effect: # in ./core
# I don't know that there's more than one of these, but it's best to be sure
find . -type f -name ".eslintcache" -exec rm {} +
rm -rf node_modules
yarn cache clean |
ESLint succeeds in fresh clone of the repo, but only in a different directory on my system. If I delete my original copy of the repo and replace it with the freshly cloned copy, it starts failing again. There are no I'll leave this open for other people who are debugging their local ESLint behavior. |
I've just run into this problem again. There are two lint issues I see locally. I have tried all of the solutions posted above to remove them without success. I've attempted to fix these here but we shouldn't have to do this: #4545 |
Still running into this problem as of October 2024 — this time it's the |
Recently, @mcmire put up #4537 to address some lint errors he observes locally (ref: #4537 (comment)). These began to appear on his system after my PR #4521. I am unable to observe the same errors. On the other hand, I observe no less than 44 errors from the root
yarn lint
on current main (b7fa70e):ESLint output
The text was updated successfully, but these errors were encountered: