Fix crash on attempting to suggest a ts import for a synthetic js resolution #41467
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 #41410
After looking at it a bit, I realized we were checking if
ignoreErrors
was set, but were unconditionally making a diagnostic because we wanted to try and offer a suggestion (namely, a suggestion to try to install types for it when the js seems to be present, but not any types). I simply changed our suggestion-or-error adding function to more gracefully handle the psuedo-synthetic nodes we use for some compiler-option-added imports. Now that I know how it works, I can say it was theoretically possible to trigger the same issue withimportHelpers
, but you'd have needed to have atslib
on disk with no accompanying types, which is obviously not what we distribute (therefore very unlikely to occur).