noExportedImports

Ta treść nie jest jeszcze dostępna w Twoim języku.

JavaScript (and super languages)

Summary

Rule available since: v1.9.0
Diagnostic Category: lint/style/noExportedImports
This rule doesn’t have a fix.
The default severity of this rule is information.

How to configure

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

Description

Disallow exporting an imported variable.

In JavaScript, you can re-export a variable either by using export from or by first importing the variable and then exporting it with a regular export.

You may prefer to use the first approach, as it clearly communicates the intention to re-export an import, and can make static analysis easier.

Examples

Invalid

1
import { A } from "mod";
2
export { A };

code-block.js:1:10 lint/style/noExportedImports ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ℹ An import should not be exported. Use export from instead.
  
  > 1 │ import { A } from “mod”;
      │          ^
    2 │ export { A };
    3 │ 
  
  ℹ export from makes it clearer that the intention is to re-export a variable.

1
import * as ns from "mod";
2
export { ns };

code-block.js:1:8 lint/style/noExportedImports ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ℹ An import should not be exported. Use export from instead.
  
  > 1 │ import * as ns from “mod”;
      │        ^^^^^^^
    2 │ export { ns };
    3 │ 
  
  ℹ export from makes it clearer that the intention is to re-export a variable.

1
import D from "mod";
2
export { D };

code-block.js:1:8 lint/style/noExportedImports ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ℹ An import should not be exported. Use export from instead.
  
  > 1 │ import D from “mod”;
      │        ^
    2 │ export { D };
    3 │ 
  
  ℹ export from makes it clearer that the intention is to re-export a variable.

Valid

1
export { A } from "mod";
2
export * as ns from "mod";
3
export { default as D } from "mod";