-
-
Notifications
You must be signed in to change notification settings - Fork 43
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
How to migrate to the new eslint/typescript ? #61
Comments
Migration it's not hard, what I did was: 1 - Remove The resulting configuration should be 99% compatible to what you actually have I am not sure how the author @blakeembrey feels about this input, but I hope he can contribute towards the standard/ts-standard project |
@colthreepv Thanks, this is great! Would you like to contribute these instructions to the README? Edit: I can also deprecate this package with a link to the instructions once we add them. |
Hello, as an avid user of this ruleset, how can current users easily migrate to the new ESlint + Typescript parsing ?
For anyone not tracking JS world as their first news outlet:
TSlint is going to die in 2020, long live Typescript
REF: https://eslint.org/blog/2019/01/future-typescript-eslint
The text was updated successfully, but these errors were encountered: