-
-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ability to match glob
symlink behavior
#97
Comments
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 |
I've been trying to switch
@vercel/nft
over totinyglobby
fromglob
. There's one failing test and I'm pretty sure it's because of the symlink behavior thatglob
hasFrom https://www.npmjs.com/package/glob:
The text was updated successfully, but these errors were encountered: