Bug: URL in `@see` tag is incorrectly truncated at the equals sign `=`

[astrochemx]

Bug Description

When formatting a JSDoc block containing an @see tag with a URL that includes query parameters, prettier-plugin-jsdoc incorrectly truncates the URL right before the = character. It strips out the rest of the query string and the hash fragment.

Input

/** @see https://github.com/lint-staged/lint-staged?tab=readme-ov-file#how-can-i-resolve-typescript-tsc-ignoring-tsconfigjson-when-lint-staged-runs-via-husky-hooks */

Output (Actual behavior)

/** @see https://github.com/lint-staged/lint-staged?tab */

Expected behavior

The URL should remain completely intact and not be truncated:

/** @see https://github.com/lint-staged/lint-staged?tab=readme-ov-file#how-can-i-resolve-typescript-tsc-ignoring-tsconfigjson-when-lint-staged-runs-via-husky-hooks */

Steps to Reproduce

1. Create a JavaScript file with the provided input JSDoc comment.
2. Run Prettier against the file with prettier-plugin-jsdoc enabled.
3. Observe that the URL in the @see tag is destructively truncated after ?tab.

Environment

• Prettier Version: 3.8.3
• prettier-plugin-jsdoc Version: 1.8.0
• Node.js Version: 26.1.0
• OS: Windows 11 x64

[moltar]

Looked into this — root cause is in comment-parser@1.4.6, not directly in this plugin. Filing here too because there's a complementary fix worth doing on the prettier-plugin-jsdoc side.

Filed upstream: syavorsky/comment-parser#190.

Root cause

comment-parser@1.4.6 (PR syavorsky/comment-parser#189, released 2026-03-28) extended nameTokenizer to split any non-optional name on = and stuff the right-hand side into default. The intent was @property {number} BITMASK_VALUE_A=16, but the rule fires for any name containing = — including URLs in @see.

For @see https://example.com/foo?bar=baz#section, nameTokenizer now returns:

{ tag: 'see', name: 'https://example.com/foo?bar', default: 'baz#section', optional: false }

Why this plugin then drops the rest

In dist/parser.js, every tag is passed through assignOptionalAndDefaultToName. That function only restores name = ${name}=${default} when optional === true (the [name=default] bracket form). For @see, optional is false, so default is silently discarded.

Then in dist/stringify.js, @see emits only name:

if (name)
  tagString += `${gap}${name}${" ".repeat(tagNameGapAdj)}`;

So baz#section is lost on output.

Suggested fix on this plugin's side

Even after comment-parser is fixed, it's worth hardening the round-trip here so a similar regression upstream can't silently truncate user content again. Two reasonable options:

1. In assignOptionalAndDefaultToName, when default_ is present but optional is false (and the tag isn't one where defaults make semantic sense — @param, @property, @default), restore name = ${name}=${default_} so the original text survives.
2. Alternatively, in stringify, treat a non-empty default on a non-optional tag as a signal to emit ${name}=${default} for name-only output paths.

Either approach makes the plugin lossless for free-form name slots like @see URLs regardless of what the tokenizer does.

Workaround until released

Pin comment-parser to 1.4.5:

"pnpm": { "overrides": { "comment-parser": "1.4.5" } }

Confirmed in isolation by repointing the resolved version in node_modules and re-running prettier --plugin=prettier-plugin-jsdoc on the affected file.