Typedoc: TypeDoc renders main entry point containing only exports default and reexport declarations as empty

[octatone]

I have an entry point index.ts for my library that contains only an export default and export declarations:

import Main from './Main'
export default Main

export { default as State } from './state'
export { default as ThingModel } from './state/Thing/Model'
export { default as ThingCollection } from './state/Thing/Collection'

// etc ...

When I generate docs via TypeDoc it is an empty file. I would expect it to list what is exported from this module:

[aciccarello]

Hi @octatone, how are you calling/what are you using for your typedoc configuration.

[octatone]

via shell:
typedoc --options ./config/typedoc.js --out ./docs ./src

typedoc.js:

module.exports = {
  mode: "modules",
  module: "umd",
  target: "ES5",
  externalPattern: "node_modules",
  excludeExternals: true,
  excludePrivate: true
}

index.ts lives at ./src/index.ts

I get the same empty output regardless of options or no options (default options).

[chrisprice]

From a quick poke around, am I right in thinking this behavior is because typedoc only supports ts.SyntaxKind.ExportAssignment and the export syntax in use is ts.SyntaxKind.ExportDeclaration?

[pluma]

I'm guessing this isn't going to be fixed anytime soon?

[pabloFuente]

And how can the export syntax be changed from ExportDeclaration to ExportAssignment? Any idea?

[Gerrit0]

This will be fixed by #801

[pluma]

801 was closed and replaced by #1157, which has been merged. I can't seem to get reexports to show up with the latest release, though.

[Gerrit0]

Could you set up an example repo showing this problem? The tests for it are passing... seems to be working for me.

[pluma]

Here's my setup:

index.ts
typedoc.json

Only the default export shows up in the documentation:

[pluma]

Ah, nevermind, explicitly changing it to export {...} from syntax fixes this. Re-exporting the imports doesn't work though.

[Gerrit0]

Ah, that makes some sense. Yet another reason coming back to why we need to use the type checker to get this information instead of walking the node tree and trying to figure it out ourselves... Glad you found a workaround for now.