Use relative module specifiers in error messages if possible #27441
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 #25747
We don't create node module specifiers since within the checker during checking because we don't really have access to the FS to do the
fileExists
andreadFile
calls to check if a given possible representation is valid. Naturally, if it seems it's necessary (ie, we dislike./node_modules/foo/bar
in errors enough) we can rig something up to pass them through from the compiler host.