Investigate improving "could not find entry point" error messages

[Gerrit0]

Search Terms

Unable to find any entry points. Make sure TypeDoc can find your tsconfig.

Problem

TypeDoc's errors/warnings when determining entry points could use a lot of user experience improvements. The "make sure TypeDoc can find your tsconfig" message that is printed might have usually been the problem several years ago, but now that we use TypeScript's API to find a tsconfig file, it's very rarely the issue. In my experience it is far more likely that:

• A file was included that was not included in the program (we should tell the user the path exists, but isn't included in the tsconfig)
• The user provided a directory/file when TypeDoc expected a file/directory (common when first setting up packages mode)
• Packages mode was given a directory without workspaces, and expected to expand them (Update typedoc.json Gerrit0/typedoc-packages-example#3)

Suggested Solution

Spend some time trying to break entry points in every way imaginable, and provide better error messaging describing what went wrong.

See also:

• V0.24.2 does not work #2241
• Failed to find any packages in pnpm workspace #2238
• The entry point ./lib does not exist or is not included in the program for your provided tsconfig. #2177
• How to correctly use multiple entrypoints with root entry? #2173
• Typedoc do not work with PNPM workspaces #2149
• Why does typedoc foo.ts report Error: Unable to find any entry points #2080
• Probably a ton more

[Gerrit0]

Note: I am excluding legacy-packages from this investigation, as it will be removed in 0.25 and I don't want to waste time on it.