Kræn Hansen

First off. Thanks a lot for stewarding and maintaining a valuable tool for the community! > TypeDoc's current function rules are so convoluted that I have to rediscover them every...

> a rather major change which will probably break >50% of TypeDoc's tests Yeah - it would probably be good to signal quite explicitly to developers, as they might have...

@brettz9 do you think something changed upstream that might make it more feasible to implement now? If you think this is possible and something you would take a PR for...

@brettz9: Looking more at the code, it looks to me as if the inline `{@link}` tag isn't supported at all. The parsed comment returned from `@es-joy/jsdoccomment`'s `parseComment` function via https://github.com/gajus/eslint-plugin-jsdoc/blob/ec278a292ed343ac875359d66acc4dd81301ec23/src/iterateJsdoc.js#L1141-L1149...

Just to clarify: Would you consider that the responsibility of `@es-joy/jsdoccomment` or do you think it'd be reasonable to implement that in `eslint-plugin-jsdoc` (which would probably be the easiest for...

@brettz9 I started working on this: https://github.com/gajus/eslint-plugin-jsdoc/pull/1058, so perhaps you can assign the issue to me? Note that this is still draft and I have outstanding tasks (see the PR...

> there might be cases in which it is possible to argue in favor of es6 imports. I wanted to share my use-case: The code that will be relying on...

> I think we can probably close this issue therefore I agree. I just tested and `/** @type {MyClass} */` does indeed mark `MyClass` as used with `no-undefined-types` enabled.

@mprobst I think it would it make sense to archive the repo and push a deprecation to NPM as well, to avoid additional users starting to rely on it.

I can verify this is still an issue. This is the output from running `npm audit` in a repository with the latest version of `nw-gyp` installed: ``` tar