You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[warning] The glob ./src/index.ts did not match any files
[info] Try replacing Windows path separators (\) with posix path separators (/)
[error] Unable to find any entry points. See previous warnings
[error] Found 1 errors and 1 warnings
[warning] The glob ./src/index.ts did not match any files
[error] Unable to find any entry points. See previous warnings
[error] Found 1 errors and 1 warnings
Though this failure is not really typedoc's fault because this results in a path like C:\Users\electrovir\repo/src/index.ts since import.meta.dirname reports the path in Windows format.
Actual working version
After this I tried dozens of different path construction and conversion techniques. I finally ended up with one that works:
Relative locations originating in a config file are considered relative to the config file, I suggest:
exportdefault{entryPoints: ["src/index.ts"],}
When printing errors about path separators, typedoc definitely shouldn't normalize the path.
Requiring / path separators is necessary because entryPoints (and some other options) are not arrays of paths, but arrays of globs, and \ is an escape character there. Without this breaking change in 0.28, it isn't possible to properly escape special characters in globs - #2825.
Search terms
Expected Behavior
Can easily run typedoc on Windows file paths.
Actual Behavior
Most formats simply don't work.
First attempt (Windows path entry point)
typedoc --options typedoc.js
with:errors out with the following:
Second attempt (posix path entry point)
So I used
node:path/posix
instead:This errors out as well:
Though this failure is not really typedoc's fault because this results in a path like
C:\Users\electrovir\repo/src/index.ts
sinceimport.meta.dirname
reports the path in Windows format.Actual working version
After this I tried dozens of different path construction and conversion techniques. I finally ended up with one that works:
Steps to reproduce the bug
https://github.com/electrovir/typedoc-windows-path-issue/blob/dev/typedoc.js
Environment
The text was updated successfully, but these errors were encountered: