Indeed, the interop story here isn't great. This is something we're looking at for future milestones.

I'm not sure how TypeScript can fix it without parsing the JSDoc comments and moving things around in the generated JavaScript, which is why I originally posted the issue on the JSDoc repo. Thoughts?

I'm not convinced the JSDoc team will accept responsibility for fixing this, even if they could. So far, my original issue report has been met with stone silence.

So maybe it's entirely up to the TypeScript team...

As I detailed in the original issue (https://github.com/jsdoc3/jsdoc/issues/272), the most painful part is that the comments must include explicit names for the namespace/class/members in order for the docs to be generated correctly, which is a maintenance nightmare. For example:

@namespace My.Namespace
@class My.Namespace.SomeClass
@constructor My.Namespace.SomeClass
@member My.Namespace.SomeClass#_someField
@method My.Namespace.SomeClass#_someMethod

Could the tsc compiler be modified to parse, validate, and augment comments as well? It could generate the necessary JSDoc tags/names for the JSDoc generator to work and even add additional tags that it detects are missing, e.g. @public, @private, @readonly, @type {string}, etc.

That would be sweet.

We've begun supporting a simple subset of JSDoc in TypeScript that is understood by the language service and by the Visual Studio plugin. Marking this as 'fixed'.