import-x
A performant, lightweight ESLint plugin for linting ES2015+ import/export syntax, forked from eslint-plugin-import.
What is import-x?
eslint-plugin-import-x is a fork of eslint-plugin-import that provides linting rules for ES2015+ import/export syntax in JavaScript and TypeScript projects. It aims to solve performance and dependency issues in the original plugin by using lighter tools and modern resolvers, helping developers catch errors like unresolved imports or incorrect exports more efficiently.
JavaScript and TypeScript developers using ESLint for code quality, particularly those working on large codebases where linting performance and modern module resolution (like the `exports` field) are critical.
Developers choose eslint-plugin-import-x for its significantly faster performance, reduced dependency footprint, and proactive support for modern ES features like the `exports` field, which the original plugin lacks. It’s a drop-in replacement that addresses long-standing issues with breaking changes when necessary.
Overview
eslint-plugin-import-x is a fork of eslint-plugin-import that aims to provide a more performant and more lightweight version of the original plugin.
Use Cases
Best For
- Linting import/export syntax in large TypeScript monorepos
- Improving ESLint performance in projects with heavy module resolution
- Enforcing consistent import styles and preventing path errors
- Using modern package.json `exports` field with ESLint
- Reducing dependency bloat in ESLint configurations
- Migrating from eslint-plugin-import for better maintenance
Not Ideal For
- Teams stuck on legacy Node.js versions (below 18.18.0) or older ESLint (below 8.57.0)
- Projects heavily dependent on eslint-plugin-import's specific behavior without tolerance for breaking changes
- Environments where maximum third-party resolver ecosystem maturity is critical
- Simple codebases where linting performance gains are negligible and setup complexity is unwarranted
Pros & Cons
Pros
Uses get-tsconfig to replace heavy TypeScript dependencies and a custom Rust-based resolver (unrs-resolver), significantly speeding up linting operations in large projects.
Has only 16 dependencies compared to 117 in eslint-plugin-import, reducing bloat and potential conflicts in your ESLint setup.
Targets Node.js 18.18.0+ and ESLint 8.57.0+, with first-party support for the exports field in package.json, ensuring alignment with contemporary JavaScript standards.
Introduces import-x/resolver-next for flat configs, which shares a single resolver instance to optimize caching and memoization out-of-the-box.
Cons
The project philosophy embraces breaking changes to fix issues, which can disrupt existing configurations and require manual migration efforts from eslint-plugin-import.
As a newer fork, it has fewer community-contributed resolvers and integrations compared to the long-established eslint-plugin-import, potentially limiting third-party tool support.
Supports both legacy .eslintrc* and new eslint.config.* systems, with TypeScript setup requiring additional packages like eslint-import-resolver-typescript, adding overhead for beginners.
Open Source Alternative To
import-x is an open-source alternative to the following products:
Frequently Asked Questions
Related Projects
importESLint plugin with rules that help validate proper imports.
PromiseEnforce best practices for JavaScript promises
functionalESLint rules to disable mutation and promote fp in JavaScript and TypeScript.
fpESLint rules for functional programming
Found a gem we're missing?
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.