You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm sure the problem is a parser problem. (If you are not sure, search for the issue in eslint-plugin-vue repo and open the issue in eslint-plugin-vue repo if there is no solution.
I have tried restarting my IDE and the issue persists.
I have updated to the latest version of the packages.
What version of ESLint are you using?
8.56.0
What version of eslint-plugin-vue and vue-eslint-parser are you using?
In reproduction, I use tsconfig.json and .eslintrc.cjs which were created by "npm init vue@latest".
<script setup lang="ts" generic="/** definition of data in FormContext */TDefinitionOfFormContextextendsRecord<string, unknown>,
/** Output of FormContext */TOutputOfFormContext,
/** Vee Validate Path of whole this component */TObjectArrayFieldPathextendsPath<TDefinitionOfFormContext>,
/** Row data type */TItemValueextendsItem<PathValue<TDefinitionOfFormContext, TObjectArrayFieldPath>>
">
// import and code
</script>
What did you expect to happen?
No error. For example, in .ts file multiline generic definition cause no error, which is indicated in this picture.
Before You File a Bug Report Please Confirm You Have Done The Following...
What version of ESLint are you using?
8.56.0
What version of
eslint-plugin-vue
andvue-eslint-parser
are you using?What did you do?
Configuration
In reproduction, I use tsconfig.json and .eslintrc.cjs which were created by "npm init vue@latest".
What did you expect to happen?
No error. For example, in .ts file multiline generic definition cause no error, which is indicated in this picture.

What actually happened?
Parsing error: ';' expected. eslint


Link to Minimal Reproducible Example
https://github.com/pronitsateli731/vue-parser-report-r60119
Actually happened:
Expect to Happen (TypeScript File)
Additional comments
No response
The text was updated successfully, but these errors were encountered: