Repro of tsup vs tsc handling of TypeScript declaration merging
#1637
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.
During the process of refactoring tech debt in
appconfigand the frontend, I encountered an issue with theYieldSourceIdtype, which is defined using TypeScript’s declaration merging feature. When imported into the UI, this type was incorrectly resolving tonever.Investigation & Discovery
After spending considerable time troubleshooting, I shared the issue on StackOverflow to gain insights.
Solution & Comparison
This PR introduces a minimal reproduction case that demonstrates the discrepancy in type resolution when building the
.d.tsdefinition file usingtscversustsup.tsc: The declaration merging behaves as expected, and the correct type definition is produced.tsup: The type unexpectedly resolves tonever.This PR serves as both documentation of the issue and a comparison of the behavior between the two build tools.