@typescript-eslint/typescript-estree
8.73.0 · 16 Nov 2026MIT224M / weekRepositoryHomepagenpmAtom feed
2.34.0 is the newest release of 2.x.
In short
6 breaking1 removed2 new2 fixed8 changed
- Breaking
Node 6 is no longer supported.
- Breaking
eslint-plugin: Removed hardcoded checks which prevented some rules from running on non-TypeScript files (i.e. files that are not
*.ts/*.tsx). - Breaking
eslint-plugin: Removed deprecated rule
prefer-interface. This rule was replaced byconsistent-type-definitions. - Breaking
eslint-plugin: Removed deprecated rule
no-triple-slash-reference. This rule was replaced bytriple-slash-reference - Breaking
eslint-plugin: Merged both
no-angle-bracket-type-assertionandno-object-literal-type-assertioninto one rule -consistent-type-assertions. - Breaking
eslint-plugin:
explicit-function-return-typeno longer treatsexport default () => {}as an expression for the purposes of theallowExpressionsoption. - Removed
eslint-plugin: remove deprecated rules
Release note
The section about @typescript-eslint/typescript-estree of a note shared by several packages.
Breaking changes
- Breaking
Node 6 is no longer supported.
Node 6 is now end of life. With the release of ESLint v6, they have dropped support for Node 6. As such, we have also dropped Node 6 from our testing pipeline. Please consider upgrading to a supported version of Node. See this page for more information about node version lifecycle and dates.
- Breaking
eslint-plugin: Removed hardcoded checks which prevented some rules from running on non-TypeScript files (i.e. files that are not
*.ts/*.tsx).Some users with mixed TS/JS codebases may now see some TypeScript-specific rules being reported against JS files.
Please use ESLint's
"overrides"config to select which files to apply rules to.
- Breaking
eslint-plugin: Removed deprecated rule
prefer-interface. This rule was replaced byconsistent-type-definitions. - Breaking
eslint-plugin: Removed deprecated rule
no-triple-slash-reference. This rule was replaced bytriple-slash-reference - Breaking
eslint-plugin: Merged both
no-angle-bracket-type-assertionandno-object-literal-type-assertioninto one rule -consistent-type-assertions. - Breaking
eslint-plugin:
explicit-function-return-typeno longer treatsexport default () => {}as an expression for the purposes of theallowExpressionsoption. - Breaking
eslint-plugin: Changed a number of the default rule configs:
explicit-function-return-type-allowTypedFunctionExpressionsandallowHigherOrderFunctionsare now bothtrueby default.no-inferrable-types-ignoreParametersandignorePropertiesare now bothfalseby default.no-this-alias-allowDestructuringis nowtrueby default.
- Breaking
eslint-plugin: Reworked the recommended configs:
plugin:@typescript-eslint/recommendedThis is our slim, recommended set of rules. This config does not require type information, so it can be easily dropped into an existing config.
plugin:@typescript-eslint/recommended-requiring-type-checkingThis is a slightly expanded set of rules, intended to be used in conjunction with
plugin:@typescript-eslint/recommended. These rules specifically require type information. We separated these rules into a separate config to ease adoption and to make the baserecommended"fast-by-default".
plugin:@typescript-eslint/eslint-recommendedThis config is a compatibility config that disables rules from
eslint:recommendedwhich are already handled by TypeScript.
This config simply turns on every single rule available in the plugin.
The intention is that you can use all the configs together, as they build upon one-another:
{ "extends": [ "eslint:recommended", "plugin:@typescript-eslint/eslint-recommended", "plugin:@typescript-eslint/recommended", "plugin:@typescript-eslint/recommended-requiring-type-checking" ] }
Bug Fixes
typescript-estree: fix
istoken typed asKeywordtypescript-estree: jsx comment parsing
Features
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.