xo 0.51.0 → 0.52.0

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

@@ -1,6 +1,10 @@
-# `return-await`
+---
+description: 'Enforce consistent returning of awaited values.'
+---
 
-Enforces consistent returning of awaited values.
+> 🛑 This file is source code, not the primary documentation location! 🛑
+>
+> See **https://typescript-eslint.io/rules/return-await** for documentation.
 
 Returning an awaited promise can make sense for better stack trace information as well as for consistent error handling (returned promises will not be caught in an async function try/catch).
 
@@ -9,16 +13,6 @@ Returning an awaited promise can make sense for better stack trace information a
 This rule builds on top of the [`eslint/no-return-await`](https://eslint.org/docs/rules/no-return-await) rule.
 It expands upon the base rule to add support for optionally requiring `return await` in certain cases.
 
-## How to Use
-
-```jsonc
-{
-  // note you must disable the base rule as it can report incorrect errors
-  "no-return-await": "off",
-  "@typescript-eslint/return-await": "error"
-}
-```
-
 ## Options
 
 ```ts

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

@@ -1,6 +1,10 @@
-# `semi`
+---
+description: 'Require or disallow semicolons instead of ASI.'
+---
 
-Requires or disallows semicolons instead of ASI.
+> 🛑 This file is source code, not the primary documentation location! 🛑
+>
+> See **https://typescript-eslint.io/rules/semi** for documentation.
 
 This rule enforces consistent use of semicolons after statements.
 
@@ -10,23 +14,3 @@ This rule extends the base [`eslint/semi`](https://eslint.org/docs/rules/semi) r
 It adds support for TypeScript features that require semicolons.
 
 See also the [`@typescript-eslint/member-delimiter-style`](member-delimiter-style.md) rule, which allows you to specify the delimiter for `type` and `interface` members.
-
-## How to Use
-
-```jsonc
-{
-  // note you must disable the base rule as it can report incorrect errors
-  "semi": "off",
-  "@typescript-eslint/semi": ["error"]
-}
-```
-
-## Options
-
-See [`eslint/semi` options](https://eslint.org/docs/rules/semi#options).
-
-<sup>
-
-Taken with ❤️ [from ESLint core](https://github.com/eslint/eslint/blob/main/docs/rules/semi.md)
-
-</sup>

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/sort-type-union-intersection-members.md

@@ -1,6 +1,10 @@
-# `sort-type-union-intersection-members`
+---
+description: 'Enforce members of a type union/intersection to be sorted alphabetically.'
+---
 
-Enforces members of a type union/intersection to be sorted alphabetically.
+> 🛑 This file is source code, not the primary documentation location! 🛑
+>
+> See **https://typescript-eslint.io/rules/sort-type-union-intersection-members** for documentation.
 
 Sorting union (`|`) and intersection (`&`) types can help:
 
@@ -91,49 +95,6 @@ type T4 =
 
 ## Options
 
-```ts
-type Options = {
-  // true to check intersection types, false otherwise
-  checkIntersections?: boolean;
-  // true to check union types, false otherwise
-  checkUnions?: boolean;
-  // the ordering of the groups
-  groupOrder?: (
-    | 'conditional'
-    | 'function'
-    | 'import'
-    | 'intersection'
-    | 'keyword'
-    | 'literal'
-    | 'named'
-    | 'object'
-    | 'operator'
-    | 'tuple'
-    | 'union'
-    | 'nullish'
-  )[];
-};
-
-const defaultOptions: Options = {
-  checkIntersections: true,
-  checkUnions: true,
-  groupOrder: [
-    'named',
-    'keyword',
-    'operator',
-    'literal',
-    'function',
-    'import',
-    'conditional',
-    'object',
-    'tuple',
-    'intersection',
-    'union',
-    'nullish',
-  ],
-};
-```
-
 ### `groupOrder`
 
 Each member of the type is placed into a group, and then the rule sorts alphabetically within each group.

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/space-before-blocks.md

@@ -1,11 +1,17 @@
-# `space-before-blocks`
+---
+description: 'Enforce consistent spacing before blocks.'
+---
 
-Enforces consistent spacing before blocks.
+> 🛑 This file is source code, not the primary documentation location! 🛑
+>
+> See **https://typescript-eslint.io/rules/space-before-blocks** for documentation.
 
 ## Rule Details
 
 This rule extends the base [`eslint/space-before-blocks`](https://eslint.org/docs/rules/space-before-blocks) rule.
-It adds support for interfaces and enums:
+It adds support for interfaces and enums.
+
+<!-- tabs -->
 
 ### ❌ Incorrect
 
@@ -31,24 +37,6 @@ interface State {
 }
 ```
 
-In case a more specific options object is passed these blocks will follow `classes` configuration option.
-
-## How to Use
-
-```jsonc
-{
-  // note you must disable the base rule as it can report incorrect errors
-  "space-before-blocks": "off",
-  "@typescript-eslint/space-before-blocks": ["error"]
-}
-```
-
 ## Options
 
-See [`eslint/space-before-blocks` options](https://eslint.org/docs/rules/space-before-blocks#options).
-
-<sup>
-
-Taken with ❤️ [from ESLint core](https://github.com/eslint/eslint/blob/master/docs/rules/space-before-blocks.md)
-
-</sup>
+In case a more specific options object is passed these blocks will follow `classes` configuration option.

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/space-before-function-paren.md

@@ -1,28 +1,12 @@
-# `space-before-function-paren`
+---
+description: 'Enforce consistent spacing before function parenthesis.'
+---
 
-Enforces consistent spacing before function parenthesis.
+> 🛑 This file is source code, not the primary documentation location! 🛑
+>
+> See **https://typescript-eslint.io/rules/space-before-function-paren** for documentation.
 
 ## Rule Details
 
 This rule extends the base [`eslint/space-before-function-paren`](https://eslint.org/docs/rules/space-before-function-paren) rule.
 It adds support for generic type parameters on function calls.
-
-## How to Use
-
-```jsonc
-{
-  // note you must disable the base rule as it can report incorrect errors
-  "space-before-function-paren": "off",
-  "@typescript-eslint/space-before-function-paren": ["error"]
-}
-```
-
-## Options
-
-See [`eslint/space-before-function-paren` options](https://eslint.org/docs/rules/space-before-function-paren#options).
-
-<sup>
-
-Taken with ❤️ [from ESLint core](https://github.com/eslint/eslint/blob/main/docs/rules/space-before-function-paren.md)
-
-</sup>

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/space-infix-ops.md

@@ -1,32 +1,16 @@
-# `space-infix-ops`
+---
+description: 'Require spacing around infix operators.'
+---
 
-Requires spacing around infix operators.
+> 🛑 This file is source code, not the primary documentation location! 🛑
+>
+> See **https://typescript-eslint.io/rules/space-infix-ops** for documentation.
 
 This rule extends the base [`eslint/space-infix-ops`](https://eslint.org/docs/rules/space-infix-ops) rule.
-
-It also add support for enum members
+It adds support for enum members.
 
 ```ts
 enum MyEnum {
   KEY = 'value',
 }
 ```
-
-## How to Use
-
-```jsonc
-{
-  "space-infix-ops": "off",
-  "@typescript-eslint/space-infix-ops": ["error", { "int32Hint": false }]
-}
-```
-
-## Options
-
-See [`eslint/space-infix-ops` options](https://eslint.org/docs/rules/space-infix-ops#options).
-
-<sup>
-
-Taken with ❤️ [from ESLint core](https://github.com/eslint/eslint/blob/main/docs/rules/space-infix-ops.md)
-
-</sup>

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

@@ -1,6 +1,10 @@
-# `strict-boolean-expressions`
+---
+description: 'Disallow certain types in boolean expressions.'
+---
 
-Disallows certain types in boolean expressions.
+> 🛑 This file is source code, not the primary documentation location! 🛑
+>
+> See **https://typescript-eslint.io/rules/strict-boolean-expressions** for documentation.
 
 Forbids usage of non-boolean types in expressions where a boolean is expected.
 `boolean` and `never` types are always allowed.
@@ -85,29 +89,6 @@ const foo = (arg: any) => (Boolean(arg) ? 1 : 0);
 
 ## Options
 
-```ts
-type Options = {
-  allowString?: boolean;
-  allowNumber?: boolean;
-  allowNullableObject?: boolean;
-  allowNullableBoolean?: boolean;
-  allowNullableString?: boolean;
-  allowNullableNumber?: boolean;
-  allowAny?: boolean;
-};
-
-const defaultOptions: Options = {
-  allowString: true,
-  allowNumber: true,
-  allowNullableObject: true,
-  allowNullableBoolean: false,
-  allowNullableString: false,
-  allowNullableNumber: false,
-  allowAny: false,
-  allowRuleToRunWithoutStrictNullChecksIKnowWhatIAmDoing: false,
-};
-```
-
 ### `allowString`
 
 Allows `string` in a boolean context.

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/switch-exhaustiveness-check.md

@@ -1,6 +1,10 @@
-# `switch-exhaustiveness-check`
+---
+description: 'Require switch-case statements to be exhaustive with union type.'
+---
 
-Requires switch-case statements to be exhaustive with union type.
+> 🛑 This file is source code, not the primary documentation location! 🛑
+>
+> See **https://typescript-eslint.io/rules/switch-exhaustiveness-check** for documentation.
 
 Union type may have a lot of parts. It's easy to forget to consider all cases in switch. This rule reminds which parts are missing. If domain of the problem requires to have only a partial switch, developer may _explicitly_ add a default clause.
 
@@ -106,19 +110,6 @@ switch (day) {
 }
 ```
 
-## Options
-
-```jsonc
-// .eslintrc.json
-{
-  "rules": {
-    "@typescript-eslint/switch-exhaustiveness-check": "warn"
-  }
-}
-```
-
-This rule is not configurable.
-
 ## When Not To Use It
 
 If program doesn't have union types with many parts. Downside of this rule is the need for type information, so it's slower than regular rules.

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

@@ -1,10 +1,16 @@
-# `triple-slash-reference`
+---
+description: 'Disallow certain triple slash directives in favor of ES6-style import declarations.'
+---
 
-Disallows certain triple slash directives in favor of ES6-style import declarations.
+> 🛑 This file is source code, not the primary documentation location! 🛑
+>
+> See **https://typescript-eslint.io/rules/triple-slash-reference** for documentation.
+
+## Rule Details
 
 Use of triple-slash reference type directives is discouraged in favor of the newer `import` style. This rule allows you to ban use of `/// <reference path="" />`, `/// <reference types="" />`, or `/// <reference lib="" />` directives.
 
-## Rule Details
+## Options
 
 With `{ "path": "never", "types": "never", "lib": "never" }` options set, the following will all be **incorrect** usage:
 
@@ -44,22 +50,6 @@ import * as foo from 'foo';
 import foo = require('foo');
 ```
 
-## Options
-
-```ts
-type Options = {
-  lib?: 'always' | 'never';
-  path?: 'always' | 'never';
-  types?: 'always' | 'never' | 'prefer-import';
-};
-
-const defaultOptions: Options = {
-  lib: 'always',
-  path: 'never',
-  types: 'prefer-import',
-};
-```
-
 ## When To Use It
 
 If you want to ban use of one or all of the triple slash reference directives, or any time you might use triple-slash type reference directives and ES6 import declarations in the same file.

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

@@ -1,6 +1,10 @@
-# `type-annotation-spacing`
+---
+description: 'Require consistent spacing around type annotations.'
+---
 
-Requires consistent spacing around type annotations.
+> 🛑 This file is source code, not the primary documentation location! 🛑
+>
+> See **https://typescript-eslint.io/rules/type-annotation-spacing** for documentation.
 
 Spacing around type annotations improves readability of the code. Although the most commonly used style guideline for type annotations in TypeScript prescribes adding a space after the colon, but not before it, it is subjective to the preferences of a project. For example:
 
@@ -37,21 +41,11 @@ This rule aims to enforce specific spacing patterns around type annotations and
 
 ## Options
 
-This rule has an object option:
-
-- `"before": false`, (default for colon) disallows spaces before the colon/arrow.
-- `"before": true`, (default for arrow) requires a space before the colon/arrow.
-- `"after": true`, (default) requires a space after the colon/arrow.
-- `"after": false`, disallows spaces after the colon/arrow.
-- `"overrides"`, overrides the default options for type annotations with `colon` (e.g. `const foo: string`) and function types with `arrow` (e.g. `type Foo = () => {}`). Additionally allows granular overrides for `variable` (`const foo: string`),`parameter` (`function foo(bar: string) {...}`),`property` (`interface Foo { bar: string }`) and `returnType` (`function foo(): string {...}`) annotations.
-
-### defaults
-
 Examples of code for this rule with no options at all:
 
 <!--tabs-->
 
-#### ❌ Incorrect
+### ❌ Incorrect
 
 <!-- prettier-ignore -->
 ```ts
@@ -80,7 +74,7 @@ type Foo = () =>{};
 type Foo = ()=> {};
 ```
 
-#### ✅ Correct
+### ✅ Correct
 
 <!-- prettier-ignore -->
 ```ts

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

@@ -1,6 +1,10 @@
-# `typedef`
+---
+description: 'Require type annotations in certain places.'
+---
 
-Requires type annotations in certain places.
+> 🛑 This file is source code, not the primary documentation location! 🛑
+>
+> See **https://typescript-eslint.io/rules/typedef** for documentation.
 
 TypeScript cannot always infer types for all places in code.
 Some locations require type annotations for their types to be inferred.
@@ -18,11 +22,15 @@ class ContainsText {
 }
 ```
 
-**_Note:_** requiring type annotations unnecessarily can be cumbersome to maintain and generally reduces code readability.
+:::caution
+
+Requiring type annotations unnecessarily can be cumbersome to maintain and generally reduces code readability.
 TypeScript is often better at inferring types than easily written type annotations would allow.
 
 **Instead of enabling `typedef`, it is generally recommended to use the `--noImplicitAny` and `--strictPropertyInitialization` compiler options to enforce type annotations only when useful.**
 
+:::
+
 ## Rule Details
 
 This rule can enforce type annotations in locations regardless of whether they're required.
@@ -32,30 +40,6 @@ This is typically used to maintain consistency for element types that sometimes
 
 ## Options
 
-```ts
-type Options = {
-  arrayDestructuring?: boolean;
-  arrowParameter?: boolean;
-  memberVariableDeclaration?: boolean;
-  objectDestructuring?: boolean;
-  parameter?: boolean;
-  propertyDeclaration?: boolean;
-  variableDeclaration?: boolean;
-  variableDeclarationIgnoreFunction?: boolean;
-};
-
-const defaultOptions: Options = {
-  arrayDestructuring: false,
-  arrowParameter: false,
-  memberVariableDeclaration: false,
-  objectDestructuring: false,
-  parameter: false,
-  propertyDeclaration: false,
-  variableDeclaration: false,
-  variableDeclarationIgnoreFunction: false,
-};
-```
-
 For example, with the following configuration:
 
 ```json

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

@@ -1,18 +1,19 @@
-# `unbound-method`
+---
+description: 'Enforce unbound methods are called with their expected scope.'
+---
 
-Enforces unbound methods are called with their expected scope.
-
-Warns when a method is used outside of a method call.
+> 🛑 This file is source code, not the primary documentation location! 🛑
+>
+> See **https://typescript-eslint.io/rules/unbound-method** for documentation.
 
 Class functions don't preserve the class scope when passed as standalone variables.
-
 If your function does not access `this`, [you can annotate it with `this: void`](https://www.typescriptlang.org/docs/handbook/2/functions.html#declaring-this-in-a-function), or consider using an arrow function instead.
 
 If you're working with `jest`, you can use [`eslint-plugin-jest`'s version of this rule](https://github.com/jest-community/eslint-plugin-jest/blob/main/docs/rules/unbound-method.md) to lint your test files, which knows when it's ok to pass an unbound method to `expect` calls.
 
 ## Rule Details
 
-Examples of code for this rule
+Examples of code for this rule with the default options:
 
 <!--tabs-->
 
@@ -75,10 +76,6 @@ const { double } = arith;
 
 ## Options
 
-The rule accepts an options object with the following property:
-
-- `ignoreStatic` to not check whether `static` methods are correctly bound
-
 ### `ignoreStatic`
 
 Examples of **correct** code for this rule with `{ ignoreStatic: true }`:
@@ -96,19 +93,6 @@ const { log } = OtherClass;
 log();
 ```
 
-## Example
-
-```json
-{
-  "@typescript-eslint/unbound-method": [
-    "error",
-    {
-      "ignoreStatic": true
-    }
-  ]
-}
-```
-
 ## When Not To Use It
 
 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.

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

@@ -1,27 +1,15 @@
-# `unified-signatures`
+---
+description: 'Disallow two overloads that could be unified into one with a union or an optional/rest parameter.'
+---
 
-Disallows two overloads that could be unified into one with a union or an optional/rest parameter.
+> 🛑 This file is source code, not the primary documentation location! 🛑
+>
+> See **https://typescript-eslint.io/rules/unified-signatures** for documentation.
 
 ## Rule Details
 
 This rule aims to keep the source code as maintainable as possible by reducing the amount of overloads.
 
-## Options
-
-```ts
-type Options = {
-  ignoreDifferentlyNamedParameters?: boolean;
-};
-
-const defaultOptions: Options = {
-  ignoreDifferentlyNamedParameters: false,
-};
-```
-
-The rule accepts an options object with the following property:
-
-- `ignoreDifferentlyNamedParameters`: whether two parameters with different names at the same index should be considered different even if their types are the same.
-
 Examples of code for this rule with the default options:
 
 <!--tabs-->
@@ -48,6 +36,10 @@ function x(x: number | string): void;
 function y(...x: number[]): void;
 ```
 
+## Options
+
+### `ignoreDifferentlyNamedParameters`
+
 Examples of code for this rule with `ignoreDifferentlyNamedParameters`:
 
 <!--tabs-->
@@ -75,3 +67,5 @@ function f(b: string): void;
 function f(...a: number[]): void;
 function f(...a: string[]): void;
 ```
+
+## Options

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

@@ -1,6 +1,6 @@
 {
   "name": "@typescript-eslint/eslint-plugin",
-  "version": "5.30.7",
+  "version": "5.35.1",
   "description": "TypeScript plugin for ESLint",
   "keywords": [
     "eslint",
@@ -44,9 +44,9 @@
     "typecheck": "tsc -p tsconfig.json --noEmit"
   },
   "dependencies": {
-    "@typescript-eslint/scope-manager": "5.30.7",
-    "@typescript-eslint/type-utils": "5.30.7",
-    "@typescript-eslint/utils": "5.30.7",
+    "@typescript-eslint/scope-manager": "5.35.1",
+    "@typescript-eslint/type-utils": "5.35.1",
+    "@typescript-eslint/utils": "5.35.1",
     "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": "557ce041be53443a35a933549fe38660a9a770c5"
+  "gitHead": "cb43b4a19dcb967c3342dc8e677e57097b76d888"
 }

package/node_modules/@typescript-eslint/parser/README.md

@@ -256,7 +256,7 @@ Note that if you pass custom programs via `options.programs` this option will no
 
 Default `undefined`.
 
-This option allow you to tell parser to act as if `emitDecoratorMetadata: true` is set in `tsconfig.json`, but without [type-aware linting](https://typescript-eslint.io/docs/linting/type-linting). In other words, you don't have to specify `parserOptions.project` in this case, making the linting process faster.
+This option allow you to tell parser to act as if `emitDecoratorMetadata: true` is set in `tsconfig.json`, but without [type-aware linting](https://typescript-eslint.io/docs/linting/typed-linting). In other words, you don't have to specify `parserOptions.project` in this case, making the linting process faster.
 
 ## Utilities
 

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

@@ -1,6 +1,6 @@
 {
   "name": "@typescript-eslint/parser",
-  "version": "5.30.7",
+  "version": "5.35.1",
   "description": "An ESLint custom parser which leverages TypeScript ESTree",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
@@ -45,9 +45,9 @@
     "eslint": "^6.0.0 || ^7.0.0 || ^8.0.0"
   },
   "dependencies": {
-    "@typescript-eslint/scope-manager": "5.30.7",
-    "@typescript-eslint/types": "5.30.7",
-    "@typescript-eslint/typescript-estree": "5.30.7",
+    "@typescript-eslint/scope-manager": "5.35.1",
+    "@typescript-eslint/types": "5.35.1",
+    "@typescript-eslint/typescript-estree": "5.35.1",
     "debug": "^4.3.4"
   },
   "devDependencies": {
@@ -71,5 +71,5 @@
       ]
     }
   },
-  "gitHead": "557ce041be53443a35a933549fe38660a9a770c5"
+  "gitHead": "cb43b4a19dcb967c3342dc8e677e57097b76d888"
 }

package/node_modules/@typescript-eslint/scope-manager/dist/referencer/ClassVisitor.d.ts

@@ -14,6 +14,7 @@ declare class ClassVisitor extends Visitor {
     protected visitMethod(node: TSESTree.MethodDefinition): void;
     protected visitType(node: TSESTree.Node | null | undefined): void;
     protected visitMetadataType(node: TSESTree.TSTypeAnnotation | null | undefined, withDecorators: boolean): void;
+    protected visitStaticBlock(node: TSESTree.StaticBlock): void;
     protected ClassBody(node: TSESTree.ClassBody): void;
     protected PropertyDefinition(node: TSESTree.PropertyDefinition): void;
     protected MethodDefinition(node: TSESTree.MethodDefinition): void;
@@ -21,6 +22,7 @@ declare class ClassVisitor extends Visitor {
     protected TSAbstractMethodDefinition(node: TSESTree.TSAbstractMethodDefinition): void;
     protected Identifier(node: TSESTree.Identifier): void;
     protected PrivateIdentifier(): void;
+    protected StaticBlock(node: TSESTree.StaticBlock): void;
 }
 export { ClassVisitor };
 //# sourceMappingURL=ClassVisitor.d.ts.map