fix: force emit types even when there're errors #320
Merged
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.
The dts plugin runs TypeScript to generate .d.ts files for .ts inputs. This often just works. However in some cases it still fails to fetch types from deep dependencies. I used to turn off all strict type-checking options to get rid of these errors, but today I found a special case which doesn't work in any option settings:
strictNullChecks: false
, the code above raisesUnused '@ts-expect-error' directive
.I only want to generate and bundle types and don't want to handle any type errors. So today I found that the TypeScript Playground actually can emit types even when there're errors in the code. After digging a while I found the hidden option to force emitting types.