Glob Tester

How to use it

1. Type a glob pattern in the first field — for example src/**/*.{ts,tsx}.
2. Paste file names into the second field, one per line.
3. Each line is marked as matched or not matched in real time, with a running count.
4. The status line shows the compiled regex source, so you can see exactly how your pattern translated.
5. Load the sample to start from a working example.

Common use cases

• Build tool config — verify the include/exclude globs in tsconfig, ESLint or bundler settings before committing them.
• Ignore rules — check which files a .gitignore-style pattern would catch.
• CI scripts — confirm a copy or lint step will pick up exactly the files you expect.
• Learning glob syntax — compare * versus ** and see the difference immediately.

Why it stays private

Pattern matching runs through a locally compiled regular expression; nothing is uploaded. You can safely test patterns against internal file trees that you would not paste into an online service.

FAQ

Q: Which syntax subset is supported? A: * (within a path segment), ** (across segments), ? (single non-slash character), [abc] and [!abc] classes, and {a,b} alternatives, including nesting. Recursive brace expansion like {a,b/**} degrades to plain alternation.

Q: Why does ** sometimes swallow the following slash? A: A ** followed by / is treated as "any number of directories", matching the convention in most build tools. That is why src/**/*.ts matches both src/a.ts and src/x/y.ts.

Q: Are paths matched from the start? A: Yes. The whole file name must match the pattern, just like gitignore-style tooling. Anchor your pattern with **/ at the start if you want to match at any depth.