VueJs: intellisense on external components
Hi,
I would like to know if there is a way to have the same support for intellisense for local VueJs components also for external components imported from the node_modules folder.
Example: if I import a component (like vue-recaptcha) Rider does not suggests/list me the 2 properties 'sitekey' and 'load-recaptcha-script' but only the common ones (the same for all components).
If I create my own component in the SAME project it works very well.
I would like to know if there are requirements to get this feature: for some 'famous' external components it seems to work but I suppouse that this is done because the VueJs plugin 'incorporate' some extra info for them (is it so?).
It would be wonderfull if you could provide a guide to produce a well-formed distributable vuejs library component to satisfy all requirements for the best experience.
Thank you
Please sign in to leave a comment.
The IDE doesn't understand the way components are exposed in library files, thus the issue.
To improve code completion for different Vue.js component libraries, we are using a special format of metadata, called
web-types. web-types describe the library's components and their directives. The library developers have to provide descriptions of library components in theweb-typesformat and include it in package distribution to get all props correctly completed and resolved.Thank you for your answer! It's a lot that I have been searching for this info ... that is really not easy to find!
I have searched for the web-types actually implemented: https://www.npmjs.com/search?q=%40web-types ...there are 5 items.
Seems something that the world does not use...
I can't understand the point of this project...it has 12months with 1 developer and covers only 5 libraries.
Why should I adopt your standard?
It seems that Vetur is more and more adopted...Why don't you provide a plugin for Vetur definitions instead of creating a new standard?
Thank you so much again.. now I understand in witch hell I am now :P