xo 0.53.0 → 0.54.0

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

@@ -0,0 +1,12 @@
+---
+description: 'Enforce consistent spacing between property names and type annotations in types and interfaces.'
+---
+
+> 🛑 This file is source code, not the primary documentation location! 🛑
+>
+> See **https://typescript-eslint.io/rules/key-spacing** for documentation.
+
+## Examples
+
+This rule extends the base [`eslint/key-spacing`](https://eslint.org/docs/rules/key-spacing) rule.
+This version adds support for type annotations on interfaces, classes and type literals properties.

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/lines-around-comment.md

@@ -0,0 +1,37 @@
+---
+description: 'Require empty lines around comments.'
+---
+
+> 🛑 This file is source code, not the primary documentation location! 🛑
+>
+> See **https://typescript-eslint.io/rules/lines-around-comment** for documentation.
+
+## Rule Details
+
+This rule extends the base [`eslint/lines-around-comment`](https://eslint.org/docs/rules/lines-around-comment) rule.
+It adds support for TypeScript syntax.
+
+See the [ESLint documentation](https://eslint.org/docs/rules/lines-around-comment) for more details on the `comma-dangle` rule.
+
+## Rule Changes
+
+```jsonc
+{
+  // note you must disable the base rule as it can report incorrect errors
+  "lines-around-comment": "off",
+  "@typescript-eslint/lines-around-comment": ["error"]
+}
+```
+
+## Options
+
+In addition to the options supported by the `lines-around-comment` rule in ESLint core, the rule adds the following options:
+
+- `allowEnumEnd: true` doesn't require a blank line after an enum body block end
+- `allowEnumStart: true` doesn't require a blank line before an enum body block start
+- `allowInterfaceEnd: true` doesn't require a blank line before an interface body block end
+- `allowInterfaceStart: true` doesn't require a blank line after an interface body block start
+- `allowModuleEnd: true` doesn't require a blank line before a module body block end
+- `allowModuleStart: true` doesn't require a blank line after a module body block start
+- `allowTypeEnd: true` doesn't require a blank line before a type literal block end
+- `allowTypeStart: true` doesn't require a blank line after a type literal block start

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

@@ -24,6 +24,7 @@ type OrderConfig = MemberType[] | SortedOrderConfig | 'never';
 
 interface SortedOrderConfig {
   memberTypes?: MemberType[] | 'never';
+  optionalityOrder?: 'optional-first' | 'required-first';
   order:
     | 'alphabetically'
     | 'alphabetically-case-insensitive'
@@ -44,9 +45,10 @@ You can configure `OrderConfig` options for:
 - **`interfaces`**?: override ordering specifically for interfaces
 - **`typeLiterals`**?: override ordering specifically for type literals
 
-The `OrderConfig` settings for each kind of construct may configure sorting on one or both two levels:
+The `OrderConfig` settings for each kind of construct may configure sorting on up to three levels:
 
 - **`memberTypes`**: organizing on member type groups such as methods vs. properties
+- **`optionalityOrder`**: whether to put all optional members first or all required members first
 - **`order`**: organizing based on member names, such as alphabetically
 
 ### Groups
@@ -54,9 +56,9 @@ The `OrderConfig` settings for each kind of construct may configure sorting on o
 You can define many different groups based on different attributes of members.
 The supported member attributes are, in order:
 
-- **Accessibility** (`'public' | 'protected' | 'private'`)
+- **Accessibility** (`'public' | 'protected' | 'private' | '#private'`)
 - **Decoration** (`'decorated'`): Whether the member has an explicit accessibility decorator
-- **Kind** (`'call-signature' | 'constructor' | 'field' | 'get' | 'method' | 'set' | 'signature'`)
+- **Kind** (`'call-signature' | 'constructor' | 'field' | 'readonly-field' | 'get' | 'method' | 'set' | 'signature' | 'readonly-signature'`)
 
 Member attributes may be joined with a `'-'` to combine into more specific groups.
 For example, `'public-field'` would come before `'private-field'`.
@@ -81,11 +83,13 @@ The default configuration looks as follows:
   "default": [
     // Index signature
     "signature",
+    "call-signature",
 
     // Fields
     "public-static-field",
     "protected-static-field",
     "private-static-field",
+    "#private-static-field",
 
     "public-decorated-field",
     "protected-decorated-field",
@@ -94,14 +98,15 @@ The default configuration looks as follows:
     "public-instance-field",
     "protected-instance-field",
     "private-instance-field",
+    "#private-instance-field",
 
     "public-abstract-field",
     "protected-abstract-field",
-    "private-abstract-field",
 
     "public-field",
     "protected-field",
     "private-field",
+    "#private-field",
 
     "static-field",
     "instance-field",
@@ -125,6 +130,7 @@ The default configuration looks as follows:
     "public-static-get",
     "protected-static-get",
     "private-static-get",
+    "#private-static-get",
 
     "public-decorated-get",
     "protected-decorated-get",
@@ -133,14 +139,15 @@ The default configuration looks as follows:
     "public-instance-get",
     "protected-instance-get",
     "private-instance-get",
+    "#private-instance-get",
 
     "public-abstract-get",
     "protected-abstract-get",
-    "private-abstract-get",
 
     "public-get",
     "protected-get",
     "private-get",
+    "#private-get",
 
     "static-get",
     "instance-get",
@@ -154,6 +161,7 @@ The default configuration looks as follows:
     "public-static-set",
     "protected-static-set",
     "private-static-set",
+    "#private-static-set",
 
     "public-decorated-set",
     "protected-decorated-set",
@@ -162,14 +170,15 @@ The default configuration looks as follows:
     "public-instance-set",
     "protected-instance-set",
     "private-instance-set",
+    "#private-instance-set",
 
     "public-abstract-set",
     "protected-abstract-set",
-    "private-abstract-set",
 
     "public-set",
     "protected-set",
     "private-set",
+    "#private-set",
 
     "static-set",
     "instance-set",
@@ -183,6 +192,7 @@ The default configuration looks as follows:
     "public-static-method",
     "protected-static-method",
     "private-static-method",
+    "#private-static-method",
 
     "public-decorated-method",
     "protected-decorated-method",
@@ -191,14 +201,15 @@ The default configuration looks as follows:
     "public-instance-method",
     "protected-instance-method",
     "private-instance-method",
+    "#private-instance-method",
 
     "public-abstract-method",
     "protected-abstract-method",
-    "private-abstract-method",
 
     "public-method",
     "protected-method",
     "private-method",
+    "#private-method",
 
     "static-method",
     "instance-method",
@@ -902,6 +913,96 @@ interface Foo {
 }
 ```
 
+#### Sorting Optional Members First or Last
+
+The `optionalityOrder` option may be enabled to place all optional members in a group at the beginning or end of that group.
+
+This config places all optional members before all required members:
+
+```jsonc
+// .eslintrc.json
+{
+  "rules": {
+    "@typescript-eslint/member-ordering": [
+      "error",
+      {
+        "default": {
+          "optionalityOrder": "optional-first",
+          "order": "alphabetically"
+        }
+      }
+    ]
+  }
+}
+```
+
+<!--tabs-->
+
+##### ❌ Incorrect
+
+```ts
+interface Foo {
+  a: boolean;
+  b?: number;
+  c: string;
+}
+```
+
+##### ✅ Correct
+
+```ts
+interface Foo {
+  b?: number;
+  a: boolean;
+  c: string;
+}
+```
+
+<!--/tabs-->
+
+This config places all required members before all optional members:
+
+```jsonc
+// .eslintrc.json
+{
+  "rules": {
+    "@typescript-eslint/member-ordering": [
+      "error",
+      {
+        "default": {
+          "optionalityOrder": "required-first",
+          "order": "alphabetically"
+        }
+      }
+    ]
+  }
+}
+```
+
+<!--tabs-->
+
+##### ❌ Incorrect
+
+```ts
+interface Foo {
+  a: boolean;
+  b?: number;
+  c: string;
+}
+```
+
+##### ✅ Correct
+
+```ts
+interface Foo {
+  a: boolean;
+  c: string;
+  b?: number;
+}
+```
+
+<!--/tabs-->
+
 ## All Supported Options
 
 ### Member Types (Granular Form)
@@ -913,20 +1014,60 @@ The most explicit and granular form is the following:
 [
   // Index signature
   "signature",
+  "readonly-signature",
 
   // Fields
   "public-static-field",
+  "public-static-readonly-field",
   "protected-static-field",
+  "protected-static-readonly-field",
   "private-static-field",
+  "private-static-readonly-field",
+  "#private-static-field",
+  "#private-static-readonly-field",
+
   "public-decorated-field",
+  "public-decorated-readonly-field",
   "protected-decorated-field",
+  "protected-decorated-readonly-field",
   "private-decorated-field",
+  "private-decorated-readonly-field",
+
   "public-instance-field",
+  "public-instance-readonly-field",
   "protected-instance-field",
+  "protected-instance-readonly-field",
   "private-instance-field",
+  "private-instance-readonly-field",
+  "#private-instance-field",
+  "#private-instance-readonly-field",
+
   "public-abstract-field",
+  "public-abstract-readonly-field",
   "protected-abstract-field",
-  "private-abstract-field",
+  "protected-abstract-readonly-field",
+
+  "public-field",
+  "public-readonly-field",
+  "protected-field",
+  "protected-readonly-field",
+  "private-field",
+  "private-readonly-field"
+  "#private-field",
+  "#private-readonly-field"
+
+  "static-field",
+  "static-readonly-field",
+  "instance-field",
+  "instance-readonly-field"
+  "abstract-field",
+  "abstract-readonly-field",
+
+  "decorated-field",
+  "decorated-readonly-field",
+
+  "field",
+  "readonly-field",
 
   // Static initialization
   "static-initialization",
@@ -940,6 +1081,7 @@ The most explicit and granular form is the following:
   "public-static-get",
   "protected-static-get",
   "private-static-get",
+  "#private-static-get",
 
   "public-decorated-get",
   "protected-decorated-get",
@@ -948,14 +1090,15 @@ The most explicit and granular form is the following:
   "public-instance-get",
   "protected-instance-get",
   "private-instance-get",
+  "#private-instance-get",
 
   "public-abstract-get",
   "protected-abstract-get",
-  "private-abstract-get",
 
   "public-get",
   "protected-get",
   "private-get",
+  "#private-get",
 
   "static-get",
   "instance-get",
@@ -969,6 +1112,7 @@ The most explicit and granular form is the following:
   "public-static-set",
   "protected-static-set",
   "private-static-set",
+  "#private-static-set",
 
   "public-decorated-set",
   "protected-decorated-set",
@@ -977,10 +1121,10 @@ The most explicit and granular form is the following:
   "public-instance-set",
   "protected-instance-set",
   "private-instance-set",
+  "#private-instance-set",
 
   "public-abstract-set",
   "protected-abstract-set",
-  "private-abstract-set",
 
   "public-set",
   "protected-set",
@@ -998,15 +1142,16 @@ The most explicit and granular form is the following:
   "public-static-method",
   "protected-static-method",
   "private-static-method",
+  "#private-static-method",
   "public-decorated-method",
   "protected-decorated-method",
   "private-decorated-method",
   "public-instance-method",
   "protected-instance-method",
   "private-instance-method",
+  "#private-instance-method",
   "public-abstract-method",
-  "protected-abstract-method",
-  "private-abstract-method"
+  "protected-abstract-method"
 ]
 ```
 
@@ -1110,7 +1255,7 @@ Another option is to group the member types by their scope (`public`, `protected
   // Fields
   "static-field", // = ["public-static-field", "protected-static-field", "private-static-field"]
   "instance-field", // = ["public-instance-field", "protected-instance-field", "private-instance-field"]
-  "abstract-field", // = ["public-abstract-field", "protected-abstract-field", "private-abstract-field"]
+  "abstract-field", // = ["public-abstract-field", "protected-abstract-field"]
 
   // Static initialization
   // No scope for static initialization.
@@ -1121,17 +1266,17 @@ Another option is to group the member types by their scope (`public`, `protected
   // Getters
   "static-get", // = ["public-static-get", "protected-static-get", "private-static-get"]
   "instance-get", // = ["public-instance-get", "protected-instance-get", "private-instance-get"]
-  "abstract-get", // = ["public-abstract-get", "protected-abstract-get", "private-abstract-get"]
+  "abstract-get", // = ["public-abstract-get", "protected-abstract-get"]
 
   // Setters
   "static-set", // = ["public-static-set", "protected-static-set", "private-static-set"]
   "instance-set", // = ["public-instance-set", "protected-instance-set", "private-instance-set"]
-  "abstract-set", // = ["public-abstract-set", "protected-abstract-set", "private-abstract-set"]
+  "abstract-set", // = ["public-abstract-set", "protected-abstract-set"]
 
   // Methods
   "static-method", // = ["public-static-method", "protected-static-method", "private-static-method"]
   "instance-method", // = ["public-instance-method", "protected-instance-method", "private-instance-method"]
-  "abstract-method" // = ["public-abstract-method", "protected-abstract-method", "private-abstract-method"]
+  "abstract-method" // = ["public-abstract-method", "protected-abstract-method"]
 ]
 ```
 
@@ -1146,7 +1291,7 @@ The third grouping option is to ignore both scope and accessibility.
 
   // Fields
   "field", // = ["public-static-field", "protected-static-field", "private-static-field", "public-instance-field", "protected-instance-field", "private-instance-field",
-  //              "public-abstract-field", "protected-abstract-field", private-abstract-field"]
+  //              "public-abstract-field", "protected-abstract-field"]
 
   // Static initialization
   // No grouping for static initialization.
@@ -1156,15 +1301,31 @@ The third grouping option is to ignore both scope and accessibility.
 
   // Getters
   "get", // = ["public-static-get", "protected-static-get", "private-static-get", "public-instance-get", "protected-instance-get", "private-instance-get",
-  //                "public-abstract-get", "protected-abstract-get", "private-abstract-get"]
+  //                "public-abstract-get", "protected-abstract-get"]
 
   // Setters
   "set", // = ["public-static-set", "protected-static-set", "private-static-set", "public-instance-set", "protected-instance-set", "private-instance-set",
-  //                "public-abstract-set", "protected-abstract-set", "private-abstract-set"]
+  //                "public-abstract-set", "protected-abstract-set"]
 
   // Methods
   "method" // = ["public-static-method", "protected-static-method", "private-static-method", "public-instance-method", "protected-instance-method", "private-instance-method",
-  //                "public-abstract-method", "protected-abstract-method", "private-abstract-method"]
+  //                "public-abstract-method", "protected-abstract-method"]
+]
+```
+
+### Member Group Types (Readonly Fields)
+
+It is possible to group fields by their `readonly` modifiers.
+
+```jsonc
+[
+  // Index signature
+  "readonly-signature",
+  "signature",
+
+  // Fields
+  "readonly-field", // = ["public-static-readonly-field", "protected-static-readonly-field", "private-static-readonly-field", "public-instance-readonly-field", "protected-instance-readonly-field", "private-instance-readonly-field", "public-abstract-readonly-field", "protected-abstract-readonly-field"]
+  "field" // = ["public-static-field", "protected-static-field", "private-static-field", "public-instance-field", "protected-instance-field", "private-instance-field", "public-abstract-field", "protected-abstract-field"]
 ]
 ```
 

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

@@ -159,7 +159,7 @@ If these are provided, the identifier must start with one of the provided values
   - Accepts one or array of selectors to define an option block that applies to one or multiple selectors.
   - For example, if you provide `{ selector: ['function', 'variable'] }`, then it will apply the same option to variable and function nodes.
   - See [Allowed Selectors, Modifiers and Types](#allowed-selectors-modifiers-and-types) below for the complete list of allowed selectors.
-- `modifiers` allows you to specify which modifiers to granularly apply to, such as the accessibility (`private`/`protected`/`public`), or if the thing is `static`, etc.
+- `modifiers` allows you to specify which modifiers to granularly apply to, such as the accessibility (`#private`/`private`/`protected`/`public`), or if the thing is `static`, etc.
   - The name must match _all_ of the modifiers.
   - For example, if you provide `{ modifiers: ['private','readonly','static'] }`, then it will only match something that is `private static readonly`, and something that is just `private` will not match.
   - The following `modifiers` are allowed:
@@ -172,6 +172,7 @@ If these are provided, the identifier must start with one of the provided values
     - `requiresQuotes` - matches any name that requires quotes as it is not a valid identifier (i.e. has a space, a dash, etc in it).
     - `public` - matches any member that is either explicitly declared as `public`, or has no visibility modifier (i.e. implicitly public).
     - `abstract`,`override`,`private`,`protected`,`readonly`,`static` - matches any member explicitly declared with the given modifier.
+    - `#private` - matches any member with a private identifier (an identifier that starts with `#`)
     - `async` - matches any method, function, or function variable which is async via the `async` keyword (e.g. does not match functions that return promises without using `async` keyword)
 - `types` allows you to specify which types to match. This option supports simple, primitive types only (`array`,`boolean`,`function`,`number`,`string`).
   - The name must match _one_ of the types.
@@ -204,7 +205,7 @@ Individual Selectors match specific, well-defined sets. There is no overlap betw
   - Allowed `modifiers`: `destructured`, `unused`.
   - Allowed `types`: `boolean`, `string`, `number`, `function`, `array`.
 - `classProperty` - matches any class property. Does not match properties that have direct function expression or arrow function expression values.
-  - Allowed `modifiers`: `abstract`, `override`, `private`, `protected`, `public`, `readonly`, `requiresQuotes`, `static`.
+  - Allowed `modifiers`: `abstract`, `override`, `#private`, `private`, `protected`, `public`, `readonly`, `requiresQuotes`, `static`.
   - Allowed `types`: `array`, `boolean`, `function`, `number`, `string`.
 - `objectLiteralProperty` - matches any object literal property. Does not match properties that have direct function expression or arrow function expression values.
   - Allowed `modifiers`: `public`, `requiresQuotes`.
@@ -216,7 +217,7 @@ Individual Selectors match specific, well-defined sets. There is no overlap betw
   - Allowed `modifiers`: `private`, `protected`, `public`, `readonly`.
   - Allowed `types`: `array`, `boolean`, `function`, `number`, `string`.
 - `classMethod` - matches any class method. Also matches properties that have direct function expression or arrow function expression values. Does not match accessors.
-  - Allowed `modifiers`: `abstract`, `async`, `override`, `private`, `protected`, `public`, `requiresQuotes`, `static`.
+  - Allowed `modifiers`: `abstract`, `async`, `override`, `#private`, `private`, `protected`, `public`, `requiresQuotes`, `static`.
   - Allowed `types`: none.
 - `objectLiteralMethod` - matches any object literal method. Also matches properties that have direct function expression or arrow function expression values. Does not match accessors.
   - Allowed `modifiers`: `async`, `public`, `requiresQuotes`.
@@ -257,16 +258,16 @@ Group Selectors are provided for convenience, and essentially bundle up sets of
   - Allowed `modifiers`: `async`, `unused`.
   - Allowed `types`: none.
 - `memberLike` - matches the same as `accessor`, `enumMember`, `method`, `parameterProperty`, `property`.
-  - Allowed `modifiers`: `abstract`, `async`, `override`, `private`, `protected`, `public`, `readonly`, `requiresQuotes`, `static`.
+  - Allowed `modifiers`: `abstract`, `async`, `override`, `#private`, `private`, `protected`, `public`, `readonly`, `requiresQuotes`, `static`.
   - Allowed `types`: none.
 - `typeLike` - matches the same as `class`, `enum`, `interface`, `typeAlias`, `typeParameter`.
   - Allowed `modifiers`: `abstract`, `unused`.
   - Allowed `types`: none.
 - `property` - matches the same as `classProperty`, `objectLiteralProperty`, `typeProperty`.
-  - Allowed `modifiers`: `abstract`, `async`, `override`, `private`, `protected`, `public`, `readonly`, `requiresQuotes`, `static`.
+  - Allowed `modifiers`: `abstract`, `async`, `override`, `#private`, `private`, `protected`, `public`, `readonly`, `requiresQuotes`, `static`.
   - Allowed `types`: `array`, `boolean`, `function`, `number`, `string`.
 - `method` - matches the same as `classMethod`, `objectLiteralMethod`, `typeMethod`.
-  - Allowed `modifiers`: `abstract`, `async`, `override`, `private`, `protected`, `public`, `readonly`, `requiresQuotes`, `static`.
+  - Allowed `modifiers`: `abstract`, `async`, `override`, `#private`, `private`, `protected`, `public`, `readonly`, `requiresQuotes`, `static`.
   - Allowed `types`: none.
 
 ## FAQ

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

@@ -0,0 +1,61 @@
+---
+description: 'Disallow duplicate constituents of union or intersection types.'
+---
+
+> 🛑 This file is source code, not the primary documentation location! 🛑
+>
+> See **https://typescript-eslint.io/rules/no-duplicate-type-constituents** for documentation.
+
+TypeScript supports types ("constituents") within union and intersection types being duplicates of each other.
+However, developers typically expect each constituent to be unique within its intersection or union.
+Duplicate values make the code overly verbose and generally reduce readability.
+
+## Rule Details
+
+This rule disallows duplicate union or intersection constituents.
+We consider types to be duplicate if they evaluate to the same result in the type system.
+For example, given `type A = string` and `type T = string | A`, this rule would flag that `A` is the same type as `string`.
+
+<!--tabs-->
+
+### ❌ Incorrect
+
+```ts
+type T1 = 'A' | 'A';
+
+type T2 = A | A | B;
+
+type T3 = { a: string } & { a: string };
+
+type T4 = [1, 2, 3] | [1, 2, 3];
+
+type StringA = string;
+type StringB = string;
+type T5 = StringA | StringB;
+```
+
+### ✅ Correct
+
+```ts
+type T1 = 'A' | 'B';
+
+type T2 = A | B | C;
+
+type T3 = { a: string } & { b: string };
+
+type T4 = [1, 2, 3] | [1, 2, 3, 4];
+
+type StringA = string;
+type NumberB = number;
+type T5 = StringA | NumberB;
+```
+
+## Options
+
+### `ignoreIntersections`
+
+When set to true, duplicate checks on intersection type constituents are ignored.
+
+### `ignoreUnions`
+
+When set to true, duplicate checks on union type constituents are ignored.

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

@@ -42,7 +42,7 @@ interface Bar {
 }
 
 // an interface with more than one supertype
-// in this case the interface can be used as a replacement of a union type.
+// in this case the interface can be used as a replacement of an intersection type.
 interface Baz extends Foo, Bar {}
 ```
 

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-import-type-side-effects.md

@@ -0,0 +1,75 @@
+---
+description: 'Enforce the use of top-level import type qualifier when an import only has specifiers with inline type qualifiers.'
+---
+
+> 🛑 This file is source code, not the primary documentation location! 🛑
+>
+> See **https://typescript-eslint.io/rules/no-import-type-side-effects** for documentation.
+
+The [`--verbatimModuleSyntax`](https://www.typescriptlang.org/tsconfig#verbatimModuleSyntax) compiler option causes TypeScript to do simple and predictable transpilation on import declarations.
+Namely, it completely removes import declarations with a top-level `type` qualifier, and it removes any import specifiers with an inline `type` qualifier.
+
+The latter behavior does have one potentially surprising effect in that in certain cases TS can leave behind a "side effect" import at runtime:
+
+```ts
+import { type A, type B } from 'mod';
+
+// is transpiled to
+
+import {} from 'mod';
+// which is the same as
+import 'mod';
+```
+
+For the rare case of needing to import for side effects, this may be desirable - but for most cases you will not want to leave behind an unnecessary side effect import.
+
+## Examples
+
+This rule enforces that you use a top-level `type` qualifier for imports when it only imports specifiers with an inline `type` qualifier
+
+<!--tabs-->
+
+### ❌ Incorrect
+
+```ts
+import { type A } from 'mod';
+import { type A as AA } from 'mod';
+import { type A, type B } from 'mod';
+import { type A as AA, type B as BB } from 'mod';
+```
+
+### ✅ Correct
+
+```ts
+import type { A } from 'mod';
+import type { A as AA } from 'mod';
+import type { A, B } from 'mod';
+import type { A as AA, B as BB } from 'mod';
+
+import T from 'mod';
+import type T from 'mod';
+
+import * as T from 'mod';
+import type * as T from 'mod';
+
+import { T } from 'mod';
+import type { T } from 'mod';
+import { T, U } from 'mod';
+import type { T, U } from 'mod';
+import { type T, U } from 'mod';
+import { T, type U } from 'mod';
+
+import type T, { U } from 'mod';
+import T, { type U } from 'mod';
+```
+
+## When Not To Use It
+
+- If you want to leave behind side effect imports, then you shouldn't use this rule.
+- If you're not using TypeScript 5.0's `verbatimModuleSyntax` option, then you don't need this rule.
+
+## Related To
+
+- [`consistent-type-imports`](./consistent-type-imports.md)
+- [`import/consistent-type-specifier-style`](https://github.com/import-js/eslint-plugin-import/blob/main/docs/rules/consistent-type-specifier-style.md)
+- [`import/no-duplicates` with `{"prefer-inline": true}`](https://github.com/import-js/eslint-plugin-import/blob/main/docs/rules/no-duplicates.md#inline-type-imports)