Quest: let's forward _all_ the ServerCapabilities to tsserver

[NullVoxPopuli]

Goal:

Achieve parity between tsserver and glint so that folks don't feel the need to have both servers active (which would consume more RAM)

Each capability should be its own PR -- some PRs will be more involved from others, and some may be straight-forward.

---

Here is where we need to configure: https://github.com/typed-ember/glint/blob/main/packages/core/src/language-server/binding.ts#L19

"ServerCapabilities"

Here is the full list:
https://github.com/microsoft/vscode-languageserver-node/blob/main/protocol/src/common/protocol.ts#L1068

Features we want?

(and probably more)

Here are the features from reported requests we can add

• Semantic Token Scopes not provided #601
  Note from discord:

  semantic highlighting is a little tricky mostly for performance reasons
  the standard TS plugin for Code actually spawns a second tsserver instance just for semantic highlighting

• TypeScript language server code-folding
  Note from discord:

  code folding should be straightforward

• textDocument/documentSymbol

• progress
  Shows ui indicator in $editor for booting/loading, pending, etc
  https://github.com/microsoft/vscode-languageserver-node/blob/main/protocol/src/common/protocol.ts#L1104

[camerondubas]

@NullVoxPopuli I'd be happy to help with this. I have a little bit of experience with language servers, but not a ton. Could you point me in the right direction to get started?

[NullVoxPopuli]

Hello!, given the list of server capabilities in protocol.ts (linked above), is there a particular one you'd like to start with implementing?

we only want one server capabilities addition per PR (for ease of testing)

[IgnaceMaes]

Thanks for setting up this initiative!

Two features I would like to see as well are:

• The TypeScript: Sort Imports command

• Inlay type hints to show inferred types inline

I haven't done any digging so no clue how straight forward these should be.