Skip to content
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

Single-module documentation & entryPoint help needed #172

Closed
mattucf opened this issue Jan 8, 2016 · 9 comments
Closed

Single-module documentation & entryPoint help needed #172

mattucf opened this issue Jan 8, 2016 · 9 comments
Labels
bug Functionality does not match expectation

Comments

@mattucf
Copy link

mattucf commented Jan 8, 2016

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:

typedoc --module commonjs --moduleResolution node -t ES5 --noImplicitAny --out docs --excludeExternals --entryPoint "index" ts/index.ts

But get this message:

Warning: The entry point `index` could not be found.

Am I doing it wrong, or is what I'm trying to do not supported?

Simplified example code:

ts/index.ts:

import * as blahmod from "./otherfile"
export let blah:string = blahmod.blah;

ts/otherfile.ts:

export let blah:string = "Just a string";
@Guria
Copy link

Guria commented Jan 29, 2016

Almost the same issue. Except that I trying to create documentation on existing js module from .d.ts file
Also can't find a way to treat my module as root.

@jvilk
Copy link

jvilk commented Aug 29, 2016

Same issue here as well. I would love for this to become a feature!

@kamranayub
Copy link
Contributor

kamranayub commented Dec 31, 2016

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:

typedoc --entryPoint \"index\"
or
typedoc --entryPoint ""index""

@demurgos
Copy link

Note: this seems to only work with --mode modules (not --mode files). Also, it only outputs the content of this file (not the content of other files).

@zikaari
Copy link

zikaari commented Jan 15, 2018

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

@FranklinYu
Copy link

Possibly related: #639.

@aciccarello
Copy link
Collaborator

Closing in favor of #639

@aciccarello aciccarello added the duplicate This duplicates another issue label Nov 17, 2018
@aciccarello aciccarello added Priority: 3 and removed duplicate This duplicates another issue question Question about functionality labels Feb 9, 2019
@aciccarello
Copy link
Collaborator

I dug into the --entryPoint option a little more and it appears completely broken. Even when TypeDoc finds the reflection, the links do not work correctly.

I recommend avoiding this option for the time being.

@aciccarello aciccarello reopened this Feb 9, 2019
@aciccarello aciccarello added the bug Functionality does not match expectation label Feb 9, 2019
@Bnaya
Copy link

Bnaya commented Oct 11, 2019

works for me,
when running it from package.json scripts, it needs Über escaping

"generate-docs": "rimraf -f generated-docs && typedoc --out generated-docs/ --readme none --entryPoint \"\\\"index\\\"\" --excludeNotExported --ignoreCompilerErrors --mode modules src/index.ts"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Functionality does not match expectation
Projects
None yet
Development

No branches or pull requests

10 participants