May 12, 2024 · Apr 23, 2024 · Apr 23, 2024 · Apr 23, 2024 · Apr 23, 2024 · Apr 24, 2024
diff --git a/packages/eslint-plugin/TSLINT_RULE_ALTERNATIVES.md b/packages/eslint-plugin/TSLINT_RULE_ALTERNATIVES.md
 | [`member-access`]                 | ✅  | [`@typescript-eslint/explicit-member-accessibility`] |
 | [`member-ordering`]               | ✅  | [`@typescript-eslint/member-ordering`]               |
 | [`no-any`]                        | ✅  | [`@typescript-eslint/no-explicit-any`]               |
 | [`no-empty-interface`]            | ✅  | [`@typescript-eslint/no-empty-interface`]          |
 | [`no-empty-interface`]            | ✅  | [`@typescript-eslint/no-empty-object-type`]          |
 | [`no-import-side-effect`]         | 🔌  | [`import/no-unassigned-import`]                      |
 | [`no-inferrable-types`]           | ✅  | [`@typescript-eslint/no-inferrable-types`]           |
 | [`no-internal-module`]            | ✅  | [`@typescript-eslint/prefer-namespace-keyword`]      |
 [`@typescript-eslint/member-ordering`]: https://typescript-eslint.io/rules/member-ordering
 [`@typescript-eslint/method-signature-style`]: https://typescript-eslint.io/rules/method-signature-style
 [`@typescript-eslint/no-explicit-any`]: https://typescript-eslint.io/rules/no-explicit-any
 [`@typescript-eslint/no-empty-interface`]: https://typescript-eslint.io/rules/no-empty-interface
 [`@typescript-eslint/no-empty-object-type`]: https://typescript-eslint.io/rules/no-empty-object-type
 [`@typescript-eslint/no-implied-eval`]: https://typescript-eslint.io/rules/no-implied-eval
 [`@typescript-eslint/no-inferrable-types`]: https://typescript-eslint.io/rules/no-inferrable-types
 [`@typescript-eslint/prefer-namespace-keyword`]: https://typescript-eslint.io/rules/prefer-namespace-keyword
diff --git a/packages/eslint-plugin/docs/rules/ban-types.mdx b/packages/eslint-plugin/docs/rules/ban-types.mdx
 // use safer object types
 const lowerObj: Object = {};
 const capitalObj: Object = { a: 'string' };

 const curly1: {} = 1;
 const curly2: {} = { a: 'string' };
 ```

 </TabItem>
 // use safer object types
 const lowerObj: object = {};
 const capitalObj: { a: string } = { a: 'string' };

 const curly1: number = 1;
 const curly2: Record<'a', string> = { a: 'string' };
 ```

 </TabItem>

 The default options provide a set of "best practices", intended to provide safety and standardization in your codebase:

 - Don't use the upper-case primitive types, you should use the lower-case types for consistency.
 - Don't use the upper-case primitive types or `Object`, you should use the lower-case types for consistency.
 - Avoid the `Function` type, as it provides little safety for the following reasons:
  - It provides no type safety when calling the value, which means it's easy to provide the wrong arguments.
  - It accepts class declarations, which will fail when called, as they are called without the `new` keyword.
 - Avoid the `Object` and `{}` types, as they mean "any non-nullish value".
  - This is a point of confusion for many developers, who think it means "any object type".
  - See [this comment for more information](https://github.com/typescript-eslint/typescript-eslint/issues/2063#issuecomment-675156492).

 <details>
 <summary>Default Options</summary>

 If your project is a rare one that intentionally deals with the class equivalents of primitives, it might not be worthwhile to enable the default `ban-types` options.
 You might consider using [ESLint disable comments](https://eslint.org/docs/latest/use/configure/rules#using-configuration-comments-1) for those specific situations instead of completely disabling this rule.

 ## Related To

 - [`no-empty-object-type`](./no-empty-object-type.mdx)
diff --git a/packages/eslint-plugin/docs/rules/no-empty-interface.mdx b/packages/eslint-plugin/docs/rules/no-empty-interface.mdx
 >
 > See **https://typescript-eslint.io/rules/no-empty-interface** for documentation.

 :::danger Deprecated

 This rule has been deprecated in favour of the more comprehensive [`@typescript-eslint/no-empty-object-type`](./no-empty-object-type.mdx) rule.

 :::

 An empty interface in TypeScript does very little: any non-nullable value is assignable to `{}`.
 Using an empty interface is often a sign of programmer error, such as misunderstanding the concept of `{}` or forgetting to fill in fields.

 ## When Not To Use It

 If you don't care about having empty/meaningless interfaces, then you will not need this rule.

 ## Related To

 - [`no-empty-object-type`](./no-empty-object-type.mdx)
diff --git a/packages/eslint-plugin/docs/rules/no-empty-object-type.mdx b/packages/eslint-plugin/docs/rules/no-empty-object-type.mdx
 ---
 description: 'Disallow accidentally using the "empty object" type.'
 ---

 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';

 > 🛑 This file is source code, not the primary documentation location! 🛑
 >
 > See **https://typescript-eslint.io/rules/no-empty-object-type** for documentation.

 The `{}`, or "empty object" type in TypeScript is a common source of confusion for developers unfamiliar with TypeScript's structural typing.
 `{}` represents any _non-nullish value_, including literals like `0` and `""`:

 ```ts
 let anyNonNullishValue: {} = 'Intentionally allowed by TypeScript.';
 ```

 Often, developers writing `{}` actually mean either:

 - `object`: representing any _object_ value
 - `unknown`: representing any value at all, including `null` and `undefined`

 In other words, the "empty object" type `{}` really means _"any value that is defined"_.
 That includes arrays, class instances, functions, and primitives such as `string` and `symbol`.

 To avoid confusion around the `{}` type allowing any _non-nullish value_, this rule bans usage of the `{}` type.
 That includes interfaces and object type aliases with no fields.

 :::tip
 If you do have a use case for an API allowing `{}`, you can always configure the [rule's options](#options), use an [ESLint disable comment](https://eslint.org/docs/latest/use/configure/rules#using-configuration-comments-1), or [disable the rule in your ESLint config](https://eslint.org/docs/latest/use/configure/rules#using-configuration-files-1).
 :::

 Note that this rule does not report on:

 - `{}` as a type constituent in an intersection type (e.g. types like TypeScript's built-in `type NonNullable<T> = T & {}`), as this can be useful in type system operations.
 - Interfaces that extend from multiple other interfaces.

 ## Examples

 <Tabs>
 <TabItem value="❌ Incorrect">

 ```ts
 let anyObject: {};
 let anyValue: {};

 interface AnyObjectA {}
 interface AnyValueA {}

 type AnyObjectB = {};
 type AnyValueB = {};
 ```

 </TabItem>
 <TabItem value="✅ Correct">

 ```ts
 let anyObject: object;
 let anyValue: unknown;

 type AnyObjectA = object;
 type AnyValueA = unknown;

 type AnyObjectB = object;
 type AnyValueB = unknown;

 let objectWith: { property: boolean };

 interface InterfaceWith {
  property: boolean;
 }

 type TypeWith = { property: boolean };
 ```

 </TabItem>
 </Tabs>

 ## Options

 By default, this rule flags both interfaces and object types.

 ### `allowInterfaces`

 Whether to allow empty interfaces, as one of:

 - `'always'`: to always allow interfaces with no fields
 - `'never'` _(default)_: to never allow interfaces with no fields
 - `'with-single-extends'`: to allow empty interfaces that `extend` from a single base interface

 Examples of **correct** code for this rule with `{ allowInterfaces: 'with-single-extends' }`:

 ```ts option='{ "allowInterfaces": "with-single-extends" }' showPlaygroundButton
 interface Base {
  value: boolean;
 }

 interface Derived extends Base {}
 ```

 ### `allowObjectTypes`

 Whether to allow empty object type literals, as one of:

 - `'always'`: to always allow object type literals with no fields
 - `'never'` _(default)_: to never allow object type literals with no fields

 ### `allowWithName`

 A stringified regular expression to allow interfaces and object type aliases with the configured name.
 This can be useful if your existing code style includes a pattern of declaring empty types with `{}` instead of `object`.

 Examples of code for this rule with `{ allowWithName: 'Props$' }`:

 <Tabs>
 <TabItem value="❌ Incorrect">

 ```ts option='{ "allowWithName": "Props$" }' showPlaygroundButton
 interface InterfaceValue {}

 type TypeValue = {};
 ```

 </TabItem>
 <TabItem value="✅ Correct">

 ```ts option='{ "allowWithName": "Props$" }' showPlaygroundButton
 interface InterfaceProps {}

 type TypeProps = {};
 ```

 </TabItem>
 </Tabs>

 ## When Not To Use It

 If your code commonly needs to represent the _"any non-nullish value"_ type, this rule may not be for you.
 Projects that extensively use type operations such as conditional types and mapped types oftentimes benefit from disabling this rule.

 ## Further Reading

 - [Enhancement: [ban-types] Split the {} ban into a separate, better-phrased rule](https://github.com/typescript-eslint/typescript-eslint/issues/8700)
 - [The Empty Object Type in TypeScript](https://www.totaltypescript.com/the-empty-object-type-in-typescript)
diff --git a/packages/eslint-plugin/src/configs/all.ts b/packages/eslint-plugin/src/configs/all.ts
    '@typescript-eslint/no-dynamic-delete': 'error',
    'no-empty-function': 'off',
    '@typescript-eslint/no-empty-function': 'error',
    '@typescript-eslint/no-empty-interface': 'error',
    '@typescript-eslint/no-empty-object-type': 'error',
    '@typescript-eslint/no-explicit-any': 'error',
    '@typescript-eslint/no-extra-non-null-assertion': 'error',
    '@typescript-eslint/no-extraneous-class': 'error',
diff --git a/packages/eslint-plugin/src/configs/recommended-type-checked.ts b/packages/eslint-plugin/src/configs/recommended-type-checked.ts
    '@typescript-eslint/no-base-to-string': 'error',
    '@typescript-eslint/no-duplicate-enum-values': 'error',
    '@typescript-eslint/no-duplicate-type-constituents': 'error',
    '@typescript-eslint/no-empty-object-type': 'error',
    '@typescript-eslint/no-explicit-any': 'error',
    '@typescript-eslint/no-extra-non-null-assertion': 'error',
    '@typescript-eslint/no-floating-promises': 'error',
diff --git a/packages/eslint-plugin/src/configs/recommended.ts b/packages/eslint-plugin/src/configs/recommended.ts
    'no-array-constructor': 'off',
    '@typescript-eslint/no-array-constructor': 'error',
    '@typescript-eslint/no-duplicate-enum-values': 'error',
    '@typescript-eslint/no-empty-object-type': 'error',
    '@typescript-eslint/no-explicit-any': 'error',
    '@typescript-eslint/no-extra-non-null-assertion': 'error',
    '@typescript-eslint/no-misused-new': 'error',
diff --git a/packages/eslint-plugin/src/configs/strict-type-checked.ts b/packages/eslint-plugin/src/configs/strict-type-checked.ts
    '@typescript-eslint/no-duplicate-enum-values': 'error',
    '@typescript-eslint/no-duplicate-type-constituents': 'error',
    '@typescript-eslint/no-dynamic-delete': 'error',
    '@typescript-eslint/no-empty-object-type': 'error',
    '@typescript-eslint/no-explicit-any': 'error',
    '@typescript-eslint/no-extra-non-null-assertion': 'error',
    '@typescript-eslint/no-extraneous-class': 'error',
diff --git a/packages/eslint-plugin/src/configs/strict.ts b/packages/eslint-plugin/src/configs/strict.ts
    '@typescript-eslint/no-array-constructor': 'error',
    '@typescript-eslint/no-duplicate-enum-values': 'error',
    '@typescript-eslint/no-dynamic-delete': 'error',
    '@typescript-eslint/no-empty-object-type': 'error',
    '@typescript-eslint/no-explicit-any': 'error',
    '@typescript-eslint/no-extra-non-null-assertion': 'error',
    '@typescript-eslint/no-extraneous-class': 'error',
diff --git a/packages/eslint-plugin/src/configs/stylistic-type-checked.ts b/packages/eslint-plugin/src/configs/stylistic-type-checked.ts
    '@typescript-eslint/no-confusing-non-null-assertion': 'error',
    'no-empty-function': 'off',
    '@typescript-eslint/no-empty-function': 'error',
    '@typescript-eslint/no-empty-interface': 'error',
    '@typescript-eslint/no-inferrable-types': 'error',
    '@typescript-eslint/non-nullable-type-assertion-style': 'error',
    '@typescript-eslint/prefer-for-of': 'error',
diff --git a/packages/eslint-plugin/src/configs/stylistic.ts b/packages/eslint-plugin/src/configs/stylistic.ts
    '@typescript-eslint/no-confusing-non-null-assertion': 'error',
    'no-empty-function': 'off',
    '@typescript-eslint/no-empty-function': 'error',
    '@typescript-eslint/no-empty-interface': 'error',
    '@typescript-eslint/no-inferrable-types': 'error',
    '@typescript-eslint/prefer-for-of': 'error',
    '@typescript-eslint/prefer-function-type': 'error',
diff --git a/packages/eslint-plugin/src/rules/ban-types.ts b/packages/eslint-plugin/src/rules/ban-types.ts
    message: 'Use bigint instead',
    fixWith: 'bigint',
  },

  Object: {
    message: 'Use object instead',
    fixWith: 'object',
  },
  Function: {
    message: [
      'The `Function` type accepts any function-like value.',
      'If you are expecting the function to accept certain arguments, you should explicitly define the function shape.',
    ].join('\n'),
  },

  // object typing
  Object: {
    message: [
      'The `Object` type actually means "any non-nullish value", so it is marginally better than `unknown`.',
      '- If you want a type meaning "any object", you probably want `object` instead.',
      '- If you want a type meaning "any value", you probably want `unknown` instead.',
      '- If you really want a type meaning "any non-nullish value", you probably want `NonNullable<unknown>` instead.',
    ].join('\n'),
    suggest: ['object', 'unknown', 'NonNullable<unknown>'],
  },
  '{}': {
    message: [
      '`{}` actually means "any non-nullish value".',
      '- If you want a type meaning "any object", you probably want `object` instead.',
      '- If you want a type meaning "any value", you probably want `unknown` instead.',
      '- If you want a type meaning "empty object", you probably want `Record<string, never>` instead.',
      '- If you really want a type meaning "any non-nullish value", you probably want `NonNullable<unknown>` instead.',
    ].join('\n'),
    suggest: [
      'object',
      'unknown',
      'Record<string, never>',
      'NonNullable<unknown>',
    ],
  },
 };

 export const TYPE_KEYWORDS = {
diff --git a/packages/eslint-plugin/src/rules/index.ts b/packages/eslint-plugin/src/rules/index.ts
 import noDynamicDelete from './no-dynamic-delete';
 import noEmptyFunction from './no-empty-function';
 import noEmptyInterface from './no-empty-interface';
 import noEmptyObjectType from './no-empty-object-type';
 import noExplicitAny from './no-explicit-any';
 import noExtraNonNullAssertion from './no-extra-non-null-assertion';
 import noExtraneousClass from './no-extraneous-class';
  'no-dynamic-delete': noDynamicDelete,
  'no-empty-function': noEmptyFunction,
  'no-empty-interface': noEmptyInterface,
  'no-empty-object-type': noEmptyObjectType,
  'no-explicit-any': noExplicitAny,
  'no-extra-non-null-assertion': noExtraNonNullAssertion,
  'no-extraneous-class': noExtraneousClass,
diff --git a/packages/eslint-plugin/src/rules/no-empty-interface.ts b/packages/eslint-plugin/src/rules/no-empty-interface.ts
    type: 'suggestion',
    docs: {
      description: 'Disallow the declaration of empty interfaces',
      recommended: 'stylistic',
    },
    deprecated: true,
    replacedBy: ['@typescript-eslint/no-empty-object-type'],
    fixable: 'code',
    hasSuggestions: true,
    messages: {
Original file line number	Diff line number	Diff line change
Expand Up		@@ -24,7 +24,7 @@ It lists all TSLint rules along side rules from the ESLint ecosystem that are th
		\| [`member-access`] \| ✅ \| [`@typescript-eslint/explicit-member-accessibility`] \|
		\| [`member-ordering`] \| ✅ \| [`@typescript-eslint/member-ordering`] \|
		\| [`no-any`] \| ✅ \| [`@typescript-eslint/no-explicit-any`] \|
		\| [`no-empty-interface`] \| ✅ \| [`@typescript-eslint/no-empty-interface`] \|
		\| [`no-empty-interface`] \| ✅ \| [`@typescript-eslint/no-empty-object-type`] \|
		\| [`no-import-side-effect`] \| 🔌 \| [`import/no-unassigned-import`] \|
		\| [`no-inferrable-types`] \| ✅ \| [`@typescript-eslint/no-inferrable-types`] \|
		\| [`no-internal-module`] \| ✅ \| [`@typescript-eslint/prefer-namespace-keyword`] \|
Expand DownExpand Up		@@ -604,7 +604,7 @@ Relevant plugins: [`chai-expect-keywords`](https://github.com/gavinaiken/eslint-
		[`@typescript-eslint/member-ordering`]: https://typescript-eslint.io/rules/member-ordering
		[`@typescript-eslint/method-signature-style`]: https://typescript-eslint.io/rules/method-signature-style
		[`@typescript-eslint/no-explicit-any`]: https://typescript-eslint.io/rules/no-explicit-any
		[`@typescript-eslint/no-empty-interface`]: https://typescript-eslint.io/rules/no-empty-interface
		[`@typescript-eslint/no-empty-object-type`]: https://typescript-eslint.io/rules/no-empty-object-type
		[`@typescript-eslint/no-implied-eval`]: https://typescript-eslint.io/rules/no-implied-eval
		[`@typescript-eslint/no-inferrable-types`]: https://typescript-eslint.io/rules/no-inferrable-types
		[`@typescript-eslint/prefer-namespace-keyword`]: https://typescript-eslint.io/rules/prefer-namespace-keyword
Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -36,9 +36,6 @@ const func: Function = () => 1;
		// use safer object types
		const lowerObj: Object = {};
		const capitalObj: Object = { a: 'string' };

		const curly1: {} = 1;
		const curly2: {} = { a: 'string' };
		```

		</TabItem>
Expand All		@@ -58,9 +55,6 @@ const func: () => number = () => 1;
		// use safer object types
		const lowerObj: object = {};
		const capitalObj: { a: string } = { a: 'string' };

		const curly1: number = 1;
		const curly2: Record<'a', string> = { a: 'string' };
		```

		</TabItem>
Expand All		@@ -70,13 +64,10 @@ const curly2: Record<'a', string> = { a: 'string' };

		The default options provide a set of "best practices", intended to provide safety and standardization in your codebase:

		- Don't use the upper-case primitive types, you should use the lower-case types for consistency.
		- Don't use the upper-case primitive types or `Object`, you should use the lower-case types for consistency.
		- Avoid the `Function` type, as it provides little safety for the following reasons:
		- It provides no type safety when calling the value, which means it's easy to provide the wrong arguments.
		- It accepts class declarations, which will fail when called, as they are called without the `new` keyword.
		- Avoid the `Object` and `{}` types, as they mean "any non-nullish value".
JoshuaKGoldberg marked this conversation as resolved. Show resolvedHide resolved
		- This is a point of confusion for many developers, who think it means "any object type".
		- See [this comment for more information](https://github.com/typescript-eslint/typescript-eslint/issues/2063#issuecomment-675156492).

		<details>
		<summary>Default Options</summary>
Expand DownExpand Up		@@ -136,3 +127,7 @@ Example configuration:

		If your project is a rare one that intentionally deals with the class equivalents of primitives, it might not be worthwhile to enable the default `ban-types` options.
		You might consider using [ESLint disable comments](https://eslint.org/docs/latest/use/configure/rules#using-configuration-comments-1) for those specific situations instead of completely disabling this rule.

		## Related To

		- [`no-empty-object-type`](./no-empty-object-type.mdx)
Original file line number	Diff line number	Diff line change
Expand Up		@@ -9,6 +9,12 @@ import TabItem from '@theme/TabItem';
		>
		> See https://typescript-eslint.io/rules/no-empty-interface for documentation.

		:::danger Deprecated

		This rule has been deprecated in favour of the more comprehensive [`@typescript-eslint/no-empty-object-type`](./no-empty-object-type.mdx) rule.

		:::

		An empty interface in TypeScript does very little: any non-nullable value is assignable to `{}`.
		Using an empty interface is often a sign of programmer error, such as misunderstanding the concept of `{}` or forgetting to fill in fields.

Expand DownExpand Up		@@ -61,3 +67,7 @@ interface Baz extends Foo, Bar {}
		## When Not To Use It

		If you don't care about having empty/meaningless interfaces, then you will not need this rule.

		## Related To

		- [`no-empty-object-type`](./no-empty-object-type.mdx)
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1,145 @@
		---
		description: 'Disallow accidentally using the "empty object" type.'
		---

		import Tabs from '@theme/Tabs';
		import TabItem from '@theme/TabItem';

		> 🛑 This file is source code, not the primary documentation location! 🛑
		>
		> See https://typescript-eslint.io/rules/no-empty-object-type for documentation.

		The `{}`, or "empty object" type in TypeScript is a common source of confusion for developers unfamiliar with TypeScript's structural typing.
		`{}` represents any _non-nullish value_, including literals like `0` and `""`:

		```ts
		let anyNonNullishValue: {} = 'Intentionally allowed by TypeScript.';
JoshuaKGoldberg marked this conversation as resolved. Show resolvedHide resolved
		```

		Often, developers writing `{}` actually mean either:

		- `object`: representing any _object_ value
		- `unknown`: representing any value at all, including `null` and `undefined`

		In other words, the "empty object" type `{}` really means _"any value that is defined"_.
		That includes arrays, class instances, functions, and primitives such as `string` and `symbol`.

		To avoid confusion around the `{}` type allowing any _non-nullish value_, this rule bans usage of the `{}` type.
		That includes interfaces and object type aliases with no fields.

		:::tip
		If you do have a use case for an API allowing `{}`, you can always configure the [rule's options](#options), use an [ESLint disable comment](https://eslint.org/docs/latest/use/configure/rules#using-configuration-comments-1), or [disable the rule in your ESLint config](https://eslint.org/docs/latest/use/configure/rules#using-configuration-files-1).
		:::
JoshuaKGoldberg marked this conversation as resolved. Show resolvedHide resolved

		Note that this rule does not report on:

		- `{}` as a type constituent in an intersection type (e.g. types like TypeScript's built-in `type NonNullable<T> = T & {}`), as this can be useful in type system operations.
		- Interfaces that extend from multiple other interfaces.

		## Examples

		<Tabs>
		<TabItem value="❌ Incorrect">

		```ts
		let anyObject: {};
		let anyValue: {};

		interface AnyObjectA {}
		interface AnyValueA {}

		type AnyObjectB = {};
		type AnyValueB = {};
		```

		</TabItem>
		<TabItem value="✅ Correct">

		```ts
		let anyObject: object;
		let anyValue: unknown;

		type AnyObjectA = object;
		type AnyValueA = unknown;

		type AnyObjectB = object;
		type AnyValueB = unknown;

		let objectWith: { property: boolean };

		interface InterfaceWith {
		property: boolean;
		}

		type TypeWith = { property: boolean };
		```

		</TabItem>
		</Tabs>

		## Options

		By default, this rule flags both interfaces and object types.

		### `allowInterfaces`

		Whether to allow empty interfaces, as one of:

		- `'always'`: to always allow interfaces with no fields
		- `'never'` _(default)_: to never allow interfaces with no fields
		- `'with-single-extends'`: to allow empty interfaces that `extend` from a single base interface

		Examples of correct code for this rule with `{ allowInterfaces: 'with-single-extends' }`:

		```ts option='{ "allowInterfaces": "with-single-extends" }' showPlaygroundButton
		interface Base {
		value: boolean;
		}

		interface Derived extends Base {}
		```

		### `allowObjectTypes`

		Whether to allow empty object type literals, as one of:
kirkwaiblinger marked this conversation as resolved. Show resolvedHide resolved

		- `'always'`: to always allow object type literals with no fields
		- `'never'` _(default)_: to never allow object type literals with no fields

		### `allowWithName`

		A stringified regular expression to allow interfaces and object type aliases with the configured name.
		This can be useful if your existing code style includes a pattern of declaring empty types with `{}` instead of `object`.

		Examples of code for this rule with `{ allowWithName: 'Props$' }`:

		<Tabs>
		<TabItem value="❌ Incorrect">

		```ts option='{ "allowWithName": "Props$" }' showPlaygroundButton
		interface InterfaceValue {}

		type TypeValue = {};
		```

		</TabItem>
		<TabItem value="✅ Correct">

		```ts option='{ "allowWithName": "Props$" }' showPlaygroundButton
		interface InterfaceProps {}

		type TypeProps = {};
		```

		</TabItem>
		</Tabs>

		## When Not To Use It

		If your code commonly needs to represent the _"any non-nullish value"_ type, this rule may not be for you.
		Projects that extensively use type operations such as conditional types and mapped types oftentimes benefit from disabling this rule.

		## Further Reading

		- [Enhancement: [ban-types] Split the {} ban into a separate, better-phrased rule](https://github.com/typescript-eslint/typescript-eslint/issues/8700)
		- [The Empty Object Type in TypeScript](https://www.totaltypescript.com/the-empty-object-type-in-typescript)
JoshuaKGoldberg marked this conversation as resolved. Show resolvedHide resolved
Original file line number	Diff line number	Diff line change
Expand Up		@@ -54,7 +54,7 @@ export = {
		'@typescript-eslint/no-dynamic-delete': 'error',
		'no-empty-function': 'off',
		'@typescript-eslint/no-empty-function': 'error',
		'@typescript-eslint/no-empty-interface': 'error',
		'@typescript-eslint/no-empty-object-type': 'error',
		'@typescript-eslint/no-explicit-any': 'error',
		'@typescript-eslint/no-extra-non-null-assertion': 'error',
		'@typescript-eslint/no-extraneous-class': 'error',
Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -18,6 +18,7 @@ export = {
		'@typescript-eslint/no-base-to-string': 'error',
		'@typescript-eslint/no-duplicate-enum-values': 'error',
		'@typescript-eslint/no-duplicate-type-constituents': 'error',
		'@typescript-eslint/no-empty-object-type': 'error',
		'@typescript-eslint/no-explicit-any': 'error',
		'@typescript-eslint/no-extra-non-null-assertion': 'error',
		'@typescript-eslint/no-floating-promises': 'error',
Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -15,6 +15,7 @@ export = {
		'no-array-constructor': 'off',
		'@typescript-eslint/no-array-constructor': 'error',
		'@typescript-eslint/no-duplicate-enum-values': 'error',
		'@typescript-eslint/no-empty-object-type': 'error',
		'@typescript-eslint/no-explicit-any': 'error',
		'@typescript-eslint/no-extra-non-null-assertion': 'error',
		'@typescript-eslint/no-misused-new': 'error',
Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -24,6 +24,7 @@ export = {
		'@typescript-eslint/no-duplicate-enum-values': 'error',
		'@typescript-eslint/no-duplicate-type-constituents': 'error',
		'@typescript-eslint/no-dynamic-delete': 'error',
		'@typescript-eslint/no-empty-object-type': 'error',
		'@typescript-eslint/no-explicit-any': 'error',
		'@typescript-eslint/no-extra-non-null-assertion': 'error',
		'@typescript-eslint/no-extraneous-class': 'error',
Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -19,6 +19,7 @@ export = {
		'@typescript-eslint/no-array-constructor': 'error',
		'@typescript-eslint/no-duplicate-enum-values': 'error',
		'@typescript-eslint/no-dynamic-delete': 'error',
		'@typescript-eslint/no-empty-object-type': 'error',
		'@typescript-eslint/no-explicit-any': 'error',
		'@typescript-eslint/no-extra-non-null-assertion': 'error',
		'@typescript-eslint/no-extraneous-class': 'error',
Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -23,7 +23,6 @@ export = {
		'@typescript-eslint/no-confusing-non-null-assertion': 'error',
		'no-empty-function': 'off',
		'@typescript-eslint/no-empty-function': 'error',
		'@typescript-eslint/no-empty-interface': 'error',
		'@typescript-eslint/no-inferrable-types': 'error',
		'@typescript-eslint/non-nullable-type-assertion-style': 'error',
		'@typescript-eslint/prefer-for-of': 'error',
Expand Down