René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Enhance `path.matchesGlob` to support exclusion patterns and options (parity with `fs.glob`)","articleBody":"\n\n### What is the problem this feature will solve?\n------------------------------------------------\nCurrently, the `fs.glob` function in Node.js allows specifying advanced options such as `exclude` patterns, which not only exclude the specified path but also all its descendants from matching results. In contrast, `path.matchesGlob` only matches a glob pattern to an input string without supporting exclude patterns or additional options.\n\nThere is no way to replicate the full matching logic of `fs.glob` (including exclude semantics) using `path.matchesGlob` alone on a list of paths, such as when working with a virtual filesystem.\n\nExample:\n  - `fs.glob({ include: '**/*', exclude: ['folder_a/folder_b'] })` will exclude `folder_a/folder_b` and all its contents.\n  - However, using only `path.matchesGlob`, one cannot easily achieve the same exclusion behavior because the exclude pattern only matches the exact path, not its descendants.\n\n\n### What is the feature you are proposing to solve the problem?\n----------------------------------------------------------\n- Allow `path.matchesGlob` to accept an options argument (e.g., `{ exclude: [...] }`, and/or other options supported by `fs.glob`).\n- Ensure that exclusion patterns work the same way as in `fs.glob`, i.e., they exclude the matched path and all its descendants.\n- This will enable users to apply consistent glob-matching logic both for real file systems and for lists of paths (e.g., in virtual filesystems or in-memory path lists).\n\nExample API:\n```js\nconst include = '**/*';\nconst exclude = ['folder_a/folder_b'];\nconst path = 'folder_a/folder_b/file.js';\npath.matchesGlob(path, include, { exclude }); // returns false\n```\n\n\n### What alternatives have you considered?\n--------------------------------------\n- Manually replicating exclusion logic by writing custom code to check if a path is a descendant of any excluded folder. This approach is error-prone and leads to code duplication.\n\n\nThe proposed enhancement would provide parity and consistency between `fs.glob` and `path.matchesGlob`, improving developer experience and flexibility.\n\n\n","author":{"url":"https://github.com/mizulu","@type":"Person","name":"mizulu"},"datePublished":"2025-07-10T01:15:29.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/59015/node/issues/59015"}