eslint-plugin-import-next

⭐ If this plugin caught a real bug for you, star the repo — it's the signal that keeps these rules maintained.

Description

This plugin provides Next-generation import sorting, validation, and architectural boundaries.

• Why — a linter nobody reads protects nothing. We would rather miss a finding than spend your attention on one that was never real.
• How — evidence, not names. A rule fires on what the code does, resolved through the AST and ESLint's own scope analysis.
• What — every finding carries its fix, in prose for a human and as structured JSON for an agent. Security rules add a CWE mapping and, where assigned, a CVSS score.

That trade costs recall, and we measure it: methodology · results · a false positive is a bug.

Getting Started

• To check out the guide, visit eslint.interlace.tools. 📚

npm install eslint-plugin-import-next --save-dev

⚙️ Configuration Presets

🔄 Parity with eslint-plugin-import

Rule	Original Plugin	Status	Notes
All Rules	eslint-plugin-import	✅ Supported	Full drop-in replacement

🧬 Deep dependency graphs

import/no-cycle crashes on deep import chains. import-next/no-cycle does not.

Cycle detection is a strongly-connected-components pass over your module graph. Done recursively — one JavaScript stack frame per module — a chain deeper than the engine's call stack throws RangeError: Maximum call stack size exceeded. ESLint then exits 2 with no results at all: not a slow lint, no lint. Both rules default to unlimited traversal depth, so nothing caps the descent.

import-next runs the same traversal on an explicit stack, so its ceiling is heap rather than stack.

See it yourself

npm i -D eslint eslint-plugin-import eslint-plugin-import-next
curl -O https://raw.githubusercontent.com/ofri-peretz/eslint/main/benchmarks/scripts/repro-deep-chain.mjs
node repro-deep-chain.mjs 6000

chain depth: 6000 modules

eslint-plugin-import         FAILED after 93.6s — RangeError: Error while loading rule 'import/no-cycle': Maximum call stack size exceeded
eslint-plugin-import-next    completed in 18.2s

Measured on Node 24 / darwin-arm64 with ESLint 10.7. The exact depth at which the recursive implementation dies varies with Node version and platform stack size — around 5,000 modules here.

Chains get deep by accident

Hand-written 5,000-module chains are rare. These are not:

• generated clients and schema bindings, where each type re-exports the next
• barrel files (index.ts) re-exporting barrels, several layers down
• long export … from ladders in a monorepo's shared packages

Depth accumulates through re-export edges, which is exactly what the rule follows.

Speed, for completeness

Across graph shapes at 5,000 files each, import-next is ~1.1× faster on dense cyclic graphs and on cold single-file runs, and ties on graphs with no cycles to find. The wide/shallow shape is unresolved — two runs disagree (0.8× sequential, 1.01× interleaved) and the machine has not been quiet enough to settle it, so no claim is made there. On a real 455K-line React codebase it is 8× faster in rule time and 3.1× end-to-end at 100% detection parity.

Speed is the smaller story. The deep-chain result above is a difference in kind, not degree.

Detection parity is checked per shape before any timing is trusted, and every number comes from a committed result file:

• benchmarks/results/ilb-perf-import-shapes/
• benchmarks/results/ilb-perf-import-no-cycle/
• methodology

📦 Compatibility

See the ESLint Version Support Policy for the full matrix.

Rules

Legend

🔗 Related ESLint Plugins

Part of the Interlace ESLint ecosystem — AI-native rules with LLM-optimized error messages:

Security

Plugin	Downloads	Description
eslint-plugin-anthropic-security		Anthropic SDK security.
eslint-plugin-browser-security		XSS, DOM security.
eslint-plugin-drizzle-security		Drizzle security.
eslint-plugin-express-security		Express middleware hardening.
eslint-plugin-gemini-security		Google Gemini SDK security.
eslint-plugin-jwt-security		Token security.
eslint-plugin-knex-security		Knex security.
eslint-plugin-lambda-security		AWS Lambda hardening.
eslint-plugin-mcp-sdk-security		MCP SDK security.
eslint-plugin-mongodb-security		MongoDB injection.
eslint-plugin-mysql-security		MySQL security.
eslint-plugin-nestjs-security		NestJS framework hardening.
eslint-plugin-node-security		Server-side patterns.
eslint-plugin-openai-security		OpenAI SDK security.
eslint-plugin-postgresql-security		PostgreSQL security.
eslint-plugin-prisma-security		Prisma security.
eslint-plugin-secure-coding		Injection prevention.
eslint-plugin-sequelize-security		Sequelize ORM security.
eslint-plugin-sqlite-security		SQLite security.
eslint-plugin-typeorm-security		TypeORM security.
eslint-plugin-vercel-ai-security		AI SDK security.

Code quality

Plugin	Downloads	Description
eslint-plugin-conventions		Team-specific habits and styles.
eslint-plugin-maintainability		Cognitive load and clean-code patterns.
eslint-plugin-modernization		ESNext migration + syntax evolution.
eslint-plugin-modularity		Structural integrity and DDD patterns.
eslint-plugin-operability		Production readiness and resource health.
eslint-plugin-react-a11y		React accessibility / WCAG.
eslint-plugin-react-features		React best practices and optimization.
eslint-plugin-reliability		Runtime stability and error safety.

⭐ Support & follow

If this plugin caught a real bug for you, star the repo — stars are the signal that keeps the Interlace ESLint ecosystem maintained — and follow the writeups on Dev.to for the benchmarks and security research behind these rules.

📄 License

MIT © Ofri Peretz