valid-types cannot parse links right after another tag

[LukeAbby]

Expected behavior

I expected @remarks {@link SomeType} to parse.

Actual behavior

I get an error saying it's invalid. I considered posting this issue on https://github.com/jsdoc-type-pratt-parser based upon the guidance in this issue format but I don't believe it's part of the concern of that library. It's probably being given an erroneous input.

ESLint Config

{
    "jsdoc/valid-types": "error"
}

ESLint sample

type SomeType = number;

// Ok
/** {@link SomeType} */

// Ok
/** @remarks foo bar lorem ipsum {@link SomeType} */

// Not ok
/** @remarks {@link SomeType} */

Environment

• Node version: v20.15.0
• ESLint version v9.26.0
• eslint-plugin-jsdoc version: ^50.6.11

[brettz9]

This is due to our use of the JSDoc-flavor-agnostic comment-parser. I don't have the bandwidth myself to switch to another parser like https://www.npmjs.com/package/@microsoft/tsdoc (it would surely necessitate a lot of changes) but PRs would be welcome.

[github-actions]

🎉 This issue has been resolved in version 50.6.16 🎉

The release is available on:

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

Your semantic-release bot 📦🚀