no-extraneous-dependencies causes errors for not imported @types/*

[alan-albuquerque]

Hello I'am facing a similar issue reported here and there @ljharb asked to open another issue if it is still happening on version 2.23.4.

My scenario is:
node: v12.22.1

import { difference } from 'ramda';
import { v4 as uuid } from 'uuid';

causes:

  error  '@types/uuid' should be listed in the project's dependencies, not devDependencies  import/no-extraneous-dependencies
  error  '@types/ramda' should be listed in the project's dependencies, not devDependencies  import/no-extraneous-dependencies

package.json

"eslint": "^7.31.0",
"eslint-plugin-import": "2.23.4",

config:

"import/no-extraneous-dependencies": [
            "error",
            {
                "devDependencies": ["**/*.d.ts", "**/*.test.*", "**/*.spec.*", "test-utils/**/*"]
            }
        ]

Am I doing something wrong?

[JounQin]

Can you provide a reproduction?

[DonIsaac]

I'm seeing this problem as well. My config is simlar, and my versions are below:

• eslint-plugin-import: 2.27.5
• eslint-plugin-import-resolver-typescript : 2.23.5
• typescript: 5.0.4
• typescript-eslint/parser: 5.48.0

[AndyOGo]

I had the same problem with packages from @types/*, e.g. @types/react.
For my case I just needed to allow peerDependecies for react.

import { useEffect, useState } from "react";

'@types/react' should be listed in the project's dependencies, not devDependencies.eslintimport/no-extraneous-dependencies

[ahuth]

I think import-js/eslint-import-resolver-typescript#265 may be the cause of this

[JounQin]

Duplicate of import-js/eslint-import-resolver-typescript#265

[JounQin]

Please follow the README more carefully:

https://github.com/import-js/eslint-plugin-import#typescript

See also

eslint-plugin-import/config/typescript.js

Line 17 in 7a21f7e

'import/external-module-folders': ['node_modules', 'node_modules/@types'],

[ljharb]

More generally, please use the config/typescript config from this plugin, which sets that.