How to configure embeded typescript-language-server?

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
typescript

Research direction

Start with docs/configuration.md, especially its configuration section, then review the Eclipse Web Developer settings pages and the issue's described tsserver and typescript-language-server flow. Determine whether the needed configuration is supported through Eclipse or requires an external launch configuration, and document the supported setup and configuration location.

Written by the indexing model from the issue text.

Description

contributions welcome enhancement

I'm plagued by the diagnostic message File is a CommonJS module; it may be converted to an ES module. [80001].

I know it's coming from tsserver itself and passes through the internal handler typescript-language-server somehow.
I can configure tsserver itself by placing a file at the right location, but that only allows to fully disable all diagnostics, which is not helpful at all.
I know the typescript-language-server allows to configure ignores on a more granular level, as documented here.

But i can't for the life of me find out just HOW i get to pass the needed config values through eclipse. And the web developers settings pages for language server configurations are pretty lacking in that department, if existing at all.

Do i really have to define an external language server launch configuration, just to somehow get some options changed? Or is there some kind of well-known file for the typescript-language-server that is magically detected and read when in the workspace/project root?

Dominant language
Java
Stars
203
Forks
76
Avg merge
1d 5h
Merged PRs (30d)
30

Getting set up

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.

More from eclipse-wildwebdeveloper/wildwebdeveloper

All issues in eclipse-wildwebdeveloper/wildwebdeveloper

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.