no-undefined-types regression for imported module types in v51.0.0

[Andrioden]

Expected behavior

Eslint pass OK without warning

Actual behavior

Eslint warns The type 'Ably.Realtime' is undefined jsdoc/no-undefined-types.

On v50.8.0 this do not occur.

ESLint Config

I have a lot of rules, but no related config to this warning

ESLint sample

External dependency (happens to both in exact same pattern as below)

package.json

  "dependencies": {
    "ably": "2.9.0",
    "konva": "9.3.20",
  },

code.js

import * as Ably from "ably"

export class Code {
    /** @type {Ably.Realtime} */
    static #client
}

Environment

• Node version: v22.14.0
• ESLint version eslint@9.29.0
• eslint-plugin-jsdoc version: v51.0.0

[azat-io]

Same problem.

[github-actions]

🎉 This issue has been resolved in version 51.1.3 🎉

The release is available on:

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

Your semantic-release bot 📦🚀

[brettz9]

Thanks for the report. The regression was due to our starting to check whether the properties actually exist. Unfortunately, in ESLint, we can't introspect on the whole project for imports and globals, so the fix I've provided now liberalizes the checks again not to care about imports and globals defined in a /* globals */ comment. Hopefully that will avoid undue complaints while still checking for any properties/methods' existence when defined within the file.