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
So, turns out that the undocumented configFilePath property that shows up in the return value from parseJsonConfigFileContent is important. If you delete it, then when you create a program without it you'll end up with a program that can't always find @types packages... When reworking the options, it showed up and since it didn't seem to do anything, I just deleted it. Restoring it and adding a dummy option for it fixes this.
Expected Behavior
Compile same as calling tsc directly when specifying path to tsconfig file.
Calling tsc directly from any directory like
tsc -project /path/to/some/far/away/tsconfig.json
works without any problems.Actual Behavior
Cannot find typings in node_modules folder that is in same folder as tsconfig file. Throws errors like "Cannot find module '<module_name>'.".
Steps to reproduce the bug
/my-library/src
)tsconfig.json
filenode_modules
folder@types
folder/my-library/docs
)package.json
file"typedoc --json api.json --tsconfig ../src/tsconfig.json"
Environment
Workarounds
"cd ../src && typedoc --json ../docs/api.json --tsconfig tsconfig.json"
--ignoreCompilerErrors
The text was updated successfully, but these errors were encountered: