Question 1

How do I set up eslint-plugin-import with TypeScript?

Accepted Answer

Install @typescript-eslint/parser and eslint-import-resolver-typescript, then extend 'plugin:import/typescript' in your ESLint config and configure the TypeScript resolver in settings for proper module resolution.

Question 2

What's the difference between eslint-plugin-import and ESLint's built-in import rules?

Accepted Answer

ESLint has limited native support for imports, focusing on syntax, while eslint-plugin-import adds extensive rules for static analysis, resolution, and style, making it essential for catching module-specific errors in ES6+ projects.

Question 3

How can I fix 'import/no-unresolved' errors when using webpack aliases?

Accepted Answer

Configure the webpack resolver by installing eslint-import-resolver-webpack and setting it in ESLint settings, ensuring your webpack config aliases match to resolve modules correctly.

Question 4

Does eslint-plugin-import detect circular dependencies?

Accepted Answer

Yes, the 'no-cycle' rule identifies and reports circular dependencies between modules, helping prevent runtime issues and maintain clean architecture in complex codebases.

Question 5

What's the best way to enforce import order with this plugin?

Accepted Answer

Use the 'order' rule with custom groups and sorting options, such as separating internal and external imports, and enable auto-fix to automatically rearrange imports on save or lint.

Question 6

Are there resolvers for eslint-plugin-import that work with monorepos?

Accepted Answer

Yes, configure settings like import/internal-regex and import/external-module-folders to mark monorepo packages as internal, and use resolvers like Node with path adjustments for proper scoping.

import

What is import?

Overview

Use Cases

Best For

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions