fix(paths): respect desired path on case-insensitive file systems #397
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
danielpza
approved these changes
Mar 10, 2025
danielpza
changed the title
|
The fix is published on version v3.5.4. Thank you for your contribution @denis-sokolov ❤️ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Today typescript-transform-paths changes the case of import statements on a case-insensitive file system. I have a file
Fooand an importfrom "./Foo", yet after the transformation with typescript-transform-paths, the import looks like"./foo". Even if that import would work on a case-insensitive file system, it seems clearly undesirable.Note that #187 does not fix the issue above.