Search terms
Failed, resolve, entry, point, path, typescript, source.
Expected Behavior
TypeDoc should automatically discover entry points according to the exports field in package.json and use tsconfig.json options to map the JavaScript files back to the original TypeScript source, as described in the documentation.
Actual Behavior
On Windows, each entry point results in a warning of Failed to resolve entry point path {0} from package.json to a TypeScript source file. This is because, in src/lib/utils/entry-point.ts, the JavaScript to TypeScript source map jsToTsSource is constructed with keys that are normalized via normalizePath, but when the map is later queried on line 90 (at time of writing), the path is not similarly normalized (forward slashes are used rather than backwards ones).
Steps to reproduce the bug
- On a Windows machine in a project that uses
exports, execute typedoc. No configuration is needed.
Environment
- TypeDoc version: 0.28.15.
- TypeScript version: 5.9.3.
- Node.js version: 25.2.1.
- OS: Windows 11.
Search terms
Failed, resolve, entry, point, path, typescript, source.
Expected Behavior
TypeDoc should automatically discover entry points according to the
exportsfield inpackage.jsonand usetsconfig.jsonoptions to map the JavaScript files back to the original TypeScript source, as described in the documentation.Actual Behavior
On Windows, each entry point results in a warning of
Failed to resolve entry point path {0} from package.json to a TypeScript source file. This is because, insrc/lib/utils/entry-point.ts, the JavaScript to TypeScript source mapjsToTsSourceis constructed with keys that are normalized vianormalizePath, but when the map is later queried on line 90 (at time of writing), thepathis not similarly normalized (forward slashes are used rather than backwards ones).Steps to reproduce the bug
exports, executetypedoc. No configuration is needed.Environment