-
Notifications
You must be signed in to change notification settings - Fork 710
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Specify compilerOptions via package.json config #2022
Comments
I'm not sure I want to add more special casing into the options parser... TypeScript does a similar thing, with a better error message when you do
TypeDoc's behavior should mirror tsc's.
|
That makes sense. Am I able to specify the compiler options from the package.json? It doesn’t seem to work either. {
"typedoc": {
"entryPoint": "src/index.d.cts",
"compilerOptions": {
"skipLibCheck": true
}
}
} |
Currently no, not supported. That key only lets you set the name/entry point/readme. PR welcome if you'd like to add support for that though :) src/lib/utils/entry-point |
One thing to note: that section of the package.json is only used in packages mode. |
Regarding setting the compiler options from package.json - I changed my mind. #2061 should meet this need. |
Search terms
error The 'compilerOptions' option must be a non-array object.
Expected Behavior
Typedoc works as expected:
Actual Behavior
Typedoc errors with:
Steps to reproduce the bug
Environment
Other
Really though, I would like to have
skipLibCheck: false
just like mytsconfig.json
, but that gives me a long TypeScript ESLint error and I couldn’t find an exclude or excludePattern that ignored it.The text was updated successfully, but these errors were encountered: