All main generations of "JSDoc" were headed by micmaths (Michael Mathews). He started with JSDoc.pm in 2001, a simple system written in Perl, in cooperation with Canadian programmer Gabriel Reid. It was hosted on SourceForge in a CVS repository.[3] By JSDoc 1.0 (2007) he rewrote the system in JavaScript (again for Rhino), and after a set of expansions JSDoc 2.0 (2008) gained the name "jsdoc-toolkit". Released under the MIT License, it was hosted in a Subversion repository on Google Code.[4] By 2011 he has refactored the system into JSDoc 3.0 and hosted the result on GitHub. It now runs on Node.js.[1]
Then what else would they want to add to their stack? Notice one doesn'tnecessarily need the TypeScript Compiler to add TypeScript- or Flow-liketype annotations and remove them in a build step - Babel for examplecould do that just fine as well.Or are you asking for a jsdoc-like thing that lives in comments, wherethe code can be run without a compilation step?
This feels like rich territory for a blog post, if someone feels qualified? Specifically, just running the typescript tool chain for jsdoc annotations, which are excellent for all the reasons mentioned above (comments only, vanilla js etc).
08ab062aa8