typedoc "Option 'entryPointStrategy' could not be resolved" error

TL;DR

Set entryPointStrategy to one of the valid values: resolve, expand, or packages. The error means the value is misspelled or comes from a different TypeDoc version's vocabulary.

Error

Error: Option 'entryPointStrategy' could not be resolved.

Steps

1. Open typedoc.json (or the CLI args) and read the current entryPointStrategy value. Expected: you see the exact string TypeDoc rejected.
2. Replace it with a valid value for your layout: resolve for explicit file globs, expand to expand directories, packages for monorepo package discovery. Expected: the value is one of the three.
3. Check your TypeDoc version with npx typedoc --version; older versions predate some values. Expected: version 0.24 or newer for all three values.
4. Re-run npx typedoc. Expected: the option resolves and conversion starts.

When to use

• TypeDoc errors on the entryPointStrategy option specifically
• A typedoc.json was copied from a blog post for a different version
• A docs agent invented an option value

When not to use

• The option resolves but entry points are wrong (different problem)
• You are on a TypeDoc version where the option does not exist at all (upgrade instead)
• The error names a different option

Tool compatibility

TypeDoc 0.24 through 0.28. The valid value set has been stable across these releases.

Variant phrasings

entryPointStrategy worked before a TypeDoc upgrade

Rare, but check the changelog: option vocabularies do change across majors. Pin or update the value.

using packages strategy in a single-package repo

Switch to resolve with explicit entry points; packages expects a packages directory layout.

Why it happens

TypeDoc validates option values against an enum. Copy-pasted configs and generated configs frequently carry values from other tools or other versions, and validation rejects them before any conversion runs.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_O5h7ydy632GJSi18bKaRVQ