Consider extracting yaml-language-service from yaml-language-server

Summary

I would like to be able to depend on the language service part without pulling in the language server part and all of its dependencies.

Relevant information

I’m working on monaco-yaml. monaco-yaml depends on the YAML language service part in this package, but not on the language server. Currently a build process is needed to include the language service, but ideally I would like to be able to simply add it as a dependency without pulling in the language server part and its dependencies.

I believe extracting the language service also helps to better separate the two parts. monaco-yaml still depends on an older version of yaml-language-server, but I noticed the latest version of the language service also uses some imports from the language server.

I understand if this gets rejected, because it adds an additional maintenance burden, but I wanted to ask anyway to see what you think of it. I think using a yarn mono repository reduces the additional maintenance a lot.

Start by reviewing how the language service and language server are currently packaged and which imports cross between them. Check the yarn monorepo approach and the dependencies needed by monaco-yaml. Done means the language service can be added independently without pulling in the language server or its dependencies.