Bump fdir from 6.0.1 to 6.5.0

[dependabot]

Bumps fdir from 6.0.1 to 6.5.0.

Release notes

Sourced from fdir's releases.

v6.5.0

This release brings a lot of cool stuff:

ESM support

fdir now includes esm builds in addition to the commonjs build.

Thanks to @​TheAlexLichter in thecodrr/fdir#147

Node v12 support (is back!)

fdir v6.4.6 broke Node v12 & v14 compatibility as it made use of AbortController. We have now replaced AbortController with an in-house solution that should bring back support for Node v12.

Additionally, fdir now has the engines field set to >=12 to make it super clear what versions of Node we support.

Thanks to @​SuperchupuDev & @​benmccann for bringing this up and helping me test this!

Custom FS

Huge thanks to @​43081j for adding support for this. You can now pass a custom FS module and fdir will make use of it instead of the Node.js fs module.

You can use it like so:

    const api = new fdir({
      fs: fakeFs,
    }).crawl("node_modules");

The fs property expects the following methods:

export type FSLike = {
  readdir: typeof nativeFs.readdir;
  readdirSync: typeof nativeFs.readdirSync;
  realpath: typeof nativeFs.realpath;
  realpathSync: typeof nativeFs.realpathSync;
  stat: typeof nativeFs.stat;
  statSync: typeof nativeFs.statSync;
};

Other changes

• perf: use slice instead of replace when joining path by @​SuperchupuDev in thecodrr/fdir#152
• fix: support @types/picomatch v4 by @​SuperchupuDev in thecodrr/fdir#156

New Contributors

• @​TheAlexLichter made their first contribution in thecodrr/fdir#147

... (truncated)

Commits

• 14c678e chore: bump version to 6.5.0
• bcfbc2e chore: update lockfile
• 7800ee8 chore: set engines field (#159)
• e7d6042 build: set up tsdown for dual build (#147)
• 175a702 fix: support @types/picomatch v4
• 2ac620d fix: use || instead of ?? for node 12 compat
• f1630d1 chore: run format
• 6547a2d feat: support custom fs
• afde92a test: minor refactor
• 76cb3a4 fix: drop AbortController as it breaks fdir on Node v14
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)