How to deal with import-x/no-extraneous-dependencies errors on eslint.config.mjs in v3 ?

[khitrenovich]

Plugin v3 had switched to "batteries included" mode, providing other plugins, as well as eslint-import-resolver-typescript as dependencies.

However, this triggers import-x/no-extraneous-dependencies error on

import { createTypeScriptImportResolver } from 'eslint-import-resolver-typescript';

in my eslint.config.mjs file.

I do need this helper, since I need to compile my own list of TS projects (for reasons that are beyond the scope of this question).

What is the suggested way to deal with it?
I can disable this rule for the given line, of course, but I was looking for something less drastic.

[NishargShah]

Hello @khitrenovich,

The eslint-import-resolver-typescript is bundled with the eslint-config-airbnb-extended package, but it isn’t installed in your project by default. Please add it as a dev dependency, and the error should be resolved.

[NishargShah]

Alternatively, if you don’t want to deal with it, you can whitelist it. This approach is not recommended, because in strict dependency mode it will result in an error.

'import-x/no-extraneous-dependencies': [
  'error',
  {
    devDependencies: getDevDepsList('typescript'),
    optionalDependencies: false,
    whitelist: ['eslint-import-resolver-typescript'],
  },
],

Learn more about how to get getDevDepsList, please check https://eslint-airbnb-extended.nishargshah.dev/config/extended-config/helpers#get-dev-deps-list

[khitrenovich]

but it isn’t installed in your project by default

Well, the migration guide to v3 clearly states that eslint-import-resolver-typescript is now included by default and thus should be removed from project dependencies:

I just checked package.json for eslint-config-airbnb-extended and it appears there as a dependency - so the migration guide appears to be correct.

Anyway, it sounds like in case I need to rely on anything explicitly imported from eslint-import-resolver-typescript I have to add it to the dev deps of my project. This aligns with the general guidance of dependency management, but might create discrepancies between the version that is provided by eslint-config-airbnb-extended and the version that was installed manually, which is not ideal.

May I suggest to re-export createTypeScriptImportResolver via the new helpers object instead?

[NishargShah]

Anyway, it sounds like in case I need to rely on anything explicitly imported from eslint-import-resolver-typescript I have to add it to the dev deps of my project. This aligns with the general guidance of dependency management, but might create discrepancies between the version that is provided by eslint-config-airbnb-extended and the version that was installed manually, which is not ideal.

I think this problem will occur in all the packages, I suggest to add it in your package json because I am planning to frequently update the package when minor version of any package is changes ( not patch version ), so you will not get discrepancies between the packages.

May I suggest to re-export createTypeScriptImportResolver via the new helpers object instead?

This is hard to do, exposing functions may create confusion in future so this is not the good idea.