xo 0.47.0 → 0.50.0

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

@@ -1,4 +1,6 @@
-# Enforces using a particular method signature syntax. (`method-signature-style`)
+# `method-signature-style`
+
+Enforces using a particular method signature syntax.
 
 There are two ways to define an object/interface function property.
 
@@ -32,9 +34,13 @@ This rule accepts one string option:
 
 The default is `"property"`.
 
-## Rule Details
+### `property`
+
+Examples of code with `property` option.
 
-Examples of **incorrect** code with `property` option.
+<!--tabs-->
+
+#### ❌ Incorrect
 
 ```ts
 interface T1 {
@@ -50,7 +56,7 @@ interface T3 {
 }
 ```
 
-Examples of **correct** code with `property` option.
+#### ✅ Correct
 
 ```ts
 interface T1 {
@@ -67,7 +73,13 @@ interface T3 {
 }
 ```
 
-Examples of **incorrect** code with `method` option.
+### `method`
+
+Examples of code with `method` option.
+
+<!--tabs-->
+
+#### ❌ Incorrect
 
 ```ts
 interface T1 {
@@ -78,7 +90,7 @@ type T2 = {
 };
 ```
 
-Examples of **correct** code with `method` option.
+#### ✅ Correct
 
 ```ts
 interface T1 {
@@ -92,9 +104,3 @@ type T2 = {
 ## When Not To Use It
 
 If you don't want to enforce a particular style for object/interface function types, and/or if you don't use `strictFunctionTypes`, then you don't need this rule.
-
-## Attributes
-
-- [ ] ✅ Recommended
-- [x] 🔧 Fixable
-- [ ] 💭 Requires type information

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

@@ -1,4 +1,6 @@
-# Enforces naming conventions for everything across a codebase (`naming-convention`)
+# `naming-convention`
+
+Enforces naming conventions for everything across a codebase.
 
 Enforcing naming conventions helps keep the codebase consistent, and reduces overhead when thinking about how to name a variable.
 Additionally, a well-designed style guide can help communicate intent, such as by enforcing all private properties begin with an `_`, and all global-level constants are written in `UPPER_CASE`.
@@ -9,7 +11,11 @@ There are many different rules that have existed over time, but they have had th
 
 This rule allows you to enforce conventions for any identifier, using granular selectors to create a fine-grained style guide.
 
-### Note - this rule only needs type information in specific cases, detailed below
+:::note
+
+This rule only needs type information in specific cases, detailed below.
+
+:::
 
 ## Options
 
@@ -105,7 +111,7 @@ The `format` option defines the allowed formats for the identifier. This option
 Instead of an array, you may also pass `null`. This signifies "this selector shall not have its format checked".
 This can be useful if you want to enforce no particular format for a specific selector, after applying a group selector.
 
-### `custom`
+#### `custom`
 
 The `custom` option defines a custom regex that the identifier must (or must not) match. This option allows you to have a bit more finer-grained control over identifiers, letting you ban (or force) certain patterns and substrings.
 Accepts an object with the following properties:
@@ -113,7 +119,7 @@ Accepts an object with the following properties:
 - `regex` - a string that is then passed into RegExp to create a new regular expression: `new RegExp(regex)`
 - `match` - true if the identifier _must_ match the `regex`, false if the identifier _must not_ match the `regex`.
 
-### `filter`
+#### `filter`
 
 The `filter` option operates similar to `custom`, accepting the same shaped object, except that it controls if the rest of the configuration should or should not be applied to an identifier.
 
@@ -694,9 +700,3 @@ You can use the `destructured` modifier to match these names, and explicitly set
 ## When Not To Use It
 
 If you do not want to enforce naming conventions for anything.
-
-## Attributes
-
-- [ ] ✅ Recommended
-- [ ] 🔧 Fixable
-- [x] 💭 Requires type information

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

@@ -1,11 +1,15 @@
-# Disallow generic `Array` constructors (`no-array-constructor`)
+# `no-array-constructor`
+
+Disallows generic `Array` constructors.
 
 ## Rule Details
 
 This rule extends the base [`eslint/no-array-constructor`](https://eslint.org/docs/rules/no-array-constructor) rule.
 It adds support for the generically typed `Array` constructor (`new Array<Foo>()`).
 
-Examples of **incorrect** code for this rule:
+<!--tabs-->
+
+### ❌ Incorrect
 
 ```ts
 /*eslint no-array-constructor: "error"*/
@@ -14,7 +18,7 @@ Array(0, 1, 2);
 new Array(0, 1, 2);
 ```
 
-Examples of **correct** code for this rule:
+### ✅ Correct
 
 ```ts
 /*eslint no-array-constructor: "error"*/
@@ -26,7 +30,7 @@ Array(500);
 new Array(someOtherArray.length);
 ```
 
-## How to use
+## How to Use
 
 ```jsonc
 {
@@ -40,10 +44,8 @@ new Array(someOtherArray.length);
 
 See [`eslint/no-array-constructor` options](https://eslint.org/docs/rules/no-array-constructor#options).
 
-<sup>Taken with ❤️ [from ESLint core](https://github.com/eslint/eslint/blob/master/docs/rules/no-array-constructor.md)</sup>
+<sup>
 
-## Attributes
+Taken with ❤️ [from ESLint core](https://github.com/eslint/eslint/blob/main/docs/rules/no-array-constructor.md)
 
-- [x] ✅ Recommended
-- [x] 🔧 Fixable
-- [ ] 💭 Requires type information
+</sup>

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-base-to-string.md

@@ -1,4 +1,6 @@
-# Requires that `.toString()` is only called on objects which provide useful information when stringified (`no-base-to-string`)
+# `no-base-to-string`
+
+Requires `.toString()` to only be called on objects which provide useful information when stringified.
 
 JavaScript will call `toString()` on an object when it is converted to a string, such as when `+` adding to a string or in `${}` template literals.
 
@@ -13,7 +15,9 @@ This rule has some overlap with [`restrict-plus-operands`](./restrict-plus-opera
 
 This rule prevents accidentally defaulting to the base Object `.toString()` method.
 
-Examples of **incorrect** code for this rule:
+<!--tabs-->
+
+### ❌ Incorrect
 
 ```ts
 // Passing an object or class instance to string concatenation:
@@ -28,7 +32,7 @@ value + '';
 ({}.toString());
 ```
 
-Examples of **correct** code for this rule:
+### ✅ Correct
 
 ```ts
 // These types all have useful .toString()s
@@ -85,9 +89,3 @@ let text = `${value}`;
 If you don't mind `"[object Object]"` in your strings, then you will not need this rule.
 
 - [`Object.prototype.toString()` MDN documentation](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/toString)
-
-## Attributes
-
-- [ ] ✅ Recommended
-- [ ] 🔧 Fixable
-- [x] 💭 Requires type information

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

@@ -1,4 +1,6 @@
-# Disallow non-null assertion in locations that may be confusing (`no-confusing-non-null-assertion`)
+# `no-confusing-non-null-assertion`
+
+Disallows non-null assertion in locations that may be confusing.
 
 ## Rule Details
 
@@ -10,7 +12,9 @@ a !== b; // not equals test(`!==`)
 a! === b; // a non-null assertions(`!`) and an triple equals test(`===`)
 ```
 
-Examples of **incorrect** code for this rule:
+<!--tabs-->
+
+### ❌ Incorrect
 
 ```ts
 interface Foo {
@@ -23,7 +27,7 @@ const isEqualsBar = foo.bar! == 'hello';
 const isEqualsNum = 1 + foo.num! == 2;
 ```
 
-Examples of **correct** code for this rule:
+### ✅ Correct
 
 <!-- prettier-ignore -->
 ```ts
@@ -37,6 +41,19 @@ const isEqualsBar = foo.bar == 'hello';
 const isEqualsNum = (1 + foo.num!) == 2;
 ```
 
+## Options
+
+```jsonc
+// .eslintrc.json
+{
+  "rules": {
+    "@typescript-eslint/no-confusing-non-null-assertion": "warn"
+  }
+}
+```
+
+This rule is not configurable.
+
 ## When Not To Use It
 
 If you don't care about this confusion, then you will not need this rule.
@@ -44,9 +61,3 @@ If you don't care about this confusion, then you will not need this rule.
 ## Further Reading
 
 - [`Issue: Easy misunderstanding: "! ==="`](https://github.com/microsoft/TypeScript/issues/37837) in [TypeScript repo](https://github.com/microsoft/TypeScript)
-
-## Attributes
-
-- [ ] ✅ Recommended
-- [x] 🔧 Fixable
-- [ ] 💭 Requires type information

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

@@ -1,4 +1,6 @@
-# Requires expressions of type void to appear in statement position (`no-confusing-void-expression`)
+# `no-confusing-void-expression`
+
+Requires expressions of type void to appear in statement position.
 
 Returning the results of an expression whose type is void can be misleading.
 Attempting to do so is likely a symptom of expecting a different return type from a function.
@@ -9,7 +11,9 @@ This rule provides automatic fixes for most common cases.
 
 ## Examples
 
-Examples of **incorrect** code for this rule:
+<!--tabs-->
+
+### ❌ Incorrect
 
 ```ts
 // somebody forgot that `alert` doesn't return anything
@@ -29,7 +33,7 @@ function doSomething() {
 }
 ```
 
-Examples of **correct** code for this rule:
+### ✅ Correct
 
 ```ts
 // just a regular void function in a statement position
@@ -144,12 +148,6 @@ The return type of a function can be inspected by going to its definition or hov
 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
+## Related To
 
 - TSLint: ['no-void-expression'](https://palantir.github.io/tslint/rules/no-void-expression/)
-
-## Attributes
-
-- [ ] ✅ Recommended
-- [x] 🔧 Fixable
-- [x] 💭 Requires type information

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

@@ -1,11 +1,13 @@
-# Disallow duplicate class members (`no-dupe-class-members`)
+# `no-dupe-class-members`
+
+Disallows duplicate class members.
 
 ## Rule Details
 
 This rule extends the base [`eslint/no-dupe-class-members`](https://eslint.org/docs/rules/no-dupe-class-members) rule.
 It adds support for TypeScript's method overload definitions.
 
-## How to use
+## How to Use
 
 ```jsonc
 {
@@ -19,10 +21,8 @@ It adds support for TypeScript's method overload definitions.
 
 See [`eslint/no-dupe-class-members` options](https://eslint.org/docs/rules/no-dupe-class-members#options).
 
-<sup>Taken with ❤️ [from ESLint core](https://github.com/eslint/eslint/blob/master/docs/rules/no-dupe-class-members.md)</sup>
+<sup>
 
-## Attributes
+Taken with ❤️ [from ESLint core](https://github.com/eslint/eslint/blob/main/docs/rules/no-dupe-class-members.md)
 
-- [ ] ✅ Recommended
-- [ ] 🔧 Fixable
-- [ ] 💭 Requires type information
+</sup>

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-duplicate-enum-values.md

@@ -0,0 +1,56 @@
+# `no-duplicate-enum-values`
+
+Disallows duplicate enum member values.
+
+Although TypeScript supports duplicate enum member values, people usually expect members to have unique values within the same enum. Duplicate values can lead to bugs that are hard to track down.
+
+## Rule Details
+
+This rule disallows defining an enum with multiple members initialized to the same value. Now it only enforces on enum members initialized with String or Number literals. Members without initializer or initialized with an expression are not checked by this rule.
+
+<!--tabs-->
+
+### ❌ Incorrect
+
+```ts
+enum E {
+  A = 0,
+  B = 0,
+}
+```
+
+```ts
+enum E {
+  A = 'A'
+  B = 'A'
+}
+```
+
+### ✅ Correct
+
+```ts
+enum E {
+  A = 0,
+  B = 1,
+}
+```
+
+```ts
+enum E {
+  A = 'A'
+  B = 'B'
+}
+```
+
+## Options
+
+```jsonc
+// .eslintrc.json
+{
+  "rules": {
+    "@typescript-eslint/no-duplicate-enum-values": "warn"
+  }
+}
+```
+
+This rule is not configurable.

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

@@ -1,11 +1,17 @@
-# Disallow duplicate imports (`no-duplicate-imports`)
+# `no-duplicate-imports`
+
+Disallows duplicate imports.
+
+## DEPRECATED
+
+This rule has been deprecated in favour of the [`import/no-duplicates`](https://github.com/import-js/eslint-plugin-import/blob/HEAD/docs/rules/no-duplicates.md) rule.
 
 ## Rule Details
 
 This rule extends the base [`eslint/no-duplicate-imports`](https://eslint.org/docs/rules/no-duplicate-imports) rule.
 This version adds support for type-only import and export.
 
-## How to use
+## How to Use
 
 ```jsonc
 {
@@ -19,10 +25,8 @@ This version adds support for type-only import and export.
 
 See [`eslint/no-duplicate-imports` options](https://eslint.org/docs/rules/no-duplicate-imports#options).
 
-<sup>Taken with ❤️ [from ESLint core](https://github.com/eslint/eslint/blob/master/docs/rules/no-duplicate-imports.md)</sup>
+<sup>
 
-## Attributes
+Taken with ❤️ [from ESLint core](https://github.com/eslint/eslint/blob/main/docs/rules/no-duplicate-imports.md)
 
-- [ ] ✅ Recommended
-- [ ] 🔧 Fixable
-- [ ] 💭 Requires type information
+</sup>

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

@@ -1,4 +1,6 @@
-# Disallow the delete operator with computed key expressions (`no-dynamic-delete`)
+# `no-dynamic-delete`
+
+Disallows using the `delete` operator on computed key expressions.
 
 Deleting dynamically computed keys can be dangerous and in some cases not well optimized.
 
@@ -8,7 +10,22 @@ Using the `delete` operator on keys that aren't runtime constants could be a sig
 Using `Object`s with added and removed keys can cause occasional edge case bugs, such as if a key is named `"hasOwnProperty"`.
 Consider using a `Map` or `Set` if you’re storing collections of objects.
 
-Examples of **correct** code with this rule:
+<!--tabs-->
+
+### ❌ Incorrect
+
+```ts
+// Can be replaced with the constant equivalents, such as container.aaa
+delete container['aaa'];
+delete container['Infinity'];
+
+// Dynamic, difficult-to-reason-about lookups
+const name = 'name';
+delete container[name];
+delete container[name.toUpperCase()];
+```
+
+### ✅ Correct
 
 ```ts
 const container: { [i: string]: number } = {
@@ -23,19 +40,19 @@ delete container[7];
 delete container['-Infinity'];
 ```
 
-Examples of **incorrect** code with this rule:
+## Options
 
-```ts
-// Can be replaced with the constant equivalents, such as container.aaa
-delete container['aaa'];
-delete container['Infinity'];
-
-// Dynamic, difficult-to-reason-about lookups
-const name = 'name';
-delete container[name];
-delete container[name.toUpperCase()];
+```jsonc
+// .eslintrc.json
+{
+  "rules": {
+    "@typescript-eslint/no-dynamic-delete": "warn"
+  }
+}
 ```
 
+This rule is not configurable.
+
 ## When Not To Use It
 
 When you know your keys are safe to delete, this rule can be unnecessary.
@@ -44,12 +61,6 @@ 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
+## Related To
 
 - TSLint: [no-dynamic-delete](https://palantir.github.io/tslint/rules/no-dynamic-delete)
-
-## Attributes
-
-- [ ] ✅ Recommended
-- [x] 🔧 Fixable
-- [ ] 💭 Requires type information

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

@@ -1,4 +1,6 @@
-# Disallow empty functions (`no-empty-function`)
+# `no-empty-function`
+
+Disallows empty functions.
 
 ## Rule Details
 
@@ -7,7 +9,7 @@ It adds support for handling TypeScript specific code that would otherwise trigg
 
 One example of valid TypeScript specific code that would otherwise trigger the `no-empty-function` rule is the use of [parameter properties](https://www.typescriptlang.org/docs/handbook/classes.html#parameter-properties) in constructor functions.
 
-## How to use
+## How to Use
 
 ```jsonc
 {
@@ -26,7 +28,8 @@ This rule adds the following options:
 type AdditionalAllowOptionEntries =
   | 'private-constructors'
   | 'protected-constructors'
-  | 'decoratedFunctions';
+  | 'decoratedFunctions'
+  | 'overrideMethods';
 
 type AllowOptionEntries =
   | BaseNoEmptyFunctionAllowOptionEntries
@@ -75,7 +78,23 @@ class Foo {
 }
 ```
 
-## How to use
+### allow: `overrideMethods`
+
+Examples of correct code for the `{ "allow": ["overrideMethods"] }` option:
+
+```ts
+abstract class Base {
+  protected greet(): void {
+    console.log('Hello!');
+  }
+}
+
+class Foo extends Base {
+  protected override greet(): void {}
+}
+```
+
+## How to Use
 
 ```jsonc
 {
@@ -85,12 +104,8 @@ class Foo {
 }
 ```
 
----
-
-<sup>Taken with ❤️ [from ESLint core](https://github.com/eslint/eslint/blob/master/docs/rules/no-empty-function.md)</sup>
+<sup>
 
-## Attributes
+Taken with ❤️ [from ESLint core](https://github.com/eslint/eslint/blob/main/docs/rules/no-empty-function.md)
 
-- [x] ✅ Recommended
-- [ ] 🔧 Fixable
-- [ ] 💭 Requires type information
+</sup>

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

@@ -1,4 +1,6 @@
-# Disallow the declaration of empty interfaces (`no-empty-interface`)
+# `no-empty-interface`
+
+Disallows the declaration of empty interfaces.
 
 An empty interface is equivalent to its supertype. If the interface does not implement a supertype, then
 the interface is equivalent to an empty object (`{}`). In both cases it can be omitted.
@@ -7,7 +9,9 @@ the interface is equivalent to an empty object (`{}`). In both cases it can be o
 
 This rule aims to ensure that only meaningful interfaces are declared in the code.
 
-The following patterns are considered warnings:
+<!--tabs-->
+
+### ❌ Incorrect
 
 ```ts
 // an empty interface
@@ -20,7 +24,7 @@ interface Bar extends Foo {}
 interface Baz {}
 ```
 
-The following patterns are not warnings:
+### ✅ Correct
 
 ```ts
 // an interface with any number of members
@@ -38,6 +42,8 @@ interface Bar {
 interface Baz extends Foo, Bar {}
 ```
 
+<!--/tabs-->
+
 ### Options
 
 This rule accepts a single object option with the following default configuration:
@@ -59,12 +65,6 @@ This rule accepts a single object option with the following default configuratio
 
 If you don't care about having empty/meaningless interfaces, then you will not need this rule.
 
-## Compatibility
+## Related To
 
 - TSLint: [no-empty-interface](https://palantir.github.io/tslint/rules/no-empty-interface/)
-
-## Attributes
-
-- [x] ✅ Recommended
-- [x] 🔧 Fixable
-- [ ] 💭 Requires type information

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

@@ -1,4 +1,6 @@
-# Disallow usage of the `any` type (`no-explicit-any`)
+# `no-explicit-any`
+
+Disallows the `any` type.
 
 Using the `any` type defeats the purpose of using TypeScript.
 When `any` is used, all compiler type checks around that value are ignored.
@@ -11,7 +13,9 @@ TypeScript has a compiler flag for `--noImplicitAny` that will prevent
 an `any` type from being implied by the compiler, but doesn't prevent
 `any` from being explicitly used.
 
-The following patterns are considered warnings:
+<!--tabs-->
+
+### ❌ Incorrect
 
 ```ts
 const age: any = 'seventeen';
@@ -49,7 +53,7 @@ function greet(param: Array<any>): string {}
 function greet(param: Array<any>): Array<any> {}
 ```
 
-The following patterns are not warnings:
+### ✅ Correct
 
 ```ts
 const age: number = 17;
@@ -176,12 +180,6 @@ and you want to be able to specify `any`.
 
 - TypeScript [any type](https://www.typescriptlang.org/docs/handbook/basic-types.html#any)
 
-## Compatibility
+## Related To
 
 - TSLint: [no-any](https://palantir.github.io/tslint/rules/no-any/)
-
-## Attributes
-
-- [x] ✅ Recommended
-- [x] 🔧 Fixable
-- [ ] 💭 Requires type information