-
-
Notifications
You must be signed in to change notification settings - Fork 737
Single-module documentation & entryPoint help needed #172
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
Comments
Almost the same issue. Except that I trying to create documentation on existing js module from |
Same issue here as well. I would love for this to become a feature! |
Just ran into this. Entrypoint needs to be the literal name of the module, including quotes. The quotes on the command you have are parsed by the CLI, so need to escape the quotes:
|
Note: this seems to only work with |
Still doesn't work, believe me I've trying all possible combinations and permutations for past 5 hours. Would really wonderful to see this working |
Possibly related: #639. |
Closing in favor of #639 |
I dug into the I recommend avoiding this option for the time being. |
works for me,
|
Hi, I have a project with a ts/ dir that gets built as a node module -- it has an "index.ts" which exports all the relevant symbols from other files in the dir, and the package.json refers to the built "index.js" as main. Ideally, the documentation would treat the "index" module as the root of the project, and show all exported symbols as relative to that root, but I'm having difficulty figuring out how to do that with typedoc.
It seemed like using entryPoint was the right option, so I tried this command:
But get this message:
Am I doing it wrong, or is what I'm trying to do not supported?
Simplified example code:
ts/index.ts
:ts/otherfile.ts
:The text was updated successfully, but these errors were encountered: