Add TypeScript configuration options for declarations#19
Merged
Conversation
24 tasks
gossi
approved these changes
May 12, 2026
gossi
left a comment
gossi
left a comment
There was a problem hiding this comment.
yes, I do have that settings on on my configs, too. Also the first one is sorta a requirement for tsdown dts generation
|
Can I get a tl;dr of the "why" we'd add to release notes about this? (Otherwise LGTM) |
gitKrystan
approved these changes
May 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Why
isolatedDeclarations: trueRequire sufficient annotation on exports so other tools can trivially generate declaration files (also boosts type-checking performance)
Why
erasableSyntaxOnly: trueAllows enforcement non-tsc-powered compilation to be used (required for rolldown, and other non-tsc tools)