Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Migrate from TSLint to Typescript ESLint #302
While it makes sense to switch to
I think targeting this migration to a
LMK if my impression is incorrect and if majority of the TypeScript ecosystem has already moved over to using eslint.
I've been converting a project that uses gts rules to eslint if anyone wants some inspiration.
https://github.com/PolymerLabs/arcs/blob/master/config/eslintrc.json is the beginning. Also interested in working with anyone that wants to help push this forward.
Just chipping in some perspective: we're considering moving back to TSLint until the typescript-eslint repo matures.
Since migrating to ESLint, we've had A LOT of problems with extremely bad performance and poor TypeScript support with the vscode-eslint extension; it often crashes, gives odd errors, or hangs at 99% CPU (although this appears to be recently remedied).
Since moving to ESLint for TS, we're spending way too much time talking about debugging our linter.
I'm not saying don't do it – there are lots of talented people working hard on typescript-eslint; I have no doubt it will soon become the clear choice.
I'd suggest that you consider waiting until TSLint is actually deprecated if you're happy with how things work now. I'm not sure the VSCode extension support is there yet for ESLint... and make sure to test the change well and weigh the trade-offs of leaving a more mature setup.