The documentation build is only available through the at-docgen CLI, which reads process.argv, calls process.exit, and runs its work as a side effect of import, so it cannot be triggered programmatically from a running application without spawning a child process.
The documentation build is only available through the at-docgen CLI, which reads process.argv, calls process.exit, and runs its work as a side effect of import, so it cannot be triggered programmatically from a running application without spawning a child process.