Roadmap: TSLint -> ESLint

As you may have read in [this blog post](https://medium.com/palantir/tslint-in-2019-1a144c2317a9), we plan to deprecate TSLint in 2019 and support the migration to ESLint as the standard linter for both TypeScript & JavaScript. This will not be an immediate deprecation; on the contrary, there is a lot of work to do to ensure a smooth transition to the new tooling without any regressions. There are features, test suites, and conveniences in TSLint which we hope to retain in the migration. There may be a period of time when there is overlap between the two tools and TSLint early adopters are recommended to run _both_ linters to ensure full code check coverage (to a reasonable degree such that performance doesn't suffer drastically). I will be closing some feature requests in this repo which now feel out of scope because we expect them to be handled in the ESLint / [typescript-eslint](https://github.com/typescript-eslint/typescript-eslint) roadmap. One example of a category of rules for which __new feature requests__ are most likely to be closed / rejected is [formatting rules](https://github.com/palantir/tslint/labels/Formatting%20rule). I have suggested [splitting out these rules for quite some time](https://github.com/palantir/tslint/issues/3592) because we use Prettier at Palantir and consider it a better tool for the job of formatting code. TSLint will continue to release with important bug fixes and updates which keep it up-to-date with the latest compiler / language fea

Posted by adidahiya on Feb 23, 2019, 6:24 PM

Tags

• support (Software)

Related issues

• Add 65536 size support for maps
• TypeScript 7.1 Iteration Plan
• nvim-treeconfig: upstream nvim-treesitter
• Add the "action" and "method" attributes to <button>
• [FEATURE] Support multiple Connector accounts (same connector, different accounts) in Claude and Claude Code on the web (claude.ai/code)
• > We were imposed GitHub for so many exercises!