Vetur fail to start. Output: https://justpaste.it/6n1ik
@ondrej-janosik Thanks for reporting this issue. Could you provide minimal reproduction which generate this error by cloning and editing https://github.com/octref/veturpack?
Unfortunately, I can not. We found this bug in one pretty big project that I can not share with you. Can you help me where to look? I can send you just the broken .vue file. But I dont know how to find that one.
No worries. I just figured out the cause.
If we have an arrow function in some v-on value, this error happens.
<template>
<button @click="() => test = 123">click</button>
</template>
This started happening in my project as of yesterday. I stopped getting syntax highlighting for the script and style sections of one of my vue files. I lose all language support for the rest of my vue files too, syntax highlighting seems to be intact in all other vue files though.
Edit: removing all arrow functions from the template stopped the language server from crashing but the syntax highlighting is still broken. I also get a strange error when trying to use format strings within the template. "Cannot find name 'temthis'." for each instance. Note: I just removed and reinstalled vetur which is when this started happening.

@dombavetta Syntax highlighting issue is probably a separated problem. Could you create a new issue for that with reproduction?
Made a PR #1228
@ktsn Yeah I figured, I actually was just looking through the issues for users experiencing something similar and it appears theres already an issue created. I will try and get a reproducible project up but no promises, this comes from a very large project at work so I will try to strip out what I can and see if the issue is still present.
@dombavetta Thank you for your help!
@dombavetta
"Cannot find name 'temthis'."
Oh, I missed this problem. This would be also individual problem. It would be appreciated if you create an issue for that also 馃檹
Thanks for such a quick help! You were right. When I delete all arrow functions in v-on, VETUR works as expected
Most helpful comment
No worries. I just figured out the cause.
If we have an arrow function in some
v-onvalue, this error happens.