noUnusedLocals reporting warnings for properties used in <template>

• I have searched through existing issues
• I have read through docs
• I have read FAQ

Info

• Platform: macOS
• Vetur version: 0.19.2
• VS Code version: 1.33.1 (1.33.1)

Problem

With noUnusedLocals on, Vetur is report “declared but never read” errors for properties used in the <template> in single file components. See how msg is used in line 3 in the screenshot below:

Reproducible Case

https://github.com/jwhitmarsh/vetur-no-unused-locals

[octref]

Let’s keep it open since template part should ideally be considered the same file as the SFC. Now we have a temporary workaround https://github.com/vuejs/vetur/pull/1243 but that’s not a good long-term solution.

[jwhitmarsh]

Ah I didn’t realise it was the private keyword that was causing the issue. Just FYI the screenshot above (and the example repo) is what is generated by the Vue CLI (if you chose the TypeScript settings), which is why I didn’t think to change the private keyword.

I’ll mark this as closed, but I wonder if there’s a good place to document this as I imagine it’ll affect anyone creating a new app with Vue CLI running Vetur. To add to that, the reason I turned on noUnusedLocals was following the advice in #1063 so this might come up more as people move to a TS version that supports the flag.

Thanks all for your help.