-
Notifications
You must be signed in to change notification settings - Fork 339
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
The ESLint server crashed 5 times in the last 3 minutes. The server will not be restarted. #112
Comments
@artyomtrityak do you have a repository I can clone that shows the behavior. Usually when crashing the client doesn't have a lot of information why. |
+1 |
I was able to reproduce a case where a eslint plugin call process.exit() which in the case of the server shutdowns the server. It was basically a misconfiguration of the eslint / eslint plugin setup. I added code on the server that detects that case and shows a corresponding message to the user. |
See #114. I will keep this issue open until a new version of ESLint is publish to see if the exit is really causing this. |
Ok not I can see the ERROR in output: After installing it globally next error appears: TypeError: Cannot read property 'visitClass' of undefined Workaround: Upgrade babel-eslint (babel/babel-eslint#243) |
@abalmus good to see that you get better error messages now. At the end there is little the eslint extension can do if the eslint library has problems with a certain setup. What is always a good thing to do is to run eslint from the command line to see if it works. Any objections to close this issue. |
Yeah good point, thank you! I think this one can be closed. |
Closing. |
I got this message "The ESLint server crashed 5 times in the last 3 minutes. The server will not be restarted." on .jsx file save.
There is no explanation why was it crashed 5 times and how to fix this issue.
Is there any way to understand how to fix this issue and see more explicit error?
Some details:
.eslintrc
The text was updated successfully, but these errors were encountered: