[valid-types] Using module path in @typedef throws error.

[alphanull]

I need a full module path in my typedefs to be able to reference those globally, for example:

@typedef {Object} module:src/core/Player~mediaFormat

Expected behavior

Should lint OK, as with versions prior to 60.8.1

Actual behavior

Since version 60.8.1, this results in an error when linting, so this might be a regression:

867:1 warning Syntax error in name: module:src/core/Player~mediaFormat jsdoc/valid-types

ESLint Config

'jsdoc/valid-types': 'warn'

Environment

• Node version: v22.13.1
• ESLint version v9.37.0
• eslint-plugin-jsdoc version: 60.8.2

[brettz9]

Have you tried with {settings: {jsdoc: {mode: 'jsdoc'}}}?

The default typescript mode should not support namepaths, especially that style of namepath in that position.

[alphanull]

@brettz9 this setting is already active:

settings: {
        jsdoc: {
            mode: 'jsdoc',
            tagNamePreference: {
                remove: 'remove',
                endremove: 'endremove'
            },
            preferredTypes: {
                object: 'Object'
            },
            structuredTags: {
                event: {
                    name: 'text',
                    type: true
                },
                listens: {
                    name: 'text',
                    type: true
                },
                fires: {
                    name: 'text',
                    type: true
                }
            }
        }
},

As stated, this worked before, did not change anything in my setup - except updating the plugin. (which had corresponding changes in 60.8.1 so I assume it is a kind of regression, at least the behavior is not the same)

[github-actions]

🎉 This issue has been resolved in version 60.8.3 🎉

The release is available on:

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

Your semantic-release bot 📦🚀

[alphanull]

Can confirm, bug went away. Thanks for the quick fix!