-
-
Notifications
You must be signed in to change notification settings - Fork 75
Crash on running ESLint #553
Comments
Thank you for this issue. However, we cannot guarantee that ESLint core rules work properly on TypeScript syntax because the rules don't know TypeScript syntax. It's the reason that I'd like to recommend to disable |
Disable no-unused-vars for ts e tsx files See eslint/typescript-eslint-parser#553
Disable no-unused-vars for ts e tsx files See eslint/typescript-eslint-parser#553
I tryed to use @mysticatea thank you for your fast reply and help! |
@mysticatea i was able to reproduce this by this code (tested on master branch) enum Foo {
BAR = 'bar'
} |
@armano2 In that case, I guess that |
@mysticatea not really issue is with missing parent on identifier function isForInRef(ref) {
let target = ref.identifier.parent; |
Oh. Interesting. |
@mysticatea damn i found whats wrong xdddddd in visitor-keys there is and should be |
Ahhh!! Thank you so much for found! |
do you want me do to PR with this? |
If you have time. |
ok pushed PR |
Ver21.0.1 of eslint-typescript-parser version has a bug that prevented it from linting typescript files correctly. eslint/typescript-eslint-parser#553 Update it to ver21.0.2 which contains a fix. Also update the version of build-config.
What version of TypeScript are you using?
3.1.6
What version of
typescript-eslint-parser
are you using?21.0.1
What code were you trying to parse?
See quadre-code/quadre#103
I cannot hunt down to specific code...
What did you expect to happen?
Eslint should pass.
What happened?
Some more info
At the moment I cannot update ESLint to version 5.*
To see the error on my project I run
grunt eslint --stack --debug
.Is it possible the crash is because I do not use eslint-plugin-typescript and its typescript/no-unused-vars rule? Nonetheless I would expect an ESLint error and not a crash.
The text was updated successfully, but these errors were encountered: