xo 0.48.0 → 0.51.0

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

@@ -1,6 +1,6 @@
 # `no-unnecessary-qualifier`
 
-Warns when a namespace qualifier is unnecessary.
+Disallows unnecessary namespace qualifiers.
 
 ## Rule Details
 
@@ -76,16 +76,19 @@ namespace X {
 }
 ```
 
-## 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.
+## Options
 
-## Related To
+```jsonc
+// .eslintrc.json
+{
+  "rules": {
+    "@typescript-eslint/no-unnecessary-qualifier": "warn"
+  }
+}
+```
 
-- TSLint: [no-unnecessary-qualifier](https://palantir.github.io/tslint/rules/no-unnecessary-qualifier/)
+This rule is not configurable.
 
-## Attributes
+## When Not To Use It
 
-- [ ] ✅ Recommended
-- [x] 🔧 Fixable
-- [x] 💭 Requires type information
+If you don't care about having unneeded namespace or enum qualifiers, then you don't need to use this rule.

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

@@ -1,6 +1,6 @@
 # `no-unnecessary-type-arguments`
 
-Enforces that type arguments will not be used if not required.
+Disallows type arguments that are equal to the default.
 
 Warns if an explicitly specified type argument is the default for that type parameter.
 
@@ -54,12 +54,15 @@ interface I<T = number> {}
 class Impl implements I<string> {}
 ```
 
-## Related To
+## Options
 
-- TSLint: [use-default-type-parameter](https://palantir.github.io/tslint/rules/use-default-type-parameter)
-
-## Attributes
+```jsonc
+// .eslintrc.json
+{
+  "rules": {
+    "@typescript-eslint/no-unnecessary-type-arguments": "warn"
+  }
+}
+```
 
-- [ ] ✅ Recommended
-- [x] 🔧 Fixable
-- [x] 💭 Requires type information
+This rule is not configurable.

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

@@ -1,6 +1,6 @@
 # `no-unnecessary-type-assertion`
 
-Warns if a type assertion does not change the type of an expression.
+Disallows type assertions that do not change the type of an expression.
 
 This rule prohibits using a type assertion that does not change the type of an expression.
 
@@ -73,13 +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/)
-
-## Attributes
-
-- [x] ✅ Recommended
-- [x] 🔧 Fixable
-- [x] 💭 Requires type information

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

@@ -72,9 +72,3 @@ This rule is not configurable.
 ## When Not To Use It
 
 If you don't care about the specific styles of your type constraints, or never use them in the first place, then you will not need this rule.
-
-## Attributes
-
-- [x] ✅ Recommended
-- [x] 🔧 Fixable
-- [ ] 💭 Requires type information

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

@@ -1,6 +1,6 @@
 # `no-unsafe-argument`
 
-Disallows calling a function with an any type value.
+Disallows calling a function with a value with type `any`.
 
 Despite your best intentions, the `any` type can sometimes leak into your codebase.
 Call a function with `any` typed argument are not checked at all by TypeScript, so it creates a potential safety hole, and source of bugs in your codebase.
@@ -87,10 +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/)
-
-## Attributes
-
-- [x] ✅ Recommended
-- [ ] 🔧 Fixable
-- [x] 💭 Requires type information

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

@@ -1,6 +1,6 @@
 # `no-unsafe-assignment`
 
-Disallows assigning any to variables and properties.
+Disallows assigning a value with type `any` to variables and properties.
 
 Despite your best intentions, the `any` type can sometimes leak into your codebase.
 Assigning an `any` typed value to a variable can be hard to pick up on, particularly if it leaks in from an external library. Operations on the variable will not be checked at all by TypeScript, so it creates a potential safety hole, and source of bugs in your codebase.
@@ -90,10 +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/)
-
-## Attributes
-
-- [x] ✅ Recommended
-- [ ] 🔧 Fixable
-- [x] 💭 Requires type information

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

@@ -1,6 +1,6 @@
 # `no-unsafe-call`
 
-Disallows calling an any type value.
+Disallows calling a value with type `any`.
 
 Despite your best intentions, the `any` type can sometimes leak into your codebase.
 The arguments to, and return value of calling an `any` typed variable are not checked at all by TypeScript, so it creates a potential safety hole, and source of bugs in your codebase.
@@ -64,10 +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/)
-
-## Attributes
-
-- [x] ✅ Recommended
-- [ ] 🔧 Fixable
-- [x] 💭 Requires type information

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

@@ -1,6 +1,6 @@
 # `no-unsafe-member-access`
 
-Disallows member access on any typed variables.
+Disallows member access on a value with type `any`.
 
 Despite your best intentions, the `any` type can sometimes leak into your codebase.
 Member access on `any` typed variables is not checked at all by TypeScript, so it creates a potential safety hole, and source of bugs in your codebase.
@@ -70,10 +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/)
-
-## Attributes
-
-- [x] ✅ Recommended
-- [ ] 🔧 Fixable
-- [x] 💭 Requires type information

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

@@ -1,6 +1,6 @@
 # `no-unsafe-return`
 
-Disallows returning any from a function.
+Disallows returning a value with type `any` from a function.
 
 Despite your best intentions, the `any` type can sometimes leak into your codebase.
 Returned `any` typed values are not checked at all by TypeScript, so it creates a potential safety hole, and source of bugs in your codebase.
@@ -107,10 +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/)
-
-## Attributes
-
-- [x] ✅ Recommended
-- [ ] 🔧 Fixable
-- [x] 💭 Requires type information

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

@@ -1,6 +1,6 @@
 # `no-unused-expressions`
 
-Disallow unused expressions.
+Disallows unused expressions.
 
 ## Rule Details
 
@@ -26,9 +26,3 @@ See [`eslint/no-unused-expressions` options](https://eslint.org/docs/rules/no-un
 Taken with ❤️ [from ESLint core](https://github.com/eslint/eslint/blob/main/docs/rules/no-unused-expressions.md)
 
 </sup>
-
-## Attributes
-
-- [ ] ✅ Recommended
-- [ ] 🔧 Fixable
-- [ ] 💭 Requires type information

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

@@ -1,6 +1,6 @@
 # `no-unused-vars`
 
-Disallow unused variables.
+Disallows unused variables.
 
 ## Rule Details
 
@@ -26,9 +26,3 @@ See [`eslint/no-unused-vars` options](https://eslint.org/docs/rules/no-unused-va
 Taken with ❤️ [from ESLint core](https://github.com/eslint/eslint/blob/main/docs/rules/no-unused-vars.md)
 
 </sup>
-
-## Attributes
-
-- [x] ✅ Recommended
-- [ ] 🔧 Fixable
-- [ ] 💭 Requires type information

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-use-before-define.md

@@ -1,6 +1,6 @@
 # `no-use-before-define`
 
-Disallow the use of variables before they are defined.
+Disallows the use of variables before they are defined.
 
 ## Rule Details
 
@@ -112,9 +112,3 @@ See [`eslint/no-use-before-define` options](https://eslint.org/docs/rules/no-use
 Taken with ❤️ [from ESLint core](https://github.com/eslint/eslint/blob/main/docs/rules/no-use-before-define.md)
 
 </sup>
-
-## Attributes
-
-- [ ] ✅ Recommended
-- [ ] 🔧 Fixable
-- [ ] 💭 Requires type information

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

@@ -1,6 +1,6 @@
 # `no-useless-constructor`
 
-Disallow unnecessary constructors.
+Disallows unnecessary constructors.
 
 ## Rule Details
 
@@ -35,9 +35,3 @@ Taken with ❤️ [from ESLint core](https://github.com/eslint/eslint/blob/main/
 
 This lint rule will report on constructors whose sole purpose is to change visibility of a parent constructor.
 See [discussion on this rule's lack of type information](https://github.com/typescript-eslint/typescript-eslint/issues/3820#issuecomment-917821240) for context.
-
-## Attributes
-
-- [ ] ✅ Recommended
-- [ ] 🔧 Fixable
-- [ ] 💭 Requires type information

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

@@ -0,0 +1,52 @@
+# `no-useless-empty-export`
+
+Disallows empty exports that don't change anything in a module file.
+
+## Rule Details
+
+An empty `export {}` statement is sometimes useful in TypeScript code to turn a file that would otherwise be a script file into a module file.
+Per the TypeScript Handbook [Modules](https://www.typescriptlang.org/docs/handbook/modules.html) page:
+
+> In TypeScript, just as in ECMAScript 2015, any file containing a top-level import or export is considered a module.
+> Conversely, a file without any top-level import or export declarations is treated as a script whose contents are available in the global scope (and therefore to modules as well).
+
+However, an `export {}` statement does nothing if there are any other top-level import or export statements in a file.
+
+Examples of code for this rule:
+
+<!--tabs-->
+
+### ❌ Incorrect
+
+```ts
+export const value = 'Hello, world!';
+export {};
+```
+
+```ts
+import 'some-other-module';
+export {};
+```
+
+### ✅ Correct
+
+```ts
+export const value = 'Hello, world!';
+```
+
+```ts
+import 'some-other-module';
+```
+
+## Options
+
+```jsonc
+// .eslintrc.json
+{
+  "rules": {
+    "@typescript-eslint/no-useless-empty-export": "warn"
+  }
+}
+```
+
+This rule is not configurable.

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

@@ -1,6 +1,6 @@
 # `no-var-requires`
 
-Disallows the use of require statements except in import statements.
+Disallows `require` statements except in import statements.
 
 In other words, the use of forms such as `var foo = require("foo")` are banned. Instead use ES6 style imports or `import foo = require("foo")` imports.
 
@@ -42,13 +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/)
-
-## Attributes
-
-- [x] ✅ Recommended
-- [ ] 🔧 Fixable
-- [ ] 💭 Requires type information

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/non-nullable-type-assertion-style.md

@@ -1,6 +1,6 @@
 # `non-nullable-type-assertion-style`
 
-Prefers a non-null assertion over explicit type cast when possible.
+Enforces non-null assertions over explicit type casts.
 
 This rule detects when an `as` cast is doing the same job as a `!` would, and suggests fixing the code to be an `!`.
 
@@ -28,12 +28,19 @@ const definitely = maybe!;
 const alsoDefinitely = maybe!;
 ```
 
-## When Not To Use It
+## Options
 
-If you don't mind having unnecessarily verbose type casts, you can avoid this rule.
+```jsonc
+// .eslintrc.json
+{
+  "rules": {
+    "@typescript-eslint/non-nullable-type-assertion-style": "warn"
+  }
+}
+```
 
-## Attributes
+This rule is not configurable.
 
-- [ ] ✅ Recommended
-- [x] 🔧 Fixable
-- [x] 💭 Requires type information
+## When Not To Use It
+
+If you don't mind having unnecessarily verbose type casts, you can avoid this rule.

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/object-curly-spacing.md

@@ -1,6 +1,6 @@
 # `object-curly-spacing`
 
-Enforce consistent spacing inside braces.
+Enforces consistent spacing inside braces.
 
 ## Rule Details
 
@@ -26,9 +26,3 @@ See [`eslint/object-curly-spacing` options](https://eslint.org/docs/rules/object
 Taken with ❤️ [from ESLint core](https://github.com/eslint/eslint/blob/main/docs/rules/object-curly-spacing.md)
 
 </sup>
-
-## Attributes
-
-- [ ] ✅ Recommended
-- [x] 🔧 Fixable
-- [ ] 💭 Requires type information

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/padding-line-between-statements.md

@@ -1,6 +1,6 @@
 # `padding-line-between-statements`
 
-require or disallow padding lines between statements.
+Requires or disallows padding lines between statements.
 
 ## Rule Details
 
@@ -54,9 +54,3 @@ In addition to options provided by ESLint, `interface` and `type` can be used as
 Taken with ❤️ [from ESLint core](https://github.com/eslint/eslint/blob/main/docs/rules/padding-line-between-statements.md)
 
 </sup>
-
-## Attributes
-
-- [ ] ✅ Recommended
-- [x] 🔧 Fixable
-- [ ] 💭 Requires type information