Ability to match `glob` symlink behavior
I've been trying to switch @vercel/nft over to tinyglobby from glob. There's one failing test and I'm pretty sure it's because of the symlink behavior that glob has
From https://www.npmjs.com/package/glob:
By default, a ** in a pattern will follow 1 symbolic link if it is not the first item in the pattern, or none if it is the first item in the pattern, following the same behavior as Bash.
at first glance i think it is unlikely this will be added, fdir doesn't give information on whether a file is a symlink and there would need to be quite a lot of manual matching done to achieve this - not to mention it's not the behavior present in globby/fast-glob iirc
Perhaps it could be an option added to fdir...
maybe, but even then the tinyglobby side of the implementation would likely not be straightforward to add
Perhaps the fdir option could be a limit for number of symlinks to crawl. I don't think anything would have to change on the tinyglobby side then.
that wouldn't just apply to ** patterns though