-
Notifications
You must be signed in to change notification settings - Fork 266
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider extracting yaml-language-service from yaml-language-server #524
Comments
@remcohaszing I'm not clear, what language service do you want to extract? Do you mean |
Yes. I would like the This is similar to |
Hi all, To solve the issue I bundled The idea of @remcohaszing of the monorepo with 2 packages (yaml-language-server and yaml-language-service) should give us the possibility to use the language service part without other dependencies. What do you think? Other information The version of Logs file: webpack.log In my fork there is the code giving the error: |
Hi, any update on this issue? We would also like to request the same feature due to the size of the bundle being increased by ~11MB due to the |
@elvin-hwang The language service part uses Prettier. This issue isn’t related to what you describe. See #933 instead. |
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.
, but I noticed the latest version of the language service also uses some imports from the language server.monaco-yaml
still depends on an older version ofyaml-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.
The text was updated successfully, but these errors were encountered: