Replies: 1 comment
-
Unlikely, but I make no promises, behavior around how TypeDoc behaves when warnings/errors are emitted is always subject to change if a better method of handling it is discovered.
This sounds like the point of TypeDoc's packages entryPointStrategy option, where TypeDoc is run in each package and the results merged to create a single site. It won't quite produce the same output as your current setup, but might be a better fit. (Given "hundreds of libraries", this unfortunately will also likely be slower as it has to start the compiler for each library) |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I'm working with an Nx monorepo containing several Angular applications and hundreds of libraries, some of which expose secondary entry points. When generating documentation using TypeDoc for each application, I want it to include all relevant .ts files from the application itself, as well as those from the libraries the application depends on.
Currently, this setup appears to work as intended using the following configuration:
However, I'm receiving the following warnings:
From what I can tell, these warnings only appear for libraries that are not actually used by the specific application being documented. Despite the warnings, the documentation is generated correctly.
My questions are:
Will these warnings cause issues in future TypeDoc releases?
Is there a recommended way to configure TypeDoc to suppress these warnings or ensure only the used libraries are scanned?
Thank you in advance for your guidance.
Beta Was this translation helpful? Give feedback.
All reactions