import/first Style

🚧 An auto-fix is still under development.

What it does

Forbids any non-import statements before imports except directives.

Why is this bad?

Notably, imports are hoisted, which means the imported modules will be evaluated before any of the statements interspersed between them. Keeping all imports together at the top of the file may prevent surprises resulting from this part of the spec

Examples

Examples of incorrect code for this rule:

import { x } from "./foo";
export { x };
import { y } from "./bar";

Examples of correct code for this rule:

import { x } from "./foo";
import { y } from "./bar";
export { x, y };

Options

with "absolute-first":

Examples of incorrect code for this rule:

import { x } from "./foo";
import { y } from "bar";

Examples of correct code for this rule:

import { y } from "bar";
import { x } from "./foo";

References

• Rule Source