Vue file. Intellisense shows outdated list of exported members

[undefinederror]

• I searched through existing issues.
• I have looked through docs at https://vuejs.github.io/vetur/

Info

• Platform: Win
• Vetur version: 0.9.3
• VSCode version: 1.14.2

Problem

Sorry if this was already brought up, but I can't seem to find this mentioned in other issues.

In a .vue file, VS Code intellisense fails to retrieve exported members that have been added after the language server has started. third doesn't show up in the list.

From a plain .js file intellisense shows all exported members

Other that obviously closing and reopening VS Code, I found that changing the lang attribute in the script tag does refresh the list of exported members, while closing and reopening the file has no effect.

This happens for both js/ts.

Happy to provide additional details if needed.

[HerringtonDarkholme]

Thanks for report. This is a known issue.

Vue language server, the underlying server that power vetur, implements file change depending solely on editors. We need to change file change via file watching.

[undefinederror]

Thank you for your reply. Yes I thought this must have indeed been a known issue.

Looking forward to the next versions of vetur (expecially TLint integration).I am very impressed by it. Absolutely great job!

[Frizi]

This issue seems very irritating now. I have to restart the editor very frequently or do hacks like changing lang="ts" to lang="tsx" and back every time I edit any ts or d.ts file.

I could help implementing a fix, but I would need some general guidance how to do it and where could it fit. This especially includes the general setup of plugin development. Done it before for atom, but vscode seems very different in that aspect.

[octref]

Need to think about how to do this, since the suggested file watching approach can be expensive on large projects.

[Frizi]

I tried to look around how is it currently tackled, just out of curiousity. Could you explain a bit how does the plugin manage to respond on *.vue file updates, or maybe how does the typescript language server manages to do the same with all ts/d.ts/js files?

[HerringtonDarkholme]

@Frizi https://github.com/vuejs/vetur/blob/master/server/src/modes/script/serviceHost.ts#L97-L120

And grepping updateCurrentTextDocument will tell you how vetur updates vue file script.

For tsserver, you can read the source code in TypeScript's repo.

Implementing file watching isn't that hard. But I don't have the confidence to spend that much man effort for it. Indeed, two full time TS core team members spend about several weeks to implement tsserver IIRC.

[HerringtonDarkholme]

Now watcher API is exposed in the venerable TS2.7

microsoft/TypeScript#20234

Let's do it!

Sadly, the watcher API is only for code transpilation. No Language Service is supported 😢
We still need to implement our own watcher.