path: add exclude option to matchesGlob method #59061
Open
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.
This PR enhances the path.matchesGlob() method by adding comprehensive exclude pattern support to provide feature parity with fs.glob() and improve developer experience when filtering paths.
In the current implementation, path.matchesGlob() lacks advanced filtering capabilities, making it difficult for developers to exclude specific paths or directory trees without writing complex, error-prone manual exclusion logic. This limitation creates inconsistency between path matching utilities and forces code duplication across projects.
The updated implementation now includes:
This change resolves #59015 by providing the requested exclude functionality that allows developers to efficiently filter paths without manually implementing complex exclusion patterns, bringing path.matchesGlob() to feature parity with other Node.js glob utilities.