fix: resolve Windows case sensitivity with -C option (#8510) #8550
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.
Fix Windows case sensitivity issue with npm query -C option
This PR resolves a critical Windows compatibility issue where
npm query .workspace -C "path"fails when the specified path has different case than the actual filesystem path. The issue affects both drive letter case (C: vs c:) and folder name case (CLI vs cli).What this fixes:
npm query .workspace -C "c:\project"works the same asnpm query .workspace -C "C:\project"npm query .workspace -C "d:\hrd\CLI"work when the actual folder is namedcli:path()selector now performs case-insensitive matching on WindowsHow it works:
workspaces/config/lib/type-defs.jsworkspaces/arborist/lib/relpath.js:path()pseudo-selector handles Windows case sensitivity inworkspaces/arborist/lib/query-selector-all.jsworkspaces/arborist/lib/arborist/load-actual.jsTesting:
References
Fixes #8510