eslint-plugin-import-x - npm Package Versions

4.4.2

Patch Changes

• #181 cc4ee65 Thanks @SukkaW! - Fix #144, read proper sourceType for both eslint flat config and legacy eslintrc config.

4.4.0

Minor Changes

• #169 9c58269 Thanks @teidesu! - Add new rule option checkTypedImports for extensions, backports https://github.com/import-js/eslint-plugin-import/pull/2817

Patch Changes

• #171 9715220 Thanks @SukkaW! - Perf: avoid regexp during parser choosing

• #171 9715220 Thanks @SukkaW! - Add extra guard for rule no-named-as-default. A few guards are borrowed from https://github.com/import-js/eslint-plugin-import/pull/3032, but we don't sync the rest of changes from upstream since we have already implemented a way more performant check.

• #171 9715220 Thanks @SukkaW! - More test cases for no-named-export and no-defualt-export rule specifically with non-module sourceType

• #171 9715220 Thanks @SukkaW! - Fix export when there is only one TSDeclareFunction (https://github.com/import-js/eslint-plugin-import/pull/3065)

• #171 9715220 Thanks @SukkaW! - Prevent ExportMap's cache is being tainted by incompatible parser (e.g. old babel-eslint). The cache is now skipped w/ incompatible parsers, which might introduce performance impacts only for those who are using incompatible parsers. (https://github.com/import-js/eslint-plugin-import/pull/3062)

• #171 9715220 Thanks @SukkaW! - Docs: fix a few typos here and there

• #168 5de039c Thanks @hyoban! - Fixes https://github.com/un-ts/eslint-plugin-import-x/issues/167, the no-duplicates rule now allows co-existing inline type imports and namespace imports.

• #171 9715220 Thanks @SukkaW! - Properly fix espree parser w/ ESLint Flat Config

4.3.1

Patch Changes

• #162 38d0081 Thanks @AaronMoat! - Fix issue where no-duplicates rule with prefer-inline incorrectly marks default type and named type imports as duplicates

4.3.0

Minor Changes

• #159 4da5388 Thanks @GoodbyeNJN! - feat: add support for using resolver object directly in settings

4.2.1

Patch Changes

• #148 d228129 Thanks @SukkaW! - Fix newline-after-import's considerComments options when linting require, backports https://github.com/import-js/eslint-plugin-import/pull/2952

• #147 eca73ed Thanks @nchevsky! - Fix regression in rule no-unused-modules which would incorrectly initialize option src to [] instead of [process.cwd()], breaking file discovery.

• #148 d228129 Thanks @SukkaW! - Fix no-duplicates for TypeScript, backports https://github.com/import-js/eslint-plugin-import/pull/3033

4.2.0

Minor Changes

• #142 f12447e Thanks @Zamiell! - Add new option "whitelist" for rule "no-extraneous-dependencies"

Patch Changes

• #146 e5e4580 Thanks @SukkaW! - Fix https://github.com/nuxt/eslint/issues/494 by avoid importing from @typescript-eslint/typescript-estree.

4.1.1

Patch Changes

• #133 757ffa9 Thanks @SukkaW! - Fix #123 where the rule no-named-as-default will confuse TypeScript namespace exports with actual exports.

4.1.0

Minor Changes

• #122 cd52e86 Thanks @michaelfaith! - Add ESLint flat configuration presets. You can access them with:

  import eslintPluginImportX from "eslint-plugin-import-x";
  
  eslintPluginImportX.flatConfigs.recommended;
  eslintPluginImportX.flatConfigs.react;
  eslintPluginImportX.flatConfigs.typescript;
  eslintPluginImportX.flatConfigs.electron;
  

• #132 9948c78 Thanks @SukkaW! - Added no-rename-default that forbid importing a default export by a different name. Originally created by @whitneyit, ported by @SukkaW

4.0.0

Major Changes

• #112 4ba14da Thanks @SukkaW! - Use typescript-eslint v8. The minimum supported ESLint version is now >= 8.57.0 and the minimum required Node.js version is now 18.18.0.

3.1.0

Minor Changes

• #116 38aa4cb Thanks @silverwind! - Add ignoreUnusedTypeExports option to no-unused-modules

Patch Changes

• #118 0307ff2 Thanks @SukkaW! - Reverts #111. The introduction of SCC causes extra overhead that overcomes the early return it introduced.

  A new no-cycle-next rule is being implemented using the graph. It won't be backward compatible with the current rule no-cycle. The current no-cycle rule will become no-cycle-legacy in the next major version.