You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
The entry point C:/...../libs/journeys/customers/src/customer.ts is not referenced by the 'files' or 'include' option in your tsconfig
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?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
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