[api-extractor] Allow for loading the ExtractorConfig
without validating existence of target typings
#3472
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Allow for loading the
ExtractorConfig
without validating existence of target typings.Details
There are some scenarios where loading up the API-Extractor configuration is required prior to the existence of the typings files that API Extractor sources from (such as obtaining output folder paths and ensuring they are empty). This PR adds the option
ignoreMissingConfigTargets
which can be passed into theExtractorConfig
options at load time to avoid validating the existence of the target files.How it was tested
Forked off of PR #3468 where it was tested extensively against the rest of the Rushstack monorepo.