FILE PATHS & PATTERNS
Enter one glob and one path per line. Choose the matching library and adjust its options below.
Patterns and paths are processed in this browser; no files are read or changed.
Enter a pattern and at least one candidate path.
Windows separators converts \ to / in the pattern and paths. Use POSIX when \ is an escape. Case remains a separate option.
One pattern. Empty path lines are skipped; spaces and duplicates are preserved. Native ! and # semantics depend on the selected library.
Limits: 256 units per pattern, 200 paths, 512 per path, 131,072 total UTF-16 units; 1,000 minimatch brace alternatives; 2-second worker limit.
Results are outdated or being calculated.
A build includes too many files, or a watcher misses a nested directory: the pattern alone may not explain it. This Glob tester lets you hold a candidate list steady while changing the engine and its options, so you can isolate the cause before editing a configuration.
Use the glob pattern tester as a wildcard matcher for representative paths, including one expected hit and one expected miss. A minimatch tester is only useful when its settings match your project; copying a successful pattern between unrelated glob implementations can change its meaning.
The Glob tester makes depth visible through per-path results. Compare src/*.ts with src/**/*.ts: the first selects immediate children, while the second also reaches nested candidates. Original line numbers let you find the exact test case without reorganizing your list.
A normal source file can keep matching while a hidden sibling changes state when dot is enabled. The prefilled sample includes both. Case sensitivity is a separate setting, so enabling hidden files will not quietly include an uppercase extension.
Read the package and version used by your build tool. The selector exposes minimatch 10.2.6 and picomatch 4.0.7; their defaults and advanced syntax do not form a universal shell dialect.
Use POSIX for / paths and escaping. Windows separators replaces backslashes in both the pattern and candidates before matching, while preserving the originals in the report.
Automatic testing runs after a 350 ms pause. Turn it off for explicit testing with the button or Ctrl/Cmd + Enter. Changes immediately disable exporting the previous report.
This Glob tester calls the selected dependency directly. The report records its version, pattern, options, original paths and tested paths, which makes a case or separator experiment reproducible.
Test single characters with ?, character sets with [abc], directory traversal with ** and alternatives with {js,ts}. Positive extglobs such as @(foo|bar).js are also handled by the engine, without replacing your pattern with a homemade approximation.
With basename enabled, a slash-free pattern such as *.js can select src/app.js. A pattern containing / continues to test the path. This distinction helps explain why an extension filter works in one build configuration and misses files in another.
Each candidate retains its original line number and a match or no-match status. Duplicate paths remain separate rows. The complete JSON report includes misses too, so reviewing a filter does not erase the negative cases that justify it.
An ordinary star stays within one directory segment. For recursion, put ** in its own segment, as in src/**/*.ts. Adding another star inside a filename is not a portable replacement for a recursive directory segment.
Yes. A pattern such as *.{js,ts} tests either extension with both engines. Minimatch also expands ranges such as file{01..12}.js. Picomatch has different range behavior, so verify numbered alternatives with representative candidates.
Yes by default. Enable Ignore case to use nocase. For example, **/*.ts normally misses APP.TS; the switch changes that behavior without changing which hidden directories are traversed.
The directory segment ** can consume zero directories. Try src/*/*.ts if you need exactly one intermediate level; keep a direct child and a nested child in the list to check that requirement.
The default dot setting is false in both engines. Enable Include dotfiles to allow implicit matches of dotted segments, or name the dot explicitly in the pattern. For example, src/.hidden.ts can be selected by its literal path without enabling dot.
Found a path case worth checking?
Keep the expected match and miss beside each other, change one option, then save the current report.