Glob Pattern Tester

`*` for any characters except a path separator, `**` for matching across directory boundaries, `?` for exactly one character, `[abc]` character classes, and `{a,b,c}` brace alternation — the same core glob tokens used by `.gitignore`, most bundler "include"/"exclude" config, and shell globbing.

A single `*` matches any run of characters but stops at a `/` path separator, so it only matches within one directory level, while `**` matches across any number of directory levels, which is why patterns like `src/**/*.ts` are needed to match files nested arbitrarily deep.

Yes — paste as many sample paths as you like into the paths box, one per line, and every path is checked against the current pattern simultaneously, with a checkmark or cross shown next to each.

It implements the common core glob syntax those tools share, but doesn't replicate every edge case or extension-specific behavior (like `.gitignore`'s special leading-slash and directory-only trailing-slash rules), so always double-check unusual edge cases against your actual tool's documentation.

Glob patterns in build configs, `.gitignore` files, and CI workflows are notoriously easy to get subtly wrong — testing a pattern against real sample paths before committing it to a config file catches mistakes immediately instead of discovering them when a build silently includes or excludes the wrong files.