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

The ESLint server crashed 5 times in the last 3 minutes. The server will not be restarted. #112

Closed
artyomtrityak opened this issue Aug 17, 2016 · 8 comments
Labels
info-needed Issue requires more information from poster

Comments

@artyomtrityak
Copy link

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:

"babel-eslint": "^4.1.8",
"eslint": "^2.4.0",
"eslint-plugin-react": "^3.16.1",

.eslintrc

{
  "env": {
    "browser": true,
    "node": true
  },
  "parser": "babel-eslint",
  "plugins": ["react"],
  "globals": {
    "define": true,
    "requirejs": true,
    "analytics": true
  },
  "rules": {
    "semi": [2, "always"],
    "no-alert": 2,
    "no-debugger": 2,
    "no-empty": 2,
    "new-cap": 0,
    "no-dupe-class-members": 2,
    "no-restricted-syntax": [2, "WithStatement"],
    "no-unused-expressions": 2,
    "no-trailing-spaces": 1,
    "no-shadow": 2,
    "no-undef": 2,
    "no-use-before-define": 0,

    "react/jsx-boolean-value": [2, "always"],
    "react/jsx-no-undef": 2,
    "react/jsx-uses-react": 2,
    "react/jsx-uses-vars": 2,
    "react/no-did-mount-set-state": 2,
    "react/no-did-update-set-state": 2,
    "react/no-multi-comp": 1,
    "react/no-unknown-property": 2,
    "react/react-in-jsx-scope": 2
  }
}
@dbaeumer
Copy link
Member

@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.

@dbaeumer dbaeumer added the info-needed Issue requires more information from poster label Aug 18, 2016
@abalmus
Copy link

abalmus commented Aug 24, 2016

+1

@dbaeumer
Copy link
Member

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.

@dbaeumer
Copy link
Member

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.

@abalmus
Copy link

abalmus commented Sep 14, 2016

Ok not I can see the ERROR in output:
Error: Cannot find module 'estraverse-fb'

After installing it globally next error appears:

TypeError: Cannot read property 'visitClass' of undefined
at monkeypatch (/usr/local/lib/node_modules/babel-eslint/index.js:199:40)

Workaround: Upgrade babel-eslint (babel/babel-eslint#243)

@dbaeumer
Copy link
Member

@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.

@abalmus
Copy link

abalmus commented Sep 14, 2016

Yeah good point, thank you! I think this one can be closed.

@dbaeumer
Copy link
Member

Closing.

@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 21, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
info-needed Issue requires more information from poster
Projects
None yet
Development

No branches or pull requests

3 participants