Don't track private symbol roots in other files during js declaration emit #55390
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.
Fixes #55375
The linked issue only repro'd with
strict: false
andstrictNullChecks: true
because without those set, we'd reuse input type nodes much more, and not reprint the union type for the field in theOption
type. When we traverse that field, we'd see theTest
member in another module, and mistakenly try to add it as something to print in the current file. Now, we have guards against actually doing that already, but traversing it at all caused us to reserve theTest
name for that symbol in the index file, and thus mangle the originalTest
name for the other symbol when we reprinted the import in the file later.