TypeScript emits incorrect type for setters in JSDoc

[remcohaszing]

🔎 Search Terms

jsdoc set

🕗 Version & Regression Information

• This changed between versions 4.2 and 4.3
• I was unable to test this on prior versions because 4.3 added support for separate write types on properties.

⏯ Playground Link

https://www.typescriptlang.org/play?ts=5.4.5&filetype=js#code/KYDwDg9gTgLgBAYwDYEMDOa4DUBiBLJYOAbwCg44B6AKmvIurgAEpgYBXKAO02LRih4uAcwC+9ONUr1hbOGBQwAFgAoAlCQlxWHbnADk++uPo06FScwVQUAWxIBVAEoAZOAB84-QSNHzFShJS9GhyCsoq4UoaZBTiJggQPPAAZgREALxwXMAA7tj4hOqkaYQAdFFwWfqUaBC2wJRRRqXAFQFV2Xlwzi4q+q0AXJQjdQ1NAfpqQA

💻 Code

export class VFile {
  /**
   * @returns {string}
   */
  get path() {
    return ''
  }

  /**
   * @param {URL | string} path
   */
  set path(path) {
  }
}

const file = new VFile()
file.path = '/some/path'
file.path = new URL('file:///some/path')

🙁 Actual behavior

• ✔️ The setter type annotation is used for type checking the setter
• ❌ The getter type annotation is emitted as the setter type in the .d.ts file

🙂 Expected behavior

The setter type annotation should be emitted as the setter type

Additional information about the issue

This only affects types in JSDoc. Correct types are emitted for the equivalent TypeScript code.