fix: replace aliased imports for tsx and jsx files #1554
Merged
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?
Commands like
nest start
andnest build
replace the path of imports using path aliases with its relative path.But this currently fails for imports pointing to a
.tsx
orjsx
file.Issue Number: #1547
What is the new behavior?
Path aliases are replaced not only for imports pointing to
.ts
and.js
files, but for.tsx
orjsx
also.Does this PR introduce a breaking change?