no-inline-imports

What problem does it solve?

Prevents messy, hard-to-review code by ensuring all module imports stay at the top of the file instead of being scattered inside function bodies or type definitions.

Core Features & Use Cases

• Enforces Top-of-File Imports: Requires import/require statements to live only in the module header for consistency and readability.
• Flags Inline Imports in Logic and Types: Detects inline require(...) / import(...) within function bodies, type annotations, and interface fields.
• Preserves Legitimate Exceptions: Allows inline imports only for documented circular-dependency reasons or intentional lazy-loading with measurable intent.

Quick Start

Use no-inline-imports when reviewing a TypeScript/JavaScript file that introduces require(...) or import(...) inside a function, type, or interface field.