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.

eslint shutdown issue

See original GitHub issue

I am using the .eslintrc.json file that came with the boilerplate. The eslint server stops running and I get the below error logs in my VSCODE console’s eslint output.

[Info  - 10:36:36 PM] ESLint server stopped.
[Info  - 10:36:36 PM] ESLint server running in node v10.2.0
[Info  - 10:36:36 PM] ESLint server is running.
"process.env.NODE_ENV" must be "development" to use this webpack config
[Error - 10:38:09 PM] Server process exited with code undefined. This usually indicates a misconfigured ESLint setup.
[Error - 10:38:10 PM] Connection to server got closed. Server will not be restarted.
[Info  - 10:38:10 PM] ESLint server stopped.

Not sure why it says nodev10.2.0 when I don’t have that version installed. I only have 10.15.1 installed.

Prerequisites

  • [ 💚] Using yarn
  • [ 💚] Using node 10.x
  • [💚 ] Using an up-to-date master branch
  • [💚 ] Using latest version of devtools. See wiki for howto update
  • [💚 ] Link to stacktrace in a Gist (for bugs)
  • [💚 ] For issue in production release, devtools output of DEBUG_PROD=true yarn build && yarn start
  • [💚 ] Tried solutions mentioned in #400

Expected Behavior

eslint server must work properly.

Current Behavior

Its crashing

Your Environment

  • Node version : 10.15.1
  • Version or Branch used :
  • Operating System and version : osx mojave latest version
  • Link to your project : -

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Reactions:1
  • Comments:10 (3 by maintainers)

github_iconTop GitHub Comments

2reactions
supersudhcommented, Feb 25, 2019

Seems like this is an eslint issue. I am not facing the shutdown anymore if I try the below solution.

Add process.env.NODE_ENV = ‘development’; in ./node_modules/eslint/lib/api.js

1reaction
vikr01commented, Feb 25, 2019

If you notice we set NODE_ENV=development before running eslint in our script. So the issue is neither with the boilerplate nor eslint, it’s with vscode-eslint and setting the environment variable.

Read more comments on GitHub >

github_iconTop Results From Across the Web

ESLint server shut down itself · Issue #618 - GitHub
I started getting this error today out of the blue. "ESLint server shut down itself. See 'ESLint' output channel for details.
Read more >
ESLint | WebStorm Documentation - JetBrains
To resolve all the detected problems in the current file, click More actions ( Alt+Enter ) and select ESLint: Fix current file from...
Read more >
VS Code ESLint extension - Visual Studio Marketplace
Extension for Visual Studio Code - Integrates ESLint JavaScript into VS Code. ... The version also adds a command to restart the ESLint...
Read more >
prefer-const - ESLint - Pluggable JavaScript Linter
A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease.
Read more >
ESLint doesn't restart after killing port in create-react-app
If I then shut down the CRA with npx kill-port [port-number] and then restart the CRA, the app compiles successfully with no ESLint...
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