fix(vite): tsconfig paths plugin should not partially match paths #29501
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
|
View your CI Pipeline Execution ↗ for commit 89f15a8.
☁️ Nx Cloud last updated this comment at |
leosvelperez
approved these changes
Jan 7, 2025
FrozenPandaz
pushed a commit
that referenced
this pull request
Jan 7, 2025
…9501) <!-- Please make sure you have read the submission guidelines before posting an PR --> <!-- https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr --> <!-- Please make sure that your commit message follows our format --> <!-- Example: `fix(nx): must begin with lowercase` --> <!-- If this is a particularly complex change or feature addition, you can request a dedicated Nx release for this pull request branch. Mention someone from the Nx team or the `@nrwl/nx-pipelines-reviewers` and they will confirm if the PR warrants its own release for testing purposes, and generate it for you if appropriate. --> ## Current Behavior <!-- This is the behavior we have today --> When there is a path mapping like: ``` "match-lib-deep/": ["libs/lib1/src/*"], "match-lib-top-level": ["libs/lib2/src/*"], "match-lib/*": ["libs/lib3/src/*"], ``` Imports to `match-lib-deep` or `match-lib-top-level` will try and use the last `match-lib` path mapping as the trailing `/` is not accounted for in the `startsWith` check. ## Expected Behavior <!-- This is the behavior we should expect with the changes in this PR --> The correct path mapping is matched. ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> N/A (cherry picked from commit 6948249)
|
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Current Behavior
When there is a path mapping like:
Imports to
match-lib-deepormatch-lib-top-levelwill try and use the lastmatch-libpath mapping as the trailing/is not accounted for in thestartsWithcheck.Expected Behavior
The correct path mapping is matched.
Related Issue(s)
N/A