"typedoc" conditional exports in package.json not working

[ibc]

I'm writing a package whose "exports" field in package.json looks as follows:

"exports": {
	"./packets": {
		"types": "./lib/packets.d.ts",
		"import": "./lib/packets.mjs",
		"require": "./lib/packets.cjs",
		"typedoc": "./src/packets/public.ts"
	},
	"./utils": {
		"types": "./lib/utils.d.ts",
		"import": "./lib/utils.mjs",
		"require": "./lib/utils.cjs",
		"typedoc": "./src/utils/public.ts"
	}
}

In typedoc.config.mjs I don't add entryPoints since I expect Typedoc to read them from "exports" in package.json. But it doesn't work:

[warning] No entry points were provided or discovered from package.json exports, this is likely a misconfiguration

I've tried adding this in tsconfig.json in "compilerOptions" (because I've seen it somewhere):

"paths": {
  // These correspond to the public API imports as defined in "exports" in
  // package.json.
  "packets": ["./src/packets/public.ts"],
  "utils": ["./src/utils/public.ts"],
}

The result is the same as above.

Am I missing something? By reading the docs I think I'm doing it ok:

entryPoints

If this option is not set, TypeDoc will automatically discover your entry points according to the "exports" or "main" fields in your package.json, using your tsconfig options to map the JavaScript files back to the original TypeScript source.

If a "typedoc" conditional export is used, TypeDoc will use it instead of the "import" export condition.

[Gerrit0]

Per the Node docs:

Within the "exports" object, key order is significant. During condition matching, earlier entries have higher priority and take precedence over later entries. The general rule is that conditions should be from most specific to least specific in object order.

TypeDoc respects this, so it finds import before typedoc and therefore uses it.

[ibc]

Oh true, sorry, I missed thtat.

BTW something important: The "typedoc" entry must not just be above "import", but also above "types", otherwise same error as above happens.

[ibc]

Once fixed (thanks), I see a non making sense error log when running typedoc --watch:

[info] Starting compilation in watch mode...
[error] Unable to find any entry points. See previous warnings
[info] Found 0 errors. Watching for file changes.

Interesting things here are that:

1. "see previous warnings" but there are no previous warnings.
2. Such an error should make the command fail, but it doesn't.
3. Such a error log doesn't show up if I just run typedoc or typedoc --emit none.

Remember that, as said in comments above, I don't set entryPoints because I do rely on "typedoc" entry in "exports" field in package.json.

[Gerrit0]

Watch mode is annoying and special. It requires a different code path, which didn't get updated when I added support for inferring entry points. That's a bug, #2899