JS/TS server is started multiple time

Hi,
I'm beginning to test WildWebDeveloper in a fairly large workspace, with many projects containing TypeScript sources.

I see some strange effects, like:

• multiple identical Content Assist proposals (I have seen up to six),
• lots and lots of Node processes as children of Eclipse, even for projects for which I have no editor active,
• most importantly, a considerable slowdown while typing.

I still need to do more tests, so I cannot give you exact reproduction steps right now.

To give you the picture, I have 22 Eclipse projects that contain TS sources (and a tsconfig.json).
I am also using monorepo-like tooling, so my common libraries are all installed in a top-level node_modules directory.
The fact that there are multiple Node processes running does worry me, since I suspect that the same huge JS libraries are being parsed and evaluated multiple times, by every one of the servers.

I noticed that language server have a singleton property that guarantees that they are started only once per workspace.
However, the JS/TS language server is the only one that is not marked as singleton.
Why is that? Is it a deliberate choice or just an oversight?

A while back I had tried setting it as singleton and everything appeared to work perfectly.

Thanks.

Commencez par examiner la configuration du serveur de langage JS/TS et son paramètre singleton, puis comparez la manière dont les autres serveurs de langage sont démarrés. Le travail est terminé lorsqu’il est confirmé qu’il y a un serveur par workspace et que les propositions en double de content-assist, l’excès de processus Node et le ralentissement de la saisie sont résolus.