@typescript-eslint/scope-manager
8.73.0 · 16 Nov 2026MIT226.2M / weekRepositoryHomepagenpmAtom feed
347 stable releases, newest first, by release line. Notes are quoted as the maintainers published them.
- 4.x
4.22.1
4 May 2021Note: Version bump only for package @typescript-eslint/typescript-eslint
4.22.0
12 Apr 2021eslint-plugin: [no-unsafe-argument] handle tuple types on rest arguments
eslint-plugin: [prefer-regexp-exec] add autofix
4.21.0
5 Apr 2021eslint-plugin: [no-type-alias] consider
keyofas an aliaseslint-plugin: [no-unnecessary-type-assertion] correct bad fix for angle bracket assertion
eslint-plugin: [restrict-plus-operands] consider template literal types as strings
Bug Fixes
eslint-plugin: [no-type-alias] consider
keyofas an aliaseslint-plugin: [no-unnecessary-type-assertion] correct bad fix for angle bracket assertion
eslint-plugin: [restrict-plus-operands] consider template literal types as strings
eslint-plugin: [strict-boolean-expressions] account for truthy literals
eslint-plugin: always ignore assignments in no-unnecessary-type-assertion
Features
4.20.0
29 Mar 2021eslint-plugin: [space-infix-ops] support for class properties and type aliases
eslint-plugin: [type-annotation-spacing] handle space between ? and :
4.19.0
22 Mar 2021eslint-plugin: [member-delimiter-style] correct invalid fix for multiline with params on the same line
eslint-plugin: [promise-function-async] bad fixer with computed and literal methods
typescript-estree: [ts 4.2] add support for import type equal declaration
Bug Fixes
eslint-plugin: [member-delimiter-style] correct invalid fix for multiline with params on the same line
eslint-plugin: [promise-function-async] bad fixer with computed and literal methods
typescript-estree: [ts 4.2] add support for import type equal declaration
Features
4.17.0
8 Mar 2021eslint-plugin: [no-unnecessary-type-assertion] handle assignment
eslint-plugin: [strict-bool-expr] add fixes and suggestions
4.16.1
1 Mar 2021typescript-estree: update TS version range
4.16.0
1 Mar 2021eslint-plugin: [consistent-indexed-object-style] do not autofix if interface has extends
eslint-plugin: [no-implied-eval] handle conditional expression
eslint-plugin: [no-unused-vars] don't report nested module declaration
Bug Fixes
eslint-plugin: [consistent-indexed-object-style] do not autofix if interface has extends
eslint-plugin: [no-implied-eval] handle conditional expression
eslint-plugin: [no-unused-vars] don't report nested module declaration
eslint-plugin: [prefer-function-type] apply existing comments to the fixed code
eslint-plugin: [unbound-method] allow
superexpressions inthisassignmentsscope-manager: update libs for typescript 4.2
Features
TypeScript 4.2 syntax support
eslint-plugin: [member-delimiter-style] Add an option 'multilineDetection' to treat types and interfaces as single line if the last member ends on the same line as the closing bracket
eslint-plugin: [prom-func-async] report only function head
typescript-estree: throw custom error instead of plain object
4.15.2
22 Feb 2021typescript-estree: correct issues in AST definition
Add missing intrinsic keyword node to AST
eslint-plugin: [no-var-requires] report when used in type assertion
Bug Fixes
typescript-estree: correct issues in AST definition
Add missing intrinsic keyword node to AST
eslint-plugin: [no-var-requires] report when used in type assertion
Correct test names on windows for semantic-diagnostics-enabled
4.15.1
15 Feb 2021eslint-plugin: [explicit-module-boundary-types] check allowNames on function declarations and property methods
4.15.0
8 Feb 2021eslint-plugin: [no-extra-parens] handle ESLint 7.19.0
eslint-plugin: [prefer-function-type] correct fixer when signature ends with a semi
4.13.0
11 Jan 2021eslint-plugin: support eslint@5
eslint-plugin: [sort-type-union-intersection-members] add nullish group
4.12.0
4 Jan 2021eslint-plugin: [comma-spacing] handle empty type params
eslint-plugin: add rule
sort-type-union-intersection-members
4.11.1
28 Dec 2020eslint-plugin: [naming-convention] fix precedence of method and property meta selectors
4.11.0
21 Dec 2020eslint-plugin: [non-nullable-type-assertion-style] handle const assertion
eslint-plugin: [prom-func-async] add automatic fix
4.10.0
14 Dec 2020eslint-plugin: [naming-convention] fix wrong member of
methodandpropertymeta selectorseslint-plugin: add rule
non-nullable-type-assertion-style
4.9.1
7 Dec 20204.9.0
30 Nov 2020eslint-plugin: [consistent-indexed-object-style] convert readonly index signature to readonly record
eslint-plugin: [consistent-type-imports] crash when using both default and namespace in one import
eslint-plugin: [explicit-module-boundary-types] ignore functions exported within typed object/array literals
Bug Fixes
eslint-plugin: [consistent-indexed-object-style] convert readonly index signature to readonly record
eslint-plugin: [consistent-type-imports] crash when using both default and namespace in one import
eslint-plugin: [explicit-module-boundary-types] ignore functions exported within typed object/array literals
eslint-plugin: [no-use-before-define] allow class references if they're within a class decorator (#2827) (050023a), closes #2842
eslint-plugin: [triple-slash-reference] fix crash with external module reference
scope-manager: fix assertion assignments not being marked as write references (#2809) (fa68492), closes #2804
typescript-estree: add default value for
parserOptions.projectFolderIgnoreListand deduplicate resolved projects (#2819) (bf904ec), closes #2418 #2814
Features
eslint-plugin: [naming-convention] add
requireDouble,allowDouble,allowSingleOrDoubleoptions for underscoreseslint-plugin: [naming-convention] add
requiresQuotesmodifier (#2813) (6fc8409), closes #2761 #1483eslint-plugin: [naming-convention] add modifier
unusedeslint-plugin: [naming-convention] add modifiers
exported,global, anddestructured(#2808) (fb254a1), closes #2239 #2512 #2318 #2802eslint-plugin: [naming-convention] allow
destructuredmodifier forparameterselector (#2829) (525d2ff), closes #2828eslint-plugin: [naming-convention] split
propertyandmethodselectors into more granularclassXXX,objectLiteralXXX,typeXXX(#2807) (665b6d4), closes #1477 #2802eslint-plugin: [no-unused-vars] fork the base rule (#2768) (a8227a6), closes #2782 #2714 #2648
eslint-plugin: [unbound-method] add support for methods with a
this: voidparameter
4.8.2
23 Nov 2020eslint-plugin: [prefer-literal-enum-member] allow pure template literal strings
typescript-estree: fix type-only regression for consumers not yet on TS 4.1
4.8.1
17 Nov 2020eslint-plugin: [no-unnecessary-condition] false positive when array predicate returns unknown
typescript-estree: parseWithNodeMaps returning empty maps
4.8.0
16 Nov 2020eslint-plugin: [consistent-type-definitions] remove fixer when the interface is within a global module declaration
eslint-plugin: [no-unsafe-member-access] ignore MemberExpression's whose parents are either TSClassImplements or TSInterfaceHeritage
4.7.0
9 Nov 2020eslint-plugin: [array-type] parenthesize ReadonlyArray fix
eslint-plugin: [no-extra-non-null-assertion] false positive with non-nullable computed key
eslint-plugin: add rule
no-confusing-void-expression
4.6.1
2 Nov 2020eslint-plugin: [consistent-indexed-object-style] fix wrong autofix behaviour with generics
eslint-plugin: [no-shadow] ignore global module augmentation
4.6.0
26 Oct 2020eslint-plugin: [method-signature-style] correct fixer for overloads in an object literal type
eslint-plugin: [method-signature-style] don't auto-fix interfaces within namespaces
eslint-plugin: [prefer-string-starts-ends-with] Check negative indices in the second position for slice
Bug Fixes
eslint-plugin: [method-signature-style] correct fixer for overloads in an object literal type
eslint-plugin: [method-signature-style] don't auto-fix interfaces within namespaces
eslint-plugin: [prefer-string-starts-ends-with] Check negative indices in the second position for slice
Features
4.5.0
19 Oct 2020eslint-plugin: [array-type] fix issues with readonly option
eslint-plugin: [naming-convention] check bodyless function parameters
eslint-plugin: [no-invalid-this] allow "this" in class property definitions
Bug Fixes
eslint-plugin: [array-type] fix issues with readonly option
eslint-plugin: [naming-convention] check bodyless function parameters
eslint-plugin: [no-invalid-this] allow "this" in class property definitions
eslint-plugin: [no-misused-promises] False negative in LogicalExpression (#2682) (30a6951), closes #2544
eslint-plugin: [no-unnecessary-type-assertion] correct fixer for vue files
eslint-plugin: [return-await] do not auto-fix when type is
any/unknownparser: minor fix regexp, map-filter to reduce
Features
eslint-plugin: [dot-notation] add
allowProtectedClassPropertyAccessoptioneslint-plugin: [prefer-readonly-parameter-types] add
ignoreInferredTypesoptioneslint-plugin: [restrict-plus-operands] add intersection type determination logic
typescript-estree: add flag EXPERIMENTAL_useSourceOfProjectReferenceRedirect
4.4.1
12 Oct 2020eslint-plugin: [ban-ts-comment] support block comments
eslint-plugin: [ban-types] allow banning types with specific parameters
eslint-plugin: [consistent-type-assertions] check type assertion in jsx props
Bug Fixes
eslint-plugin: [ban-ts-comment] support block comments
eslint-plugin: [ban-types] allow banning types with specific parameters
eslint-plugin: [consistent-type-assertions] check type assertion in jsx props
eslint-plugin: [no-duplicate-imports] distinguish member, default
eslint-plugin: [no-throw-literal] false positive with logical expressions
eslint-plugin: [no-unused-vars] fix false positives for duplicated names in namespaces
eslint-plugin: [no-use-before-define] correctly handle typeof type references
scope-manager: don't create a variable for global augmentation
4.4.0
5 Oct 2020eslint-plugin: add
consistent-indexed-object-styleruleeslint-plugin: add extension rule
no-duplicate-imports
4.3.0
28 Sep 2020eslint-plugin: added safe getTypeOfPropertyOfType wrapper
experimental-utils: treat RuleTester arrays as readonly
eslint-plugin: [no-invalid-void-type] add option to allow
this: void
4.2.0
21 Sep 2020eslint-plugin: [naming-convention] ignore properties inside object patterns
eslint-plugin: [prefer-ts-expect-error] support block comments
scope-manager: correct analysis of inferred types in conditional types
Bug Fixes
eslint-plugin: [naming-convention] ignore properties inside object patterns
eslint-plugin: [prefer-ts-expect-error] support block comments
scope-manager: correct analysis of inferred types in conditional types
Features
eslint-plugin: add extension rule
comma-dangle
4.1.1
14 Sep 2020eslint-plugin: [naming-convention] allow an array of selectors with types and modifiers
eslint-plugin: [no-implied-eval] handle the
Functiontype
Bug Fixes
eslint-plugin: [naming-convention] allow an array of selectors with types and modifiers
eslint-plugin: [no-implied-eval] handle the
Functiontypeeslint-plugin: [no-unused-vars] better handling for declared modules (#2553) (02d72d4), closes #2523
eslint-plugin: [no-use-before-define] false positive for function type arguments (#2554) (189162d), closes #2527
eslint-plugin: [prefer-function-type] handle
thisreturneslint-plugin: [return-await] don't error for
in-try-catchif the return is in acatchwithout afinally
4.1.0
7 Sep 2020eslint-plugin: [explicit-module-boundary-types] cyclical reference infinite recursion crash
eslint-plugin: [no-unused-vars] correct detection of unused vars in a declared module with
export =eslint-plugin: [no-unused-vars] properly handle ambient declaration exports
Bug Fixes
eslint-plugin: [explicit-module-boundary-types] cyclical reference infinite recursion crash
eslint-plugin: [no-unused-vars] correct detection of unused vars in a declared module with
export =eslint-plugin: [no-unused-vars] properly handle ambient declaration exports
eslint-plugin: [no-use-before-define] false positive with jsx pragma reference (#2503) (5afeeab), closes #2502
eslint-plugin: [typedef] false positive for rest parameter with array destructuring
eslint-plugin: handle missing message IDs in eslint v5/v6
scope-manager: add
constas a global type variablescope-manager: correctly handle inferred types in nested type scopes
scope-manager: don't create references for intrinsic JSX elements
scope-manager: fallback to lib 'esnext' or 'es5' when ecma version is unsupported
scope-manager: support rest function type parameters (#2491) (9d8b4c4), closes #2449
scope-manager: support tagged template string generic type parameters
scope-manager: support type predicates (#2493) (a40f54c), closes #2462
scope-manager: treat type imports as both values and types (#2494) (916e95a), closes #2453
Features
4.0.0
31 Aug 2020- Breaking
Support new ESTree optional chaining representation
- Breaking
Consume new scope analysis package
- Breaking
eslint-plugin: [ban-ts-comment] change default for
ts-expect-errortoallow-with-description
This release comes just a few months after the v3 release due to the much faster than expected turnaround on optional chaining by ESTree. Read on for more details!
Summary of Changes
Breaking
- Breaking
Support new ESTree optional chaining representation
- Breaking
Consume new scope analysis package
- Breaking
eslint-plugin: [ban-ts-comment] change default for
ts-expect-errortoallow-with-description - Breaking
eslint-plugin: [typedef] remove all default options
- Breaking
Correct decorator traversal for AssignmentPattern
- Breaking
eslint-plugin: [no-unnecessary-condition][strict-boolean-expressions] add option to make the rules error on files without
strictNullChecksturned on - Breaking
typescript-estree: Switch to globby
Non-Breaking
- Breaking
eslint-plugin: Add
consistent-type-importsrule - Breaking
Add
downlevel-dtsto all packages with type declarations - Breaking
eslint-plugin: Add extension rule
@typescript-eslint/no-redeclare - Breaking
eslint-plugin: Add extension rule
@typescript-eslint/no-shadow
Breaking Changes
AST Changes
Support official ESTree optional chaining syntax (#2204)
When TS 3.7 released with optional chaining in November 2019, the feature was still a Stage-3 TC39 spec. This meant that ESTree[1] did not yet have an official AST representation defined, as they only officially support Stage-4 specs.
This meant that we either had to block on TS 3.7 support, unofficially support optional chaining, or find an interim representation to use. As we had no clear timeframe around which both optional chaining would move to Stage-4, and when the ESTree AST for it would be defined, we decided the first two options were sub-optimal, and instead chose to the existing
babel-eslintAST representation. This representation has been in the ecosystem for a while and was supported by a variety of plugins.Recently, ESTree agreed upon and merged an AST for optional chaining, which is vastly different to
babel-eslint's representation. ESLint and their parserespreehave already implemented and released support for this new AST as of ESLintv7.5.0.In order to correct course to match the future of the ecosystem, we've update our AST to match the new, official representation.
This means a few things right now:
- Breaking
The ESLint core rules will have complete support for optional chaining, without need for extension rules :tada:
you will need to upgrade to at least ESLint 7.5.0 in order to have support in lint rules
- Breaking
Users might have to wait for plugins outside this project to update their logic to support this new AST.
Going forward, we're trying to be a bit more conservative with our choice of AST representation to help prevent this migration pain, at the cost of not being able to write lint rules for new features.
[1] ESTree is the AST representation used in the ESLint ecosystem (amongst other things). It's collectively governed by a number of projects. github.com/estree/estree/
Remove
decoratorsfrom nodes that TS doesn't support decorators on (#2375)Previously, our parser would parse decorators and include them in the AST for
FunctionDeclarations,EnumDeclarations andInterfaceDeclarations. This was originally done because the TypeScript parser treats these as syntactically valid for various reasons (the TS parser is incredibly permissive in what it allows!).However, it's semantically invalid to have decorators for these nodes, and TypeScript will throw a semantic compile-time error. Whilst you can ignore this error with an ignore comment, TypeScript will ignore the decorator completely in the compiled output.
Additionally, babel's TypeScript parser will throw a parser error in these cases.
With this version, the parser will no longer include the
decoratorsproperty for the mentioned nodes.
Note that the parser will not error - it will just silently ignore the invalid decorators.AST_NODE_TYPES.Importremoved (#2375)This was a cleanup item that was missed in the 3.0.0 release (#1950).
The underlying type was removed back then, so it's unlikely that anyone was still using this member.TypeScript Scope Analysis (#2039)
You can read the full backstory behind this change in #1856.
In a nutshell, Scope Analysis is what enables ESLint to find and track variables as it traverses the AST. This information is consumed by rules like
no-unused-vars,no-undef,no-shadow,no-redeclare, andno-use-before-define.With this release, we've forked ESLint's
eslint-scopepackage, and rebuilt it from the ground up to support TypeScript's functionality and dual-scope system.This should mean that rules that rely upon scope analysis should all work properly, with no more false positives!
This has been marked as a breaking change for the following reasons:
- Breaking
There may be some config changes required for existing rules,
- Breaking
there are some new extension rules that have been added to better support TS that users will need to switch to:
- Breaking
There will be
eslint-disablecomments that are now unnecessary, and may block your CI if you use ESLint's--report-unused-disable-directivesCLI option, - Breaking
There will likely be a number of new lint errors as affected rules will now functioning correctly,
- Breaking
Some users may need to configure the new
parserOptions.liboption to ensure the global types are correctly defined for rules likeno-undef. - Breaking
Some rules outside this project may have been implicitly relying upon the scope analyser not understanding TS types - meaning they may need some adjustments.
Improve
parserOptions.projectglob resolution performance (#2418)For configuration simplicity, we allow you to specify globs to
parserOptions.project.Some users provide globs like
./**/tsconfig.json. This sort of glob will matchnode_modulesand anytsconfigs located in there (many packages do not maintain proper exclusion lists when publishing, so they publish unnecessary files like that). This is a problem for two reasons:It will cause us to find and parse additional, useless
tsconfigs.It will cause the glob handler to waste time traversing
node_modules.
The first issue we fixed a while ago with the
parserOptions.projectFolderIgnoreListoption, which defaulted to ignorenode_modules. At the time due to some weirdness with theglobpackage, we implemented a manual filter after the globs were resolved.We never really thought about the second issue. However in some cases (when there are a large number of dependencies in
node_modules... so in most cases!) this can cause a significant performance impact.On a medium-large node_modules folder, it can take ~3-1000ms to scan the directory. For correctness and safety reasons we have to do this scan every time ESLint asks us to parse a file, which obviously adds up over a lint run.
To fix this, we've changed the underlying package we use for glob resolution. This should change the total time we spend parsing globs during a lint run from
O(n)(wherenis the number of files in the workspace) to more or lessO(1). For more information you can see the PR.The breaking change that comes with this is as follows:
PreviouslyparserOptions.projectFolderIgnoreListaccepted an array ofRegExpobjects or regex strings.
Now it only accepts an array of strings, which must be glob strings. You'll have to translate your regexes to globs for them to continue working.Rule Changes
ban-ts-comment- change default forts-expect-errortoallow-with-description(#2351)ts-expect-errorwas added in TS 3.9. It's likets-ignore, but it's slightly less dangerous because if it suppresses no errors, then the comment itself becomes a compiler error.Whilst completely banning the comment is "best practice", in real world use cases, you might have some valid cases that requires the comment.
Previously this would require code like the following:
// some comment describing why it's disabled // eslint-disable-next-line @typescript-eslint/ban-ts-comment // ts-expect-error const x = 1 as string;
The problem is that there's no way to enforce that there is a description detailing why the suppression comment is required.
With the new default the following is considered valid code:
// ts-expect-error: some comment describing why it's disabled const x = 1 as string;
This change makes the rule a little more flexible for real-world scenarios by banning most cases, and enforcing best practice of documenting suppressions when they're required.
typedef- remove all rule defaults (#2352)For a long time we have discouraged using the
typedefrule. The rule exists for essentially one purpose: gradually migrating a weakly typed codebase to be stricter with the goal of enabling thenoImplicitAnyandstrictPropertyInitializationcompiler options.Outside of that use-case, this rule can be harmful to your codebase: explicitly annotating every single thing is known to cause performance issues with TypeScript, and maintaining all of those annotations can be a large maintenance burden.
This rule also often causes conflicts with other rules like
no-inferrable-types, which causes headaches for some setups.We have removed all defaults from the rule to force users to explicitly "opt-in" to all functionality.
no-unnecessary-conditionandstrict-boolean-expressions- report an error ifstrictNullChecksis not turned on (#2345)Both of these rules are driven off of inspecting nullability. Because of this, both rules will not work correctly if your project does not use the
strictNullCheckscompiler option.Without
strictNullChecks, TypeScript essentially erasesundefinedandnullfrom the types. This means when this rule inspects the types from a variable, it will not be able to tell that the variable might benullorundefined, which essentially makes this rule a lot less useful.If for some reason you cannot turn on
strictNullChecks, but still want to use one of these rules - you can use the newallowRuleToRunWithoutStrictNullChecksIKnowWhatIAmDoingoption to allow it.Note that the behavior of this rule is undefined with the compiler option turned off. We will not accept bug reports if you are using this option.
Non-Breaking Changes
New Rules
consistent-type-imports(#2367)TypeScript 3.8 introduced type-only imports. This is an important feature for transpilers (like babel), as it allows them to very easily determine when an import/export can be excluded from the output code.
With the new scope analyser we've introduced in this version, we've enable a number of powerful abilities that were previously difficult or impossible for us to do.
This rule is an example of a use-case that was previously nearly impossible to do that is now relatively simple. This rule can help you ensure that any imports that are only used in type locations are properly declared as a type-only import.
It also includes a powerful fixer to help automatically separate your imports for you.
Add
downlevel-dtsto all packages with type declarations (a257183)This is a minor change to ensure that our type declarations remain backwards compatible with older versions as we start to leverage new TS features.
We were already using
downlevel-dtsin a few packages, this just increases the coverage to 100%.- 3.x
3.10.0
24 Aug 2020eslint-plugin: [explicit-module-boundary-types] ignore abstract setters
eslint-plugin: [explicit-module-boundary-types] ignore all bodyless setters
eslint-plugin: [no-unnecessary-condition] better handling for unary negation
Bug Fixes
eslint-plugin: [explicit-module-boundary-types] ignore abstract setters
eslint-plugin: [explicit-module-boundary-types] ignore all bodyless setters
eslint-plugin: [no-unnecessary-condition] better handling for unary negation
typescript-estree: ts.NamedTupleMember workaround for <TS4.0
Features
eslint-plugin: add
no-implicit-any-catchruletypescript-estree: update allowed TS version range
3.9.1
17 Aug 2020eslint-plugin: [no-unnecessary-condition] fix false positive with nullish coalescing
eslint-plugin: [prefer-includes] don't auto fix when
testmethod's argument type doesn't have an 'includes' method
3.9.0
10 Aug 2020eslint-plugin: [no-throw-literal] support type assertions
eslint-plugin: [no-unsafe-assignment/return] allow assigning any => unknown
typescript-estree: support TSv4 labelled tuple members
3.8.0
3 Aug 2020eslint-plugin: [no-implied-eval] don't report when
Functionis importedeslint-plugin: [no-unsafe-assignment] fix typo in message
eslint-plugin: [naming-convention] allow specifying an array of selectors
Bug Fixes
eslint-plugin: [no-implied-eval] don't report when
Functionis importedeslint-plugin: [no-unsafe-assignment] fix typo in message
Features
eslint-plugin: [naming-convention] allow specifying an array of selectors
eslint-plugin: add
prefer-enum-initializersrule
3.7.1
27 Jul 2020eslint-plugin: [adjacent-overload-signatures] fix false positive on call signatures and a method named
calleslint-plugin: [no-extra-parens] stop reporting on calling generic functions with one argument and type parameters containing parentheses
typescript-estree: correct AST regression introduced by TS4.0 upgrade
3.7.0
20 Jul 2020eslint-plugin: [naming-convention] allow selecting only
constvariableseslint-plugin: [no-empty-function] add
decoratedFunctionsoptiontypescript-estree: support short-circuiting assignment operators
Features
eslint-plugin: [naming-convention] allow selecting only
constvariableseslint-plugin: [no-empty-function] add
decoratedFunctionsoptiontypescript-estree: support short-circuiting assignment operators
typescript-estree: support type annotations on catch clauses
3.6.1
13 Jul 2020eslint-plugin: [no-unnecessary-condition] handle computed member access
eslint-plugin: [prefer-literal-enum-member] allow negative numbers
Bug Fixes
eslint-plugin: [no-unnecessary-condition] handle computed member access
eslint-plugin: [prefer-literal-enum-member] allow negative numbers
eslint-plugin: [space-before-function-paren] incorrect handling of abstract methods (#2275) (ced6591), closes #2274
eslint-plugin: [switch-exhaustiveness-check] handle special characters in enum keys
3.6.0
6 Jul 2020eslint-plugin: [no-namespace] allow namespaces in nested declarations with
allowDeclarationseslint-plugin: [space-before-function-paren] handle abstract functions
eslint-plugin: add rule
prefer-literal-enum-member
3.5.0
29 Jun 2020eslint-plugin: [naming-convention] support unicode in regex
typescript-estree: forward compatibility for new compound assignment operators
Add package scope-manager
Bug Fixes
eslint-plugin: [naming-convention] support unicode in regex
typescript-estree: forward compatibility for new compound assignment operators
Features
Add package scope-manager
Split types into their own package
Split visitor keys into their own package
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.