Open robin-anil opened 4 years ago
Is type-coverage correctly passing cwd as the base path? Reading that bug it sounds like it ought to do that to handle code bases like mine with relative paths
I don't know how to do something to fix this bug. If there is a workaround, PR is welcome.
I haven't dug into this code base, so it may take some time for me to issue a patch. but I can show you that the following works. So if you can resolve to absolute path when you parse the tsconfig.json it may fix it.
npx type-coverage -p /Users/robinanil/work/admin/dashboard/tsconfig.json 363638 / 382102 95.16% type-coverage success.
I cannot figure out how to do this with typescript-coverage-report -- they don't seem to have a -p option. So the fix may need to go directly into code
Version(if relevant): 2.6.1
tsc runs successfully from the same folder. by type-coverage or typescript-coverage-report both errors out with the same stacktrace
Environment(if relevant):
Mac OS