Add support for a typedocMain field in package.json.

[itsjamie]

This can be used to generate a tree of your source using tsc and point
at it to generate documentation outside your normal build process.

This takes a different tack and instead of falling back to the typings, this allows you to set a specific packageMain value that is built directly with TSC. This can act as an escape hatch for projects with weird builds that involve webpack / rollup / etc, and more complex typings setups with api-extractor to go along with the bundling.

For example, in our particular case, we use webpack 4 and api-extractor to bundle packages that are used at development time, but publicly are exposed as a single package. Therefore we bundle the TS via webpack and tsloader, and bundle the declaration files using an api-extractor rollup.

Resolves #1674.

[itsjamie]

Just a note, you don't even need to generate the tree with tsc outside the binary. You can literally point typedocMain at your entry point. Because you support running directly on the TypeScript source, this means no extra steps.

[cheelahim]

@Gerrit0 What's your take on this one? I have a few projects which would benefit from this option.

[Gerrit0]

I need to pull it down and play with it, fix the CI failure, add a test, and write some docs for it, it seems like an elegant solution though.

[Gerrit0]

TIL, GitHub's gh tool merges remotely :/ that's annoying, wanted to play with it first!

[itsjamie]

For future reference, If you want to use the gh tool locally, you could use: gh pr checkout 1677

[Gerrit0]

Good to know, thanks! This has been released in 0.22.0