-
-
Notifications
You must be signed in to change notification settings - Fork 245
Support for Volar (AKA Vue Language Tools) in VS Code, vue-tsc, etc #1075
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
Comments
There's a community package that I believe adds all the correct types, see https://www.npmjs.com/package/@nativescript-dom/vue-types |
Neat. Those are manually typed, but I guess it's up to NativeScript to supply builtin types at some point. Maybe this is something to add to the templates and/or docs? It's kind of jarring generating a new project and having no types for stuff. |
@segevfiner I think the same, I think this should be in the templates |
@rigor789 That package does not work for me |
I had this working, was going comment the solution, but now its gone. Definietly possible if you have right maybe you also need |
Use tsserver (typescript-language-server) with Due to volar version mismatch to Somehow, upgrading to Before i was able to make it work both in vscode setup and neovim. now, its just neovim (probably because of different configuration) |
Uh oh!
There was an error while loading. Please reload this page.
It seems types are currently missing for NativeScript components

This is also was is used by
vue-tsc
to type check a project. It would be nice if those types are registered. This might require a transform of the NativeScript type to something that Volar/Vue Language Tools can understand, a "fake" Vue component type, a web component like type, or something else, or maybe teaching Vue Language Tools to recognize NativeScript component types directly.Without this you can't type check the project properly and you get no completions in the IDE for the NativeScript components.
The text was updated successfully, but these errors were encountered: