noNamespace

TypeScript and TSX

Summary

Rule available since: v1.0.0
Diagnostic Category: lint/style/noNamespace
This rule doesn’t have a fix.
The default severity of this rule is information.
Sources:
- Same as @typescript-eslint/no-namespace

Description

Disallow the use of TypeScript’s namespaces.

Namespaces are an old way to organize your code in TypeScript. They are not recommended anymore and should be replaced by ES6 modules (the import/export syntax).

Examples

Invalid

1
module foo {}

code-block.ts:1:1 lint/style/noNamespace ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ℹ TypeScript’s namespaces are an outdated way to organize code.
  
  > 1 │ module foo {}
      │ ^^^^^^^^^^^^^
    2 │ 
  
  ℹ Prefer the ES6 modules (import/export) over namespaces.

1
declare module foo {}

code-block.ts:1:9 lint/style/noNamespace ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ℹ TypeScript’s namespaces are an outdated way to organize code.
  
  > 1 │ declare module foo {}
      │         ^^^^^^^^^^^^^
    2 │ 
  
  ℹ Prefer the ES6 modules (import/export) over namespaces.

1
namespace foo {}

code-block.ts:1:1 lint/style/noNamespace ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ℹ TypeScript’s namespaces are an outdated way to organize code.
  
  > 1 │ namespace foo {}
      │ ^^^^^^^^^^^^^^^^
    2 │ 
  
  ℹ Prefer the ES6 modules (import/export) over namespaces.

1
declare namespace foo {}

code-block.ts:1:9 lint/style/noNamespace ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ℹ TypeScript’s namespaces are an outdated way to organize code.
  
  > 1 │ declare namespace foo {}
      │         ^^^^^^^^^^^^^^^^
    2 │ 
  
  ℹ Prefer the ES6 modules (import/export) over namespaces.

Valid

1
import foo from 'foo';
2
export { bar };

1
declare global {}

1
declare module 'foo' {}

How to configure

1
{
2
  "linter": {
3
    "rules": {
4
      "style": {
5
        "noNamespace": "error"
6
      }
7
    }
8
  }
9
}