eclipse-wildwebdeveloper / eclipse-wildwebdeveloper/wildwebdeveloper
ESLintLanguageServer and JSTSLanguageServer do not support node memory limits (--max-old-space-size)
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 201
- Forks
- 76
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 21
Description
tangentially related to #1936
both ESLintLanguageServer and JSTSLanguageServer do not support node memory limits (--max-old-space-size) unlike launches that use getInitializationOptions to inherit the org.eclipse.wildwebdeveloper.maxTsServerMemory setting.
Internal ticket: PDINC-12768
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the launch implementations for ESLintLanguageServer and JSTSLanguageServer, then compare them with launches that use getInitializationOptions and the org.eclipse.wildwebdeveloper.maxTsServerMemory setting. Confirm how --max-old-space-size is passed and verify that both language servers honor the configured memory limit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, javascript, node.js
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100