-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After update from 0.4.0 to 0.5.0: no-unused-vars returns TypeError: Cannot use 'in' operator to search for 'type' in undefined #472
Comments
We temporarily closed this due to the lack of enough information. We could not identify whether it was a bug or a userland misconfiguration with the given info. |
I too am stil getting this error. This is the whole message:
|
If it helps, this is the same error: typescript-eslint/typescript-eslint#9719 |
Same here Reproduction steps:
|
So can this be reopened @antfu ? 🤔 |
Any updates on this? I"m getting the same error |
It's still relevant today. |
This seems to be an upstream issue with ts-eslint, yet there doesn't seem to be a valid minimal reproduction here or even in typescript-eslint/typescript-eslint#9719 If you do find a minimal reproduction, please open a new issue. |
Try updating your |
newest is 8.14.0, issue is still exist |
Same for me - just updated from 0.4.0 to 0.6.1. |
@vaynevayne @deim0707 I think I found the culprit:
When commenting out the parser line, the error disappears. I don't know why we had this in the config in the first place. If it helps... 👀 |
Any update on the issue ? |
Environment
Package
@nuxt/eslint
Reproduction
N/A
Describe the bug
After updating from 0.4.0 to 0.5.0: no-unused-vars returns
TypeError: Cannot use 'in' operator to search for 'type' in undefined.
Line 133 is always the first line after <script setup lang="ts">
Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: