eclipse-wildwebdeveloper / eclipse-wildwebdeveloper/wildwebdeveloper

"[Info] ESLint server running in node v18.18.2" keeps showing up in logs

Open
#1,549 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
201
Forks
76
Avg merge
4d 7h
Merged PRs (30d)
21

Description

I keep seeing multiple entries of the following message in the Error Log (Eclipse IDE 2024-06 M2)

[Info]	ESLint server running in node v18.18.2

Does this mean that the server gets restarted? Why? I don't see a corresponding error message.
If there was an error, it should be shown.
If there was no error, the message should not appear again in the logs.

(I use the error log to check for new messages coming from a specific Maven plugin, and this repetitive noise is quite annoying)

eclipse.buildId=4.32.0.20240502-0721
java.version=21.0.3
java.vendor=Eclipse Adoptium
BootLoader constants: OS=macosx, ARCH=aarch64, WS=cocoa, NL=en_US
Framework arguments:  -product org.eclipse.epp.package.jee.product -keyring /Users/ck/.eclipse_keyring
Command-line arguments:  -os macosx -ws cocoa -arch aarch64 -product org.eclipse.epp.package.jee.product -keyring /Users/ck/.eclipse_keyring

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the repeated ESLint server message in the Eclipse IDE 2024-06 M2 environment described in the report, then trace when the ESLint server starts or restarts and how that message reaches the Error Log. Done means the cause is understood and the repetitive informational entries no longer create misleading log noise, while genuine errors remain visible.

Written by the indexing model from the issue text.

Assessment

Tech stack
eslint, node.js
Domain
developer-experience, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.