report an error when a package imported in a `@type` is not present in `package.json`

[DetachHead]

Motivation

i use import/no-extraneous-dependencies to ensure that i don't accidentally install and import dependencies without adding to package.json.

it would be nice to have that functionality in jsdoc @types as well

Current behavior

no error when eslint and/or @types/eslint is not present in dependencies or devDependencies in `package.json

/** @type {import('eslint').Linter.ParserOptions} */
const foo = {}

Desired behavior

error

Alternatives considered

raised an issue on eslint-plugin-import but it was suggested that i raise it here as it's apparently not able to check jsdocs - import-js/eslint-plugin-import#2508 (comment)

[brettz9]

Is this intended to catch the problem just a little earlier than running the compiler? Because TypeScript will, as I recall, report this kind of mistake if one is checking even plain JavaScript.

[DetachHead]

@brettz9 its for transitive dependencies or globally installed packages which the typescript compiler won't catch. In my example with the eslint type import, if I have eslint installed globally, or have another dependency that depends on eslint but eslint itself is not in my package.json's dependencies section, typescript won't care

[brettz9]

Ok, and you care about adding dependencies directly in case the transitive ones are ever removed by other dependencies?

[DetachHead]

Yep exactly. Another case I just remembered is when I remove a dependency from my package.json and forget to remove all of its imports, then all my tests still pass locally because I didn't actually uninstall it yet.

[github-actions]

🎉 This issue has been resolved in version 46.2.0 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)

Your semantic-release bot 📦🚀