Migrate from TSLint to Typescript ESLint

TSLint will eventually be deprecated in favor of TypeScript ESLint. It thus makes sense to convert from using tslint.json to a customized .eslintrc.* file and switch to using eslint.

[StephenHaney]

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.

[david-szabo97]

Any update on this?