-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add possibility to generating documentation for non component libraries #3940
Comments
@floratmin would it be possible to share some example repo on how did you set it up please? |
@kmaraz That's the target I added to "docs": {
"executor": "@nrwl/workspace:run-commands",
"options": {
"commands": [
{
"command": "yarn typedoc --tsconfig libs/my-lib/tsconfig.lib.json --out docs/my-lib libs/my-lib/src/index.ts"
}
]
}
}
|
I am also confused with setup typedoc integration with multiple packages in nx monorepo. |
This issue has been automatically marked as stale because it hasn't had any recent activity. It will be closed in 14 days if no further activity occurs. |
+1 |
1 similar comment
+1 |
I would expect that it should be possible to create one documentation from the root of the project with all libraries as modules. But as stated in TypeStrong/typedoc#1791 in seams that typedoc is not able to distinguish modules/libraries. |
This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context. |
Description
Add a document generator to nx workspaces to generate documentation for non-component libraries.
Motivation
With storybook there is a very good tool to document components. But for plain libraries there is no such tool for generating documentation.
Suggested Implementation
With typedoc there is an excellent generator. With the help of typedoc.json files in each library we can generate documentation for each library separately. This can already be easily realized with a simple @nrwl/workspace:run-commands. But an integration into library creation could make this process more straight forward.
The text was updated successfully, but these errors were encountered: