The Future of eslint-plugin-typescript

[bradzacher]

What's Happened? (the TL;DR)

This repository is has been archived, and the package eslint-plugin-typescript has been deprecated.

We've moved the issues, code, and commit history to typescript-eslint, and renamed the package to @typescript-eslint/eslint-plugin.

Why?

As part of their 2019 H1 roadmap, the TypeScript team announced that they are focusing on ESLint as the linting tool for TS, and migrating away from TSLint. They are working on migrating the proper TypeScript repo to use ESLint.

Unfortunately we were a bit fragmented in the typescript eslint world - there was three separate projects used to enable TS linting and rules (eslint-plugin-typescript, typescript-parser-eslint, and typescript-estree). So we had a lot of issues in terms of syncing the packages and releases. Additionally it was hard for you, the user, to figure out where to log issues, which caused some maintenance headaches for everyone involved.

In order to better concentrate and organise our efforts, we have merged these projects into a monorepo over at typescript-eslint. We have already seen a huge increase in velocity from this merging, and only expect that to increase as we ramp up efforts.

As part of this as well, we have renamed the packages so into the @typescript-eslint scope on npm, so that we can get a fresh start from a versioning perspective.
This plugin has become @typescript-eslint/eslint-plugin (note that when you use the plugin, you'll only need to use "plugins": ["@typescript-eslint"],).

What do I have to do as a user/contributor?

1. Open any new issues and PRs on typescript-eslint.

   • We have automatically transferred all open issues from this repo to that one.

2. Keep an eye out for the release of the newly named package @typescript-eslint/eslint-plugin.

   • Hopefully sometime next week (week ending Sunday 27th Jan).