Josh, I see that back in June, you reiterated that you wanted a core TSESLint member to work on this. However, in the meantime, TSESLint 8 was released, and eslint-plugin-deprecation is no longer compatible, so the need to have this rule working is much greater nowadays. (i.e. people are blocked from upgrading or have to chose to drop deprecation linting altogether)

In order to try and help, I implemented a short and sweet version of the rule, coming in at only 63 lines:
Zamiell@4c44df0

My short version probably doesn't cover as many cases as the 298 line version created by luca-script, but it might be easier to maintain. Ultimately, I would just like some version the rule to exist in TSESLint sooner than later. Any thoughts?

Yeah this is really painful 😬 I've had to disable the rule in my own projects and know a lot of other folks have had to choose between sticking with typescript-eslint 7 / ESLint 8 or losing the rule too, as you're saying.

Edit: or, as @ST-DDT notes, using @eslint/compat.

I actually started prototyping a reimplementation of the rule myself last week, but haven't had the time to get it to completion. The v8 release and other ESLint v9 compatibility work did a number on our schedules. #9783 has the work so far. It's on my todolist for this week to try to clean it up and get it in review.

Yeah this is really painful 😬 I've had to disable the rule in my own projects and know a lot of other folks have had to choose between sticking with typescript-eslint 7 / ESLint 8 or losing the rule too, as you're saying.

You can enable the rule using the eslint compatibility package.

https://github.com/faker-js/faker/blob/bb1a73ca3a0ac3b3cf7a0ec25740bf6e872887ae/eslint.config.js#L138

import { fixupPluginRules } from '@eslint/compat';
import eslintPluginDeprecation from 'eslint-plugin-deprecation';

...

  {
    plugins: {
      deprecation:
        // https://github.com/gund/eslint-plugin-deprecation/issues/78
        // @ts-expect-error: Types aren't matching, but it works
        fixupPluginRules(eslintPluginDeprecation),
    },
    rules: {
      'deprecation/deprecation': 'error',
    },
  },

I would prefer a solution that works out of the box though.

@JoshuaKGoldberg thanks for @typescript-eslint/no-deprecated in typescript-eslint@8.3.0, just migrated from eslint-plugin-deprecation and we've observed it working 👍

Feels quite a bit slower than eslint-plugin-deprecation in the first runs, but maybe that's a temporary problem.

I'm a bit late to the party, but would it be possible to add an option to differentiate between libraries and user code? I find it very useful to flag and address deprecated APIs during the dependency upgrade cycle, but if it flags deprecated APIs from my own code base the moment I annotate them as such, I'd effectively need to go ahead and remove the API entirely. Should I open a feature request for this?

@BurningEnlightenment Yes, please open a new issue for a feature request.

As per our contributing guidelines please open new issues for feature requests or bug reports. Or if you'd like to chat with us please visit our discord.

https://typescript-eslint.io/contributing/issues