Repository navigation
Glob patterns starting with "*." and having multiple wildcards fails #8817
Description
What version of Bun is running?
1.0.26+c75e768a6
What platform is your computer?
Linux 6.5.0-15-generic x86_64 x86_64
What steps can reproduce the bug?
Considering following project structure:
project/
├ test/
│ └ example.test.ts
├ index.ts
├ package.json
└ tsconfig.json
With following index.ts content:
import { Glob } from "bun"
for await (const f of new Glob('*.test.*').scan({ cwd: "test" })) {
console.log(f)
}
console.log("done")What is the expected behavior?
According to Glob API, I would expect the following output:
$ bun run index.ts
example.test.ts
doneWhat do you see instead?
No file matches the given pattern
$ bun run index.ts
doneAdditional information
As a workaround, escaping the first dot seems to work correctly
new Glob('*\\.test.*')
Activity
pierre-cm commentedon Feb 9, 2024
I suspect the special fast-path matching used for components such as *.ts could be the culprit.
I believe that including * here might fix the issue.
Fix #8817
leaumar commentedon Feb 13, 2024
Just wanna add that escaping the dot doesn't work for me. I'm using 1.0.26 on windows/wsl. Globbing
*.mdand such in a folder works and lists files, but running the same code with*.*or*\\.*finds no matches.fix(glob): fix patterns starting with * #8817 (#8847)