Vetur: Plugin not recognized on version 0.19.0

[pdmshrestha]

• [x] I have searched through existing issues
• [x] I have read through docs
• [x] I have read FAQ

Info

• Platform: macOS
• Vetur version:0.19.0
• VS Code version:1.33.1

Problem

Suddenly after the plugin update plugins are not recognized on template.

This happens to custom plugin too.

[octref]

Repro case?

[pdmshrestha]

@octref As I said the error came right after the update. Earlier I didn't have any error. But the app complies without any issues. The plugin used in above earlier comment is https://kazupon.github.io/vue-i18n/started.html#javascript. Vetur doesn't recognize the plugin in template now. I have other vue plugins plugins which is not recognized in the template but compiles without any issues.

[pdmshrestha]

Also the template doesn't recognize the custom attribute (hyphen separated) on components. For example <v-container grid-list-md> (grid-list-md) is not recognized but <v-container gridListMd> is recognized.

And this happened after the plugin update.

[bennyty]

I'm seeing Vetur errors after updating to 0.19.0 as well.

Unrelated: This is doubly annoying because VSCode recently broke installing old versions of extensions. If anyone else needs to downgrade to [email protected] temporarily, consider running VSCode-Insiders.

[colinbes]

Also seeing similar errors as noted above with 0.19.0
I also get error message stating that due file is not a module File '/.../recipe-manager.client/src/App.vue' is not a module.. Adding lang="html" to template tag seems to have corrected the issue which should not be required.

Failing

<template>
<div>
  <label>{{title}}</label>
    <input-tag v-model="categoryList"></input-tag>
</div>
</template>

Passing

<template lang="html">
<div>
  <label>{{title}}</label>
    <input-tag v-model="categoryList"></input-tag>
</div>
</template>

[octref]

Same root cause as https://github.com/vuejs/vetur/issues/1226, vue-i18n doesn't have a way to bind more properties to this instance.

Your second issue should be fixed.

[octref]

@colinbes Can you create a new issue and not add to an unrelated issue? If you don't have any <script> region with export default {} that error will be reported.

[colinbes]

@octref I added it to this issue as I was seeing similar error messages and adding the lang to template remove the error messages. I will create new issue.

[octref]

I'll track it in #1226.