Superchupu
Superchupu
by the way this can be worked around by doing `ignore: ['*(../)**/*']`
`fast-glob` and `glob` do this too. will likely remain intended unless this behavior changes in other libraries 
i believe that the library intentionally doesn't use newer node features to maintain compatibility, if the `engines` field is added it should reflect on what versions it works in even...
adding an engines field to anything above `>=12.0.0` would be a breaking change for `tinyglobby` users btw, would it be possible to keep engines compatibility with node 12 at least...
considering fdir started using `AbortController` recently, breaking compatibility with node 12 and 14, the engines field should probably be set to `>=16.0.0` (despite being added in 14.17.0, `AbortController` was only...
the `engines.node` field ended up getting set to >=12.0.0 in #159. i suppose this issue is solved now?
@jorenbroekema FYI #136 added the ability to provide your own fs object
the documentation.md file should be updated with the new options i think? looks like you missed that
had this issue too, it's because the node-gyp version used is the one that comes with pnpm. updating to pnpm v9 solved it for me
reopened due to #54