Related to #1738, but it works for TypeScript, not for JS. Could be an issue with VSCode, but not certain.
When using Vetur and a plugin for Vue that extends the Vue constructor, Vetur does not recognize the new options when using JS, but does recognize them when using TypeScript. Of course, default options (name, props, etc.) are correctly typed in both JS and TS.
I've used the vue-socket.io-extended library as an example, same as in #1738:
JS:
TS:
Reproducible Case
Open each of the following repos with vscode, and check the HelloWorld component:
Info
Problem
Related to #1738, but it works for TypeScript, not for JS. Could be an issue with VSCode, but not certain.
When using Vetur and a plugin for Vue that extends the Vue constructor, Vetur does not recognize the new options when using JS, but does recognize them when using TypeScript. Of course, default options (
name
,props
, etc.) are correctly typed in both JS and TS.I've used the
vue-socket.io-extended
library as an example, same as in #1738:JS:
TS:
Reproducible Case
Open each of the following repos with vscode, and check the HelloWorld component: