xo 0.50.0 → 0.52.1

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

@@ -1,6 +1,10 @@
-# `no-misused-promises`
+---
+description: 'Disallow Promises in places not designed to handle them.'
+---
 
-Disallows Promises in places not designed to handle them.
+> 🛑 This file is source code, not the primary documentation location! 🛑
+>
+> See **https://typescript-eslint.io/rules/no-misused-promises** for documentation.
 
 This rule forbids providing Promises to logical locations such as if statements in places where the TypeScript compiler allows them but they are not handled properly.
 These situations can often arise due to a missing `await` keyword or just a misunderstanding of the way async

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

@@ -1,6 +1,10 @@
-# `no-namespace`
+---
+description: 'Disallow custom TypeScript modules and namespaces.'
+---
 
-Disallows custom TypeScript modules and namespaces.
+> 🛑 This file is source code, not the primary documentation location! 🛑
+>
+> See **https://typescript-eslint.io/rules/no-namespace** for documentation.
 
 Custom TypeScript modules (`module foo {}`) and namespaces (`namespace foo {}`) are considered outdated
 ways to organize TypeScript code. ES2015 module syntax is now preferred (`import`/`export`).
@@ -11,16 +15,7 @@ This rule still allows the use of TypeScript module declarations to describe ext
 
 This rule aims to standardize the way modules are declared.
 
-## Options
-
-This rule, in its default state, does not require any argument. If you would like to enable one
-or more of the following you may pass an object with the options set as follows:
-
-- `allowDeclarations` set to `true` will allow you to `declare` custom TypeScript modules and namespaces (Default: `false`).
-- `allowDefinitionFiles` set to `true` will allow you to `declare` and use custom TypeScript modules and namespaces
-  inside definition files (Default: `true`).
-
-Examples of code for the default `{ "allowDeclarations": false, "allowDefinitionFiles": true }` options:
+Examples of code with the default options:
 
 <!--tabs-->
 
@@ -44,9 +39,11 @@ declare module 'foo' {}
 
 <!--/tabs-->
 
+## Options
+
 ### `allowDeclarations`
 
-Examples of code for the `{ "allowDeclarations": true }` option:
+Examples of code with the `{ "allowDeclarations": true }` option:
 
 <!--tabs-->
 
@@ -131,7 +128,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-asserted-nullish-coalescing.md

@@ -1,6 +1,10 @@
-# `no-non-null-asserted-nullish-coalescing`
+---
+description: 'Disallow non-null assertions in the left operand of a nullish coalescing operator.'
+---
 
-Disallows non-null assertions in the left operand of a nullish coalescing operator.
+> 🛑 This file is source code, not the primary documentation location! 🛑
+>
+> See **https://typescript-eslint.io/rules/no-non-null-asserted-nullish-coalescing** for documentation.
 
 ## Rule Details
 
@@ -45,19 +49,6 @@ let x: string;
 x! ?? '';
 ```
 
-## Options
-
-```jsonc
-// .eslintrc.json
-{
-  "rules": {
-    "@typescript-eslint/no-non-null-asserted-nullish-coalescing": "warn"
-  }
-}
-```
-
-This rule is not configurable.
-
 ## When Not To Use It
 
 If you are not using TypeScript 3.7 (or greater), then you will not need to use this rule, as the nullish coalescing operator is not supported.

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-non-null-asserted-optional-chain.md

@@ -1,6 +1,10 @@
-# `no-non-null-asserted-optional-chain`
+---
+description: 'Disallow non-null assertions after an optional chain expression.'
+---
 
-Disallows non-null assertions after an optional chain expression.
+> 🛑 This file is source code, not the primary documentation location! 🛑
+>
+> See **https://typescript-eslint.io/rules/no-non-null-asserted-optional-chain** for documentation.
 
 ## Rule Details
 
@@ -44,19 +48,6 @@ foo?.bar!();
 foo?.bar!().baz;
 ```
 
-## Options
-
-```jsonc
-// .eslintrc.json
-{
-  "rules": {
-    "@typescript-eslint/no-non-null-asserted-optional-chain": "error"
-  }
-}
-```
-
-This rule is not configurable.
-
 ## When Not To Use It
 
 If you are not using TypeScript 3.7 (or greater), then you will not need to use this rule, as the operator is not supported.

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

@@ -1,6 +1,10 @@
-# `no-non-null-assertion`
+---
+description: 'Disallow non-null assertions using the `!` postfix operator.'
+---
 
-Disallows non-null assertions using the `!` postfix operator.
+> 🛑 This file is source code, not the primary documentation location! 🛑
+>
+> See **https://typescript-eslint.io/rules/no-non-null-assertion** for documentation.
 
 ## Rule Details
 
@@ -32,23 +36,6 @@ const foo: Foo = getFoo();
 const includesBaz: boolean = foo.bar?.includes('baz') ?? false;
 ```
 
-## Options
-
-```jsonc
-// .eslintrc.json
-{
-  "rules": {
-    "@typescript-eslint/no-non-null-assertion": "warn"
-  }
-}
-```
-
-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

@@ -1,6 +1,15 @@
-# `no-parameter-properties`
+---
+description: 'Disallow the use of parameter properties in class constructors.'
+---
 
-Disallows the use of parameter properties in class constructors.
+> 🛑 This file is source code, not the primary documentation location! 🛑
+>
+> See **https://typescript-eslint.io/rules/no-parameter-properties** for documentation.
+
+:::danger Deprecated
+
+This rule has been deprecated in favour of the equivalent, better named [`parameter-properties`](./parameter-properties) rule.
+:::
 
 Parameter properties can be confusing to those new to TypeScript as they are less explicit than other ways
 of declaring and initializing class members.
@@ -395,7 +404,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-redeclare.md

@@ -1,25 +1,18 @@
-# `no-redeclare`
+---
+description: 'Disallow variable redeclaration.'
+---
 
-Disallows variable redeclaration.
+> 🛑 This file is source code, not the primary documentation location! 🛑
+>
+> See **https://typescript-eslint.io/rules/no-redeclare** for documentation.
 
 ## Rule Details
 
 This rule extends the base [`eslint/no-redeclare`](https://eslint.org/docs/rules/no-redeclare) rule.
 It adds support for TypeScript function overloads, and declaration merging.
 
-## How to Use
-
-```jsonc
-{
-  // note you must disable the base rule as it can report incorrect errors
-  "no-redeclare": "off",
-  "@typescript-eslint/no-redeclare": ["error"]
-}
-```
-
 ## Options
 
-See [`eslint/no-redeclare` options](https://eslint.org/docs/rules/no-redeclare#options).
 This rule adds the following options:
 
 ```ts
@@ -78,9 +71,3 @@ type something = string;
 // eslint-disable-next-line @typescript-eslint/no-redeclare -- intentionally naming the variable the same as the type
 const something = 2;
 ```
-
-<sup>
-
-Taken with ❤️ [from ESLint core](https://github.com/eslint/eslint/blob/main/docs/rules/no-redeclare.md)
-
-</sup>

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

@@ -1,6 +1,10 @@
-# `no-redundant-type-constituents`
+---
+description: 'Disallow members of unions and intersections that do nothing or override type information.'
+---
 
-Disallows members of unions and intersections that do nothing or override type information.
+> 🛑 This file is source code, not the primary documentation location! 🛑
+>
+> See **https://typescript-eslint.io/rules/no-redundant-type-constituents** for documentation.
 
 ## Rule Details
 
@@ -66,19 +70,6 @@ type IntersectionStringLiteral = 'foo';
 type ReturnUnionNever = () => string | never;
 ```
 
-## Options
-
-```jsonc
-// .eslintrc.json
-{
-  "rules": {
-    "@typescript-eslint/no-redundant-type-constituents": "warn"
-  }
-}
-```
-
-This rule is not configurable.
-
 ## Limitations
 
 This rule plays it safe and only works with bottom types, top types, and comparing literal types to primitive types.

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

@@ -1,6 +1,10 @@
-# `no-require-imports`
+---
+description: 'Disallow invocation of `require()`.'
+---
 
-Disallows invocation of `require()`.
+> 🛑 This file is source code, not the primary documentation location! 🛑
+>
+> See **https://typescript-eslint.io/rules/no-require-imports** for documentation.
 
 Prefer the newer ES6-style imports over `require()`.
 
@@ -31,23 +35,6 @@ import lib9 = lib2.anotherSubImport;
 import lib10 from 'lib10';
 ```
 
-## Options
-
-```jsonc
-// .eslintrc.json
-{
-  "rules": {
-    "@typescript-eslint/no-require-imports": "warn"
-  }
-}
-```
-
-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-restricted-imports.md

@@ -1,24 +1,17 @@
-# `no-restricted-imports`
+---
+description: 'Disallow specified modules when loaded by `import`.'
+---
 
-Disallows specified modules when loaded by `import`.
+> 🛑 This file is source code, not the primary documentation location! 🛑
+>
+> See **https://typescript-eslint.io/rules/no-restricted-imports** for documentation.
 
 ## Rule Details
 
 This rule extends the base [`eslint/no-restricted-imports`](https://eslint.org/docs/rules/no-restricted-imports) rule.
 
-## How to Use
-
-```jsonc
-{
-  // note you must disable the base rule as it can report incorrect errors
-  "no-restricted-imports": "off",
-  "@typescript-eslint/no-restricted-imports": ["error"]
-}
-```
-
 ## Options
 
-See [`eslint/no-restricted-imports` options](https://eslint.org/docs/rules/no-restricted-imports#options).
 This rule adds the following options:
 
 ### `allowTypeImports`

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

@@ -1,25 +1,18 @@
-# `no-shadow`
+---
+description: 'Disallow variable declarations from shadowing variables declared in the outer scope.'
+---
 
-Disallows variable declarations from shadowing variables declared in the outer scope.
+> 🛑 This file is source code, not the primary documentation location! 🛑
+>
+> See **https://typescript-eslint.io/rules/no-shadow** for documentation.
 
 ## Rule Details
 
 This rule extends the base [`eslint/no-shadow`](https://eslint.org/docs/rules/no-shadow) rule.
 It adds support for TypeScript's `this` parameters and global augmentation, and adds options for TypeScript features.
 
-## How to Use
-
-```jsonc
-{
-  // note you must disable the base rule as it can report incorrect errors
-  "no-shadow": "off",
-  "@typescript-eslint/no-shadow": ["error"]
-}
-```
-
 ## Options
 
-See [`eslint/no-shadow` options](https://eslint.org/docs/rules/no-shadow#options).
 This rule adds the following options:
 
 ```ts
@@ -85,9 +78,3 @@ Examples of **correct** code with `{ ignoreFunctionTypeParameterNameValueShadow:
 const test = 1;
 type Func = (test: string) => typeof test;
 ```
