Configurable Import Settings Challenge

Design an ESLint flat config that tunes import resolution for a mixed JS/TS workspace, ensuring custom aliases, built-in module recognition, and controlled ignore/external behavior work consistently across linted files.

Capabilities

Resolves TypeScript aliases and extensions

• Linting src/app.ts that imports @shared/logger (mapping to src/shared/logger.ts) and ./ui/Button (resolving a .tsx component) passes without unresolved or missing-extension errors. @test

Ignores generated artifacts during import checks

• Imports inside any path matching **/generated/** are skipped by import-resolution checks, while imports outside those paths still surface unresolved errors. @test

Recognizes vendor folder as external module source

• Imports from a top-level vendor/ folder (e.g., vendor/charting) are treated as external modules and do not trigger unresolved or extraneous-dependency errors, while missing local files remain flagged. @test

Adds custom core module support

• Bare imports of worker_threads and node:test are recognized as core modules and avoid unresolved/extraneous errors, whereas an unrecognized bare specifier like nonexistent-core still fails. @test

Implementation

@generates

API

// ESM flat config exporting an array of configs with import linting/resolution tuned
export default [
  /* config entries with settings and rules required to satisfy the capabilities */
];

Dependencies { .dependencies }

eslint-plugin-import-x { .dependency }

Provides import linting rules and resolver utilities for JS/TS projects.