useImportsFirst

JavaScript (and super languages)

Summary

Diagnostic Category: lint/nursery/useImportsFirst
This rule doesn’t have a fix.
The default severity of this rule is information.
Sources:
- Same as import/first

How to configure

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

Description

Enforce that all imports appear at the top of the module.

Import statements that appear after non-import statements are harder to find and may indicate disorganized code. Keeping all imports together at the top makes dependencies immediately visible.

Directives such as "use strict" are always allowed before imports, since they are parsed separately from module items.

This rule only applies to ES module import statements. CommonJS require() calls are not covered.

Examples

Invalid

1
import { foo } from "foo";
2
const bar = 1;
3
import { baz } from "baz";

code-block.js:3:1 lint/nursery/useImportsFirst ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ℹ This import appears after a non-import statement.
  
    1 │ import { foo } from “foo”;
    2 │ const bar = 1;
  > 3 │ import { baz } from “baz”;
      │ ^^^^^^^^^^^^^^^^^^^^^^^^^^
    4 │ 
  
  ℹ Scattering imports makes it harder to see the module’s dependencies at a glance.
  
  ℹ Move all import statements before any other statements.
  
  ℹ This rule belongs to the nursery group, which means it is not yet stable and may change in the future. Visit https://biomejs.dev/linter/#nursery for more information.

Valid

1
import { foo } from "foo";
2
import { bar } from "bar";
3
const baz = 1;

1
"use strict";
2
import { foo } from "foo";