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.

Bắt đầu bằng cách kiểm tra cấu hình language server JS/TS và thiết lập singleton của nó, sau đó so sánh cách các language server khác được khởi động. Hoàn tất nghĩa là xác nhận mỗi workspace có một server và đã xử lý các đề xuất content-assist trùng lặp, số lượng tiến trình Node dư thừa và tình trạng chậm khi gõ.