-
Notifications
You must be signed in to change notification settings - Fork 888
no-unsafe-any
with tsx throwing error
#3080
Comments
Do you have |
yes npm ls @types/react
...
└── @types/react@15.6.0
no |
I have the same problem |
There is an issue with using this rule with JSX syntax. See [1]. [1]: palantir/tslint#3080 Change-Id: I5ec1df9fabd1fa5ba12c15c37ff685f4e5ec55f8
Can you try to repro this with the latest TSLint? We've had various refactorings occur since 5.5.0. |
It's still reproducible (in my case) |
The same problem |
This was fixed by #3699. 🎉 |
For anyone that finds this in the future. I was struggling with this for over an hour while configuring eslint. After adding the types with |
🤖 Beep boop! 👉 TSLint is deprecated 👈 and you should switch to typescript-eslint! 🤖 🔒 This issue is being locked to prevent further unnecessary discussions. Thank you! 👋 |
Hi! Can't understand why.
CLI:
tsconfig.json:
Bug Report
TypeScript code being linted
with
tslint.json
configuration:Actual behavior
Error
Expected behavior
No errors
The text was updated successfully, but these errors were encountered: