3 ms·
this is cool! are there any examples hosted anywhere? (the screenshot looks promising) -- and do you think it's fast enough to run the parser/generator on a clo
by eat_veggies 5y ago
this is cool! are there any examples hosted anywhere? (the screenshot looks promising) -- and do you think it's fast enough to run the parser/generator on a cloudflare worker or something? part of what makes godoc so nice is that you can just aim godoc.org (or pkg.go.dev) at the url of your repo and you don't have to generate or host it yourself
- zebracanevra 5y agoFor that use case, maybe try https://www.jsdocs.io/ https://www.jsdocs.io/ ? Works well in my tests. Here's some discussion from when it was last posted: https://news.ycombinator.com/item?id=27107832 https://news.ycombinator.com/item?id=27107832
- velut 5y agoHi, I'm the author of the website mentioned by zebracanevra that does just that. When a user requests the documentation for a package hosted on npm, a lambda function (Vercel/AWS) runs the analysis process using the TypeScript compiler. The TS compiler is slow though and this process can take several seconds to finish for packages of medium and larger sizes (you can see the exact time at the bottom of a generated documentation page).