Superchupu

both `tinyglobby` and `fast-glob` return results in an arbitrary order, which is documented at https://superchupu.dev/tinyglobby/comparison#ordering, you shouldn't rely on the results being sorted in any particular way on either of...

i think this pr is probably a bit overkill, it would need more handling for systems that don't support colors and it would increase bundle size for something that is...

just my two cents: after weeks of trying to replace globby with lighter alternatives i've published [`tinyglobby`](https://npmjs.com/package/tinyglobby) which only uses two subdependencies. maybe not outright switching to it but it...

as a suggestion, it'd be nice if it could show different values based on provenance coming from trusted publishing or not, like this: https://github.com/antfu-collective/taze/blob/54aeef30400423db32e7adda950ea3ecc2a9fe86/src/commands/check/render.ts#L68-L70

thanks for pinging me, this pr makes 9 tinyglobby tests fail: ``` test at test/index.test.ts:76:1 ✖ negative patterns setting root as / (2.92105ms) AssertionError [ERR_ASSERTION]: Expected values to be strictly...

i don't think `AbortController` can be avoided considering it's being used during the crawling process regardless of the options. if we checked for support and avoided using it then it...

marking as draft until you decide to drop node 14 👍

this would need support from `fdir` first, but i believe you can replicate the functionality by using `fs.stat` on the returned glob results meanwhile

thanks for the report, that is indeed very odd. i wonder if the latest fdir release has something to do with it. do you mind checking to see if it...

ah. can you try to update fdir and see if it works? 6.4.5 happened to fix a windows bug that we believe is a bug in node 😅