I use https://github.com/fabienb4/meteor-jsdoc. It generates a meteor-style documentation application from JSDoc documentation in your code. It supports inline markdown, and in my own fork you can also include .md files.
There is no search feature yet (except ctrl-f), but since everything is in one page, ctrl+f works pretty well.
Did anybody manage to run meteor-jsdoc on MacOS? I tried it some days ago, but I only got an empty documentation. And the maintainer says that he does not have a Mac to check if its running on this system.
Unfortunately (well, not really for me), I don’t have an IOS machine readily available to check with my own project, but I’m guessing that since you get an empty (working?) app out of it, it is the JSDoc that complains, but isn’t reporting what the problem is.
A few things to make sure though, you are using the @summary tag in your documentation? You ran meteor-jsdoc build?
Otherwise, I would clone the project and add a console.log in the actions file, and seeing what stdout and stderr is saying.
Not very user friendly unfortunately.
The @summary tag is required for the docs to be generated properly. Any method docs without it won't be processed by meteor-jsdoc.
Sometimes, error messages end up Here, in the logs.stdout callback variable, but I would definitely add a few @summary tags first and build again first. Check your doc project’s /client/data/ directory to see if the docs have been retrieved from your code, and be sure that your configuration file is set up correctly.
Hmm, for me it parses both my local project, and symlinked local packages in /packages, I see no restriction for the the /packages dir only, as per the build script. I don’t see why modules should be ignored as long as they can be found from the top level directory.
