Replies: 4 comments 2 replies
-
shouldn't it be |
Beta Was this translation helpful? Give feedback.
-
@aladdin-add It's not working that way, I've already tried. Not sure how needs to be set the new configuration with typescript. It lacks explanation in the docs. |
Beta Was this translation helpful? Give feedback.
-
Yes, you haven't configured typescript-eslint correctly. You still need to specify We don't provide documentation for plugins like TypeScript. You should ask the typescript-eslint maintainers to update their docs: https://typescript-eslint.io/linting/configs |
Beta Was this translation helpful? Give feedback.
-
@nzakas Sorry my bad, I've tried various options and I was lastly for some reason remove the parser key. |
Beta Was this translation helpful? Give feedback.
-
Environment
Node version: v19.1.0
npm version: 8.19.3
Local ESLint version: v8.30.0
Operating System: Windows 11 WSL2
What parser are you using?
@typescript-eslint/parser
What did you do?
I have created new flat configuration, with
typescript
parser andtypescript
rules that overrides defaultseslint
recommended rules.On my project
eslint
was not working properly and was complaining mostly with un-def errors, for:Also, when I use the
typescript
plugin with short notation is not working, only works if I set the key as@typescript/eslint
:What did you expect to happen?
I expect
typescript
parser to parse properly.{ts, tsx}
files.What actually happened?
I'm getting errors as not recognizing the
typescript syntax
.Participation
Additional comments
some of the errors like, no extra-parens or not detecting that is
typescript
interface:Beta Was this translation helpful? Give feedback.
All reactions