-
-<sup>
-
-Taken with ❤️ [from ESLint core](https://github.com/eslint/eslint/blob/main/docs/rules/no-shadow.md)
-
-</sup>

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

@@ -1,33 +1,35 @@
-# `no-this-alias`
+---
+description: 'Disallow aliasing `this`.'
+---
 
-Disallows aliasing `this`.
+> 🛑 This file is source code, not the primary documentation location! 🛑
+>
+> See **https://typescript-eslint.io/rules/no-this-alias** for documentation.
 
 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:
 
@@ -37,26 +39,6 @@ Examples of **correct** code for this rule:
 
 (see the rationale above)
 
-## Options
-
-You can pass an object option:
-
-```jsonc
-{
-  "@typescript-eslint/no-this-alias": [
-    "error",
-    {
-      "allowDestructuring": false, // Disallow `const { props, state } = this`; true by default
-      "allowedNames": ["self"] // Allow `const self = this`; `[]` by default
-    }
-  ]
-}
-```
-
 ## 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-throw-literal.md

@@ -1,6 +1,10 @@
-# `no-throw-literal`
+---
+description: 'Disallow throwing literals as exceptions.'
+---
 
-Disallows throwing literals as exceptions.
+> 🛑 This file is source code, not the primary documentation location! 🛑
+>
+> See **https://typescript-eslint.io/rules/no-throw-literal** for documentation.
 
 It is considered good practice to only `throw` the `Error` object itself or an object using the `Error` object as base objects for user-defined exceptions.
 The fundamental benefit of `Error` objects is that they automatically keep track of where they were built and originated.
@@ -85,34 +89,26 @@ class CustomError extends Error {
 throw new CustomError();
 ```
 
-## How to Use
+## Options
 
-```jsonc
-{
-  // note you must disable the base rule as it can report incorrect errors
-  "no-throw-literal": "off",
-  "@typescript-eslint/no-throw-literal": ["error"]
-}
-```
+This rule adds the following options:
 
-### Options
-
-```jsonc
-{
-  "@typescript-eslint/no-throw-literal": [
-    "error",
-    {
-      "allowThrowingAny": true, // Default is to allow throwing values of type any
-      "allowThrowingUnknown": true // Default is to allow throwing values of type unknown
-    }
-  ]
+```ts
+interface Options extends BaseNoShadowOptions {
+  /**
+   * Whether to always allow throwing values typed as `any`.
+   */
+  allowThrowingAny?: boolean;
+
+  /**
+   * Whether to always allow throwing values typed as `unknown`.
+   */
+  allowThrowingUnknown?: boolean;
 }
-```
 
----
-
-<sup>
-
-Taken with ❤️ [from ESLint core](https://github.com/eslint/eslint/blob/main/docs/rules/no-throw-literal.md)
-
-</sup>
+const defaultOptions: Options = {
+  ...baseNoShadowDefaultOptions,
+  allowThrowingAny: false,
+  allowThrowingUnknown: false,
+};
+```

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

@@ -1,6 +1,10 @@
-# `no-type-alias`
+---
+description: 'Disallow type aliases.'
+---
 
-Disallows type aliases.
+> 🛑 This file is source code, not the primary documentation location! 🛑
+>
+> See **https://typescript-eslint.io/rules/no-type-alias** for documentation.
 
 In TypeScript, type aliases serve three purposes:
 
@@ -81,18 +85,6 @@ and simplified types (primitives, tuples, unions, intersections, etc).
 
 ## Options
 
-This rule, in its default state, does not require any argument. If you would like to enable one
-or more of the following you may pass an object with the options set as follows:
-
-- `allowAliases` set to `"always"` will allow you to do aliasing (Defaults to `"never"`).
-- `allowCallbacks` set to `"always"` will allow you to use type aliases with callbacks (Defaults to `"never"`)
-- `allowConditionalTypes` set to `"always"` will allow you to use type aliases with conditional types (Defaults to `"never"`)
-- `allowConstructors` set to `"always"` will allow you to use type aliases with constructors (Defaults to `"never"`)
-- `allowLiterals` set to `"always"` will allow you to use type aliases with literal objects (Defaults to `"never"`)
-- `allowMappedTypes` set to `"always"` will allow you to use type aliases as mapping tools (Defaults to `"never"`)
-- `allowTupleTypes` set to `"always"` will allow you to use type aliases with tuples (Defaults to `"never"`)
-- `allowGenerics` set to `"always"` will allow you to use type aliases with generics (Defaults to `"never"`)
-
 ### `allowAliases`
 
 This applies to primitive types and reference types.
@@ -608,7 +600,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

@@ -1,6 +1,10 @@
-# `no-unnecessary-boolean-literal-compare`
+---
+description: 'Disallow unnecessary equality comparisons against boolean literals.'
+---
 
-Disallows unnecessary equality comparisons against boolean literals.
+> 🛑 This file is source code, not the primary documentation location! 🛑
+>
+> See **https://typescript-eslint.io/rules/no-unnecessary-boolean-literal-compare** for documentation.
 
 Comparing boolean values to boolean literals is unnecessary, those comparisons result in the same booleans. Using the boolean values directly, or via a unary negation (`!value`), is more concise and clearer.
 
@@ -50,30 +54,10 @@ if (someStringBoolean === true) {
 
 ## Options
 
-The rule accepts an options object with the following properties.
-
-```ts
-type Options = {
-  // if false, comparisons between a nullable boolean variable to `true` will be checked and fixed
-  allowComparingNullableBooleansToTrue?: boolean;
-  // if false, comparisons between a nullable boolean variable to `false` will be checked and fixed
-  allowComparingNullableBooleansToFalse?: boolean;
-};
-```
-
-### Defaults
-
 This rule always checks comparisons between a boolean variable and a boolean
 literal. Comparisons between nullable boolean variables and boolean literals
 are **not** checked by default.
 
-```ts
-const defaults = {
-  allowComparingNullableBooleansToTrue: true,
-  allowComparingNullableBooleansToFalse: true,
-};
-```
-
 ### `allowComparingNullableBooleansToTrue`
 
 Examples of code for this rule with `{ allowComparingNullableBooleansToTrue: false }`:
@@ -146,7 +130,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-condition.md

@@ -1,6 +1,10 @@
-# `no-unnecessary-condition`
+---
+description: 'Disallow conditionals where the type is always truthy or always falsy.'
+---
 
-Disallows conditionals where the type is always truthy or always falsy.
+> 🛑 This file is source code, not the primary documentation location! 🛑
+>
+> See **https://typescript-eslint.io/rules/no-unnecessary-condition** for documentation.
 
 Any expression being used as a condition must be able to evaluate as truthy or falsy in order to be considered "necessary". Conversely, any expression that always evaluates to truthy or always evaluates to falsy, as determined by the type of the expression, is considered unnecessary and will be flagged by this rule.
 
@@ -70,20 +74,6 @@ function bar(arg?: string | null) {
 
 ## Options
 
-```ts
-type Options = {
-  // if true, the rule will ignore constant loop conditions
-  allowConstantLoopConditions?: boolean;
-  // if true, the rule will not error when running with a tsconfig that has strictNullChecks turned **off**
-  allowRuleToRunWithoutStrictNullChecksIKnowWhatIAmDoing?: boolean;
-};
-
-const defaultOptions: Options = {
-  allowConstantLoopConditions: false,
-  allowRuleToRunWithoutStrictNullChecksIKnowWhatIAmDoing: false,
-};
-```
-
 ### `allowConstantLoopConditions`
 
 Example of correct code for `{ allowConstantLoopConditions: true }`: