It's kinda nice but "@type" breaks JSDoc and there are is tooling that can generate docs after that. =(
Discussion
Oops, meant to say "there is NO tooling"
Basically better to use @param and @return for JSdoc compatibility rather than free form metaprogram expression of @type
A smart IDE is my main tooling and the source code is my main documentation. I'm happy with that.
I hear ya, it's a popular workflow.
I'm not a fan IDE's.
Syntax highlights and tag based completion is enough for me.
Give me an interactive debugger and I'll build a full node in frontend. Lol