You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #2267 there is an example of a plugin/module that one can create for Volar. It's annotated with a import('@volar/language-core').LanguageModule type but to take advantage of that annotation one would have to have volar installed in the project which IMO is not realistic thing to expect.
My thinking is that the the types (at least LanguageModule and related once) could be published separately so that one could add just the type package as a devDependency to the project.
I can't think of any other solution for that.
The text was updated successfully, but these errors were encountered:
"@volar/language-core" is almost a root dependency, and I think is fine to install it in "devDependency". It would be a maintenance issue if separate into an individual type package.
In #2267 there is an example of a plugin/module that one can create for Volar. It's annotated with a
import('@volar/language-core').LanguageModule
type but to take advantage of that annotation one would have to have volar installed in the project which IMO is not realistic thing to expect.My thinking is that the the types (at least
LanguageModule
and related once) could be published separately so that one could add just the type package as a devDependency to the project.I can't think of any other solution for that.
The text was updated successfully, but these errors were encountered: