xo 0.50.0 → 0.51.0

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/comma-dangle.md

@@ -9,7 +9,7 @@ It adds support for TypeScript syntax.
 
 See the [ESLint documentation](https://eslint.org/docs/rules/comma-dangle) for more details on the `comma-dangle` rule.
 
-## Rule Changes
+## How to Use
 
 ```jsonc
 {

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/consistent-generic-constructors.md

@@ -0,0 +1,82 @@
+# `consistent-generic-constructors`
+
+Enforces specifying generic type arguments on type annotation or constructor name of a constructor call.
+
+When constructing a generic class, you can specify the type arguments on either the left-hand side (as a type annotation) or the right-hand side (as part of the constructor call):
+
+```ts
+// Left-hand side
+const map: Map<string, number> = new Map();
+
+// Right-hand side
+const map = new Map<string, number>();
+```
+
+This rule ensures that type arguments appear consistently on one side of the declaration.
+
+## Options
+
+```jsonc
+{
+  "rules": {
+    "@typescript-eslint/consistent-generic-constructors": [
+      "error",
+      "constructor"
+    ]
+  }
+}
+```
+
+This rule takes a string option:
+
+- If it's set to `constructor` (default), type arguments that **only** appear on the type annotation are disallowed.
+- If it's set to `type-annotation`, type arguments that **only** appear on the constructor are disallowed.
+
+## Rule Details
+
+The rule never reports when there are type parameters on both sides, or neither sides of the declaration. It also doesn't report if the names of the type annotation and the constructor don't match.
+
+### `constructor`
+
+<!--tabs-->
+
+#### ❌ Incorrect
+
+```ts
+const map: Map<string, number> = new Map();
+const set: Set<string> = new Set();
+```
+
+#### ✅ Correct
+
+```ts
+const map = new Map<string, number>();
+const map: Map<string, number> = new MyMap();
+const set = new Set<string>();
+const set = new Set();
+const set: Set<string> = new Set<string>();
+```
+
+### `type-annotation`
+
+<!--tabs-->
+
+#### ❌ Incorrect
+
+```ts
+const map = new Map<string, number>();
+const set = new Set<string>();
+```
+
+#### ✅ Correct
+
+```ts
+const map: Map<string, number> = new Map();
+const set: Set<string> = new Set();
+const set = new Set();
+const set: Set<string> = new Set<string>();
+```
+
+## When Not To Use It
+
+You can turn this rule off if you don't want to enforce one kind of generic constructor style over the other.

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/consistent-type-assertions.md

@@ -111,8 +111,3 @@ const foo = <Foo props={{ ... } as Bar}/>;
 ## When Not To Use It
 
 If you do not want to enforce consistent type assertions.
-
-## Related To
-
-- TSLint: [no-angle-bracket-type-assertion](https://palantir.github.io/tslint/rules/no-angle-bracket-type-assertion/)
-- TSLint: [no-object-literal-type-assertion](https://palantir.github.io/tslint/rules/no-object-literal-type-assertion/)

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/consistent-type-definitions.md

@@ -80,7 +80,3 @@ type T = { x: number };
 ## When Not To Use It
 
 If you specifically want to use an interface or type literal for stylistic reasons, you can disable this rule.
-
-## Related To
-
-- TSLint: [interface-over-type-literal](https://palantir.github.io/tslint/rules/interface-over-type-literal/)

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/explicit-member-accessibility.md

@@ -344,7 +344,3 @@ If you think defaulting to public is a good default, then you should consider us
 ## Further Reading
 
 - TypeScript [Accessibility Modifiers](https://www.typescriptlang.org/docs/handbook/classes.html#public-private-and-protected-modifiers)
-
-## Related To
-
-- TSLint: [member-access](http://palantir.github.io/tslint/rules/member-access/)

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/explicit-module-boundary-types.md

@@ -158,10 +158,9 @@ Examples of code for this rule with `{ allowDirectConstAssertionInArrowFunctions
 
 ```ts
 export const func = (value: number) => ({ type: 'X', value });
-export const foo = () =>
-  ({
-    bar: true,
-  } as const);
+export const foo = () => ({
+  bar: true,
+});
 export const bar = () => 1;
 ```
 

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/member-ordering.md

@@ -1159,7 +1159,3 @@ It is also possible to group different member types at the same rank.
 ## When Not To Use It
 
 If you don't care about the general order of your members, then you will not need this rule.
-
-## Related To
-
-- TSLint: [member-ordering](https://palantir.github.io/tslint/rules/member-ordering/)

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-confusing-void-expression.md

@@ -147,7 +147,3 @@ console.log(void alert('Hello, world!'));
 The return type of a function can be inspected by going to its definition or hovering over it in an IDE.
 If you don't care about being explicit about the void type in actual code then don't use this rule.
 Also, if you prefer concise coding style then also don't use it.
-
-## Related To
-
-- TSLint: ['no-void-expression'](https://palantir.github.io/tslint/rules/no-void-expression/)

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-dynamic-delete.md

@@ -60,7 +60,3 @@ Some environments such as older browsers might not support `Map` and `Set`.
 
 Do not consider this rule as performance advice before profiling your code's bottlenecks.
 Even repeated minor performance slowdowns likely do not significantly affect your application's general perceived speed.
-
-## Related To
-
-- TSLint: [no-dynamic-delete](https://palantir.github.io/tslint/rules/no-dynamic-delete)

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-empty-interface.md

@@ -64,7 +64,3 @@ This rule accepts a single object option with the following default configuratio
 ## When Not To Use It
 
 If you don't care about having empty/meaningless interfaces, then you will not need this rule.
-
-## Related To
-
-- TSLint: [no-empty-interface](https://palantir.github.io/tslint/rules/no-empty-interface/)

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-explicit-any.md

@@ -179,7 +179,3 @@ and you want to be able to specify `any`.
 ## Further Reading
 
 - TypeScript [any type](https://www.typescriptlang.org/docs/handbook/basic-types.html#any)
-
-## Related To
-
-- TSLint: [no-any](https://palantir.github.io/tslint/rules/no-any/)

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-extraneous-class.md

@@ -312,7 +312,3 @@ class Constants {
 ## When Not To Use It
 
 You can disable this rule if you are unable -or unwilling- to switch off using classes as namespaces.
-
-## Related To
-
-[`no-unnecessary-class`](https://palantir.github.io/tslint/rules/no-unnecessary-class/) from TSLint

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-floating-promises.md

@@ -118,4 +118,3 @@ If you do not use Promise-like values in your codebase, or want to allow them to
 ## Related To
 
 - [`no-misused-promises`](./no-misused-promises.md)
-- TSLint: ['no-floating-promises'](https://palantir.github.io/tslint/rules/no-floating-promises/)

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-for-in-array.md

@@ -6,8 +6,6 @@ This rule prohibits iterating over an array with a for-in loop.
 
 ## Rule Details
 
-Rationale from TSLint:
-
 A for-in loop (`for (var k in o)`) iterates over the properties of an Object.
 While it is legal to use for-in loops with array types, it is not common.
 for-in will iterate over the indices of the array as strings, omitting any "holes" in
@@ -57,7 +55,3 @@ This rule is not configurable.
 ## When Not To Use It
 
 If you want to iterate through a loop using the indices in an array as strings, you can turn off this rule.
-
-## Related To
-
-- TSLint: ['no-for-in-array'](https://palantir.github.io/tslint/rules/no-for-in-array/)

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-inferrable-types.md

@@ -148,7 +148,3 @@ If you do not want to enforce inferred types.
 ## Further Reading
 
 TypeScript [Inference](https://www.typescriptlang.org/docs/handbook/type-inference.html)
-
-## Related To
-
-TSLint: [no-inferrable-types](https://palantir.github.io/tslint/rules/no-inferrable-types/)

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-invalid-void-type.md

@@ -126,7 +126,3 @@ class Example {
 
 If you don't care about if `void` is used with other types,
 or in invalid places, then you don't need this rule.
-
-## Related To
-
-- TSLint: [invalid-void](https://palantir.github.io/tslint/rules/invalid-void/)

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-misused-new.md

@@ -46,7 +46,3 @@ interface I {
 ```
 
 This rule is not configurable.
-
-## Related To
-
-- TSLint: [no-misused-new](https://palantir.github.io/tslint/rules/no-misused-new/)

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-namespace.md

@@ -131,7 +131,3 @@ If you are using the ES2015 module syntax, then you will not need this rule.
 - [Modules](https://www.typescriptlang.org/docs/handbook/modules.html)
 - [Namespaces](https://www.typescriptlang.org/docs/handbook/namespaces.html)
 - [Namespaces and Modules](https://www.typescriptlang.org/docs/handbook/namespaces-and-modules.html)
-
-## Related To
-
-- TSLint: [no-namespace](https://palantir.github.io/tslint/rules/no-namespace/)

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-non-null-assertion.md

@@ -48,7 +48,3 @@ This rule is not configurable.
 ## When Not To Use It
 
 If you don't care about strict null-checking, then you will not need this rule.
-
-## Further Reading
-
-- [`no-non-null-assertion`](https://palantir.github.io/tslint/rules/no-non-null-assertion/) in [TSLint](https://palantir.github.io/tslint/)

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-parameter-properties.md

@@ -395,7 +395,3 @@ class Foo {
 ## When Not To Use It
 
 If you don't care about the using parameter properties in constructors, then you will not need this rule.
-
-## Related To
-
-- TSLint: [no-parameter-properties](https://palantir.github.io/tslint/rules/no-parameter-properties/)

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-require-imports.md

@@ -47,7 +47,3 @@ This rule is not configurable.
 ## When Not To Use It
 
 If you don't care about TypeScript module syntax, then you will not need this rule.
-
-## Related To
-
-- TSLint: [no-require-imports](https://palantir.github.io/tslint/rules/no-require-imports/)

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-this-alias.md

@@ -6,28 +6,26 @@ This rule prohibits assigning variables to `this`.
 
 ## Rule Details
 
-Rationale from TSLint:
+Assigning a variable to `this` instead of properly using arrow lambdas may be a symptom of pre-ES6 practices
+or not managing scope well.
 
-> Assigning a variable to `this` instead of properly using arrow lambdas may be a symptom of pre-ES6 practices
-> or not managing scope well.
->
-> Instead of storing a reference to `this` and using it inside a `function () {`:
->
-> ```js
-> const self = this;
->
-> setTimeout(function () {
->   self.doWork();
-> });
-> ```
->
-> Use `() =>` arrow lambdas, as they preserve `this` scope for you:
+Instead of storing a reference to `this` and using it inside a `function () {`:
+
+```js
+const self = this;
 >
-> ```js
-> setTimeout(() => {
->   this.doWork();
-> });
-> ```
+setTimeout(function () {
+    self.doWork();
+});
+```
+
+Use `() =>` arrow lambdas, as they preserve `this` scope for you:
+
+```js
+setTimeout(() => {
+  this.doWork();
+});
+```
 
 Examples of **incorrect** code for this rule:
 
@@ -56,7 +54,3 @@ You can pass an object option:
 ## When Not To Use It
 
 If you need to assign `this` to variables, you shouldn’t use this rule.
-
-## Related To
-
-- TSLint: [`no-this-assignment`](https://palantir.github.io/tslint/rules/no-this-assignment/)

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-type-alias.md

@@ -608,7 +608,3 @@ callback, etc. that would cause the code to be unreadable or impractical.
 ## Further Reading
 
 - [Advanced Types](https://www.typescriptlang.org/docs/handbook/advanced-types.html)
-
-## Related To
-
-- TSLint: [interface-over-type-literal](https://palantir.github.io/tslint/rules/interface-over-type-literal/)

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-unnecessary-boolean-literal-compare.md

@@ -146,7 +146,3 @@ if (!(someNullCondition ?? true)) {
 | `nullableBooleanVar !== true`  | `!nullableBooleanVar`           | Only checked/fixed if the `allowComparingNullableBooleansToTrue` option is `false`  |
 | `nullableBooleanVar === false` | `nullableBooleanVar ?? true`    | Only checked/fixed if the `allowComparingNullableBooleansToFalse` option is `false` |
 | `nullableBooleanVar !== false` | `!(nullableBooleanVar ?? true)` | Only checked/fixed if the `allowComparingNullableBooleansToFalse` option is `false` |
-
-## Related To
-
-- TSLint: [no-boolean-literal-compare](https://palantir.github.io/tslint/rules/no-boolean-literal-compare)

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-unnecessary-qualifier.md

@@ -92,7 +92,3 @@ This rule is not configurable.
 ## When Not To Use It
 
 If you don't care about having unneeded namespace or enum qualifiers, then you don't need to use this rule.
-
-## Related To
-
-- TSLint: [no-unnecessary-qualifier](https://palantir.github.io/tslint/rules/no-unnecessary-qualifier/)

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-unnecessary-type-arguments.md

@@ -66,7 +66,3 @@ class Impl implements I<string> {}
 ```
 
 This rule is not configurable.
-
-## Related To
-
-- TSLint: [use-default-type-parameter](https://palantir.github.io/tslint/rules/use-default-type-parameter)

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-unnecessary-type-assertion.md

@@ -73,7 +73,3 @@ const foo: Foo = 3;
 ## When Not To Use It
 
 If you don't care about having no-op type assertions in your code, then you can turn off this rule.
-
-## Related To
-
-- TSLint: [`no-unnecessary-type-assertion`](https://palantir.github.io/tslint/rules/no-unnecessary-type-assertion/)

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-unsafe-argument.md

@@ -87,4 +87,3 @@ This rule is not configurable.
 ## Related To
 
 - [`no-explicit-any`](./no-explicit-any.md)
-- TSLint: [`no-unsafe-any`](https://palantir.github.io/tslint/rules/no-unsafe-any/)

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-unsafe-assignment.md

@@ -90,4 +90,3 @@ This rule is not configurable.
 ## Related To
 
 - [`no-explicit-any`](./no-explicit-any.md)
-- TSLint: [`no-unsafe-any`](https://palantir.github.io/tslint/rules/no-unsafe-any/)

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-unsafe-call.md

@@ -64,4 +64,3 @@ This rule is not configurable.
 ## Related To
 
 - [`no-explicit-any`](./no-explicit-any.md)
-- TSLint: [`no-unsafe-any`](https://palantir.github.io/tslint/rules/no-unsafe-any/)

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-unsafe-member-access.md

@@ -70,4 +70,3 @@ This rule is not configurable.
 ## Related To
 
 - [`no-explicit-any`](./no-explicit-any.md)
-- TSLint: [`no-unsafe-any`](https://palantir.github.io/tslint/rules/no-unsafe-any/)

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-unsafe-return.md

@@ -107,4 +107,3 @@ This rule is not configurable.
 ## Related To
 
 - [`no-explicit-any`](./no-explicit-any.md)
-- TSLint: [`no-unsafe-any`](https://palantir.github.io/tslint/rules/no-unsafe-any/)

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-var-requires.md

@@ -42,7 +42,3 @@ This rule is not configurable.
 ## When Not To Use It
 
 If you don't care about TypeScript module syntax, then you will not need this rule.
-
-## Related To
-
-- TSLint: [no-var-requires](https://palantir.github.io/tslint/rules/no-var-requires/)

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/parameter-properties.md

@@ -482,7 +482,3 @@ class Foo {
 ## When Not To Use It
 
 If you don't care about the using parameter properties in constructors, then you will not need this rule.
-
-## Related To
-
-- TSLint: [no-parameter-properties](https://palantir.github.io/tslint/rules/no-parameter-properties/)

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/prefer-for-of.md

@@ -54,7 +54,3 @@ This rule is not configurable.
 ## When Not To Use It
 
 If you transpile for browsers that do not support for-of loops, you may wish to use traditional for loops that produce more compact code.
-
-## Related To
-
-- TSLint: ['prefer-for-of'](https://palantir.github.io/tslint/rules/prefer-for-of/)

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/prefer-function-type.md

@@ -94,7 +94,3 @@ This rule is not configurable.
 ## When Not To Use It
 
 If you specifically want to use an interface or type literal with a single call signature for stylistic reasons, you can disable this rule.
-
-## Further Reading
-
-- TSLint: [`callable-types`](https://palantir.github.io/tslint/rules/callable-types/)

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/prefer-namespace-keyword.md

@@ -31,7 +31,3 @@ This rule is not configurable.
 - [Modules](https://www.typescriptlang.org/docs/handbook/modules.html)
 - [Namespaces](https://www.typescriptlang.org/docs/handbook/namespaces.html)
 - [Namespaces and Modules](https://www.typescriptlang.org/docs/handbook/namespaces-and-modules.html)
-
-## Related To
-
-- TSLint: [no-internal-module](https://palantir.github.io/tslint/rules/no-internal-module/)

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/prefer-optional-chain.md

@@ -61,8 +61,8 @@ foo && foo.a && foo.a.b && foo.a.b.c;
 foo && foo['a'] && foo['a'].b && foo['a'].b.c;
 foo && foo.a && foo.a.b && foo.a.b.method && foo.a.b.method();
 
-(((foo || {}).a || {}).b {}).c;
-(((foo || {})['a'] || {}).b {}).c;
+(((foo || {}).a || {}).b || {}).c;
+(((foo || {})['a'] || {}).b || {}).c;
 
 // this rule also supports converting chained strict nullish checks:
 foo &&

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/prefer-readonly.md

@@ -85,7 +85,3 @@ class Container {
   private neverModifiedPrivate = 'unchanged';
 }
 ```
-
-## Related To
-
-- TSLint: ['prefer-readonly'](https://palantir.github.io/tslint/rules/prefer-readonly)

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/promise-function-async.md

@@ -65,7 +65,3 @@ In addition, each of the following properties may be provided, and default to `t
   ]
 }
 ```
-
-## Related To
-
-- TSLint: [promise-function-async](https://palantir.github.io/tslint/rules/promise-function-async)

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/restrict-plus-operands.md

@@ -100,7 +100,3 @@ var fn = (a: any, b: number) => a + b;
   "@typescript-eslint/restrict-plus-operands": "error"
 }
 ```
-
-## Related To
-
-- TSLint: [restrict-plus-operands](https://palantir.github.io/tslint/rules/restrict-plus-operands/)

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/strict-boolean-expressions.md

@@ -195,5 +195,4 @@ This rule provides following fixes and suggestions for particular types in boole
 
 ## Related To
 
-- TSLint: [strict-boolean-expressions](https://palantir.github.io/tslint/rules/strict-boolean-expressions)
 - [no-unnecessary-condition](./no-unnecessary-condition.md) - Similar rule which reports always-truthy and always-falsy values in conditions

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/triple-slash-reference.md

@@ -67,8 +67,3 @@ If you want to ban use of one or all of the triple slash reference directives, o
 ## When Not To Use It
 
 If you want to use all flavors of triple slash reference directives.
-
-## Related To
-
-- TSLint: [no-reference](http://palantir.github.io/tslint/rules/no-reference/)
-- TSLint: [no-reference-import](https://palantir.github.io/tslint/rules/no-reference-import/)

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/type-annotation-spacing.md

@@ -307,7 +307,3 @@ If you don't want to enforce spacing for your type annotations, you can safely t
 
 - [TypeScript Type System](https://basarat.gitbooks.io/typescript/docs/types/type-system.html)
 - [Type Inference](https://www.typescriptlang.org/docs/handbook/type-inference.html)
-
-## Related To
-
-- TSLint: [`typedef-whitespace`](https://palantir.github.io/tslint/rules/typedef-whitespace/)

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/typedef.md

@@ -28,7 +28,7 @@ TypeScript is often better at inferring types than easily written type annotatio
 This rule can enforce type annotations in locations regardless of whether they're required.
 This is typically used to maintain consistency for element types that sometimes require them.
 
-> To enforce type definitions existing on call signatures as per TSLint's `arrow-call-signature` and `call-signature` options, use `explicit-function-return-type`, or `explicit-module-boundary-types`.
+> To enforce type definitions existing on call signatures, use `explicit-function-return-type`, or `explicit-module-boundary-types`.
 
 ## Options
 
@@ -336,7 +336,3 @@ In general, if you do not consider the cost of writing unnecessary type annotati
 
 - [TypeScript Type System](https://basarat.gitbooks.io/typescript/docs/types/type-system.html)
 - [Type Inference](https://www.typescriptlang.org/docs/handbook/type-inference.html)
-
-## Related To
-
-- TSLint: [`typedef`](https://palantir.github.io/tslint/rules/typedef)

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/unbound-method.md

@@ -114,7 +114,3 @@ log();
 If your code intentionally waits to bind methods after use, such as by passing a `scope: this` along with the method, you can disable this rule.
 
 If you're wanting to use `toBeCalled` and similar matches in `jest` tests, you can disable this rule for your test files in favor of [`eslint-plugin-jest`'s version of this rule](https://github.com/jest-community/eslint-plugin-jest/blob/main/docs/rules/unbound-method.md).
-
-## Related To
-
-- TSLint: [no-unbound-method](https://palantir.github.io/tslint/rules/no-unbound-method/)

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/unified-signatures.md

@@ -75,7 +75,3 @@ function f(b: string): void;
 function f(...a: number[]): void;
 function f(...a: string[]): void;
 ```
-
-## Related To
-
-- TSLint: [`unified-signatures`](https://palantir.github.io/tslint/rules/unified-signatures/)

package/node_modules/@typescript-eslint/eslint-plugin/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@typescript-eslint/eslint-plugin",
-  "version": "5.27.1",
+  "version": "5.30.7",
   "description": "TypeScript plugin for ESLint",
   "keywords": [
     "eslint",
@@ -44,9 +44,9 @@
     "typecheck": "tsc -p tsconfig.json --noEmit"
   },
   "dependencies": {
-    "@typescript-eslint/scope-manager": "5.27.1",
-    "@typescript-eslint/type-utils": "5.27.1",
-    "@typescript-eslint/utils": "5.27.1",
+    "@typescript-eslint/scope-manager": "5.30.7",
+    "@typescript-eslint/type-utils": "5.30.7",
+    "@typescript-eslint/utils": "5.30.7",
     "debug": "^4.3.4",
     "functional-red-black-tree": "^1.0.1",
     "ignore": "^5.2.0",
@@ -79,5 +79,5 @@
     "type": "opencollective",
     "url": "https://opencollective.com/typescript-eslint"
   },
-  "gitHead": "4e79ad260b60085ccb9761aba887cc159701c7d4"
+  "gitHead": "557ce041be53443a35a933549fe38660a9a770c5"
 }

package/node_modules/@typescript-eslint/parser/_ts3.4/dist/index.d.ts

@@ -0,0 +1,4 @@
+export { parse, parseForESLint, ParserOptions } from './parser';
+export { ParserServices, clearCaches, createProgram, } from '@typescript-eslint/typescript-estree';
+export declare const version: string;
+//# sourceMappingURL=index.d.ts.map

package/node_modules/@typescript-eslint/parser/_ts3.4/dist/parser.d.ts

@@ -0,0 +1,20 @@
+import { ParserOptions, TSESTree } from '@typescript-eslint/types';
+import { ParserServices, visitorKeys } from '@typescript-eslint/typescript-estree';
+import { ScopeManager } from '@typescript-eslint/scope-manager';
+interface ParseForESLintResult {
+    ast: TSESTree.Program & {
+        range?: [
+            number,
+            number
+        ];
+        tokens?: TSESTree.Token[];
+        comments?: TSESTree.Comment[];
+    };
+    services: ParserServices;
+    visitorKeys: typeof visitorKeys;
+    scopeManager: ScopeManager;
+}
+declare function parse(code: string, options?: ParserOptions): ParseForESLintResult['ast'];
+declare function parseForESLint(code: string, options?: ParserOptions | null): ParseForESLintResult;
+export { parse, parseForESLint, ParserOptions };
+//# sourceMappingURL=parser.d.ts.map