vetur version: 0.6.10
vscode version: 1.12.2
vetur initialized
[Error - 2:16:33 AM] Request textDocument/documentHighlight failed.
Message: Request textDocument/documentHighlight failed with message: Debug Failure. False expression:
Code: -32603
Same here:
[Error - 1:31:35 PM] Request textDocument/completion failed.
Message: Request textDocument/completion failed with message: Cannot read property 'parameters' of undefined
Code: -32603
[Error - 1:32:03 PM] Request textDocument/completion failed.
Message: Request textDocument/completion failed with message: Cannot read property 'parameters' of undefined
Code: -32603
This plugin is now very unstable.
@yinheli
DocumentHighlight is for highlighting areas related to the object under current cursor.

Is this feature working for you?
If not, when vetur is showing this error, which part (html/css/js) are you doing the highlighting on?
@octref
it works for stand html tags, but not working for custom components tag
versions:
OS: windows 10
VSCode: 1.12.2
vetur: 0.6.10
stand tags

custom component tag

documentHighlight failed error message does not appear in windows. I reported this issues while using macOS.
Thanks.
I'm on mac but I don't see any error messages...

But I can fix the highlight for custom compoennts.
@octref Thanks
It is ok now, maybe there is some conflict with other extension

double click, issue occurred

Nice - I get it reproduced. Will be able to resolve it soon.
Thanks a lot. This has been a bugging issue for a while.
I disabled highlight for js/ts now. Will re-enable it once the module resolution for importing vue files are resolved. But the change should be published soon so you won't be affected by this error.
Also need to do: Fix highlighting for html tags using custom elements.
@octref thanks ~ 馃憤
Is this still valid? I cannot reproduce and highlight seems to work fine.
@HerringtonDarkholme I don't think this applies anymore.
Others, open a new issue if you have this issue in latest.
Most helpful comment
Nice - I get it reproduced. Will be able to resolve it soon.
Thanks a lot. This has been a bugging issue for a while.