fix(compiler): support synthetic module specifiers#3453
Merged
Conversation
Typia can produce synthetic import and export string literals during TypeScript 6 transforms. The tsconfig-paths hook called getText() on the module specifier, which asserts on nodes without real source positions and stops debuggers on the caught exception. Read moduleSpecifier.text when it is available, fall back to getText(sourceFile) for source-backed nodes, and cover the behavior with a regression test for synthetic literals.
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
2 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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Typia can produce synthetic import and export string literals during TypeScript 6 transforms. The tsconfig-paths hook called getText() on the module specifier, which asserts on nodes without real source positions and stops debuggers on the caught exception.
What is the new behavior?
Read moduleSpecifier.text when it is available, fall back to getText(sourceFile) for source-backed nodes, and cover the behavior with a regression test for synthetic literals.
Does this PR introduce a breaking change?
Other information