A programmatic interface for jsdoc3 with a few extra features
MIT License
Bot releases are visible (Hide)
~/.jsdoc-api/cache
instead of os.tmpdir()
. See #19.jsdoc
child process, the maxBuffer used is now 100MB to help users processing huge amounts of input #24Published by 75lb about 2 months ago
There are no changes to the jsdoc-api output.
.explain()
and .render()
are now async-only.{ pedantic: false }
confused the underlying jsdoc. #22.source
. #11/examples
folder.explainSync()
with await explain()
and renderSync()
with await render()
.Published by 75lb almost 2 years ago
taffy-db
with a handrolled polyfill.Published by 75lb about 8 years ago
.createExplainStream()
).The main (and possibly only) benefit of streams is the ability to receive and process data as it is being created, without first needing to wait for the data source to finish. However, jsdoc-api was unable to supply output to .createExplainStream()
before the underlying jsdoc
process had completed, thus leaving no reason for the streaming interface to exist.