fdir is a fast directory crawler and globbing utility for NodeJS, designed to scan very large directories quickly and return matching file paths. It provides a builder-pattern API for crawling directories and supports synchronous or promise-based results, using Node’s fs and path modules (with optional manual installation of picomatch for globbing).
Project status
- The
thecodrr/fdirGitHub source shows evidence of recent but not current activity. The last upstream push was 2025-08-16, and the most recent listed update is v6.5.0 on 2025-08-14, which is about 10 months ago as of 2026-06-09, so it appears quiet or in maintenance mode rather than actively maintained today. - Apparent update cadence was moderately steady across 2024 into mid-2025 (multiple patch/minor updates), but it has stalled since mid-August 2025 with no further updates listed in the provided history.
AI summary generated
Recent updates
v6.5.0
v6.5.0 adds ESM builds, restores Node 12 compatibility by replacing AbortController usage with an in-house abort mechanism, and introduces support for injecting a custom filesystem implementation. It also includes smaller internal optimizations and a fix for @types/picomatch v4.
Featuresv6.4.6
v6.4.6 contains a targeted fix to the directory walking logic so that crawling is not prematurely terminated when the internal currentDepth is 0. The main behavioral change is in both async and sync walkers, and the test suite expectations were adjusted to match the corrected depth handling.
Breakingv6.4.5
This release (v6.4.5) is documented as a fix to ensure the walker callback is called only once. The code diff shows additional internal behavior changes around queueing, abort handling, and crawl depth boundaries that are not mentioned in the release notes.
Breakingv6.4.4
v6.4.4 updates formatting tooling and fixes a crawl hang when resolving symlinks at the filesystem root. It also adjusts documentation formatting for withCallback.
v6.4.3
v6.4.3 is a small bug fix release. It corrects how the exclude predicate is evaluated when symlink resolution is involved, ensuring the predicate receives the expected path value.
v6.4.2
v6.4.2 is a small patch release that addresses a crawler deadlock/regression when `maxDepth` is set to a negative value. The code change ensures the internal crawl queue is properly finalized so `fdir` resolves instead of hanging.
v6.4.1
v6.4.1 fixes handling of recursive symlinks to prevent infinite recursion that could crash or take too long. The implementation introduces directory-visit tracking and a recursion guard that behaves differently depending on whether symlink path resolution is enabled.
v6.4.0
v6.4.0 adds the ability to exclude symlinks during crawling and introduces custom glob matching via a user-provided glob factory function. It also improves relative-path behavior for symlinks and prevents returning an empty string for the root when using relative paths. The release notes cover the main functionality, but there are a couple of code-level behavior and API surface changes that are not explicitly documented.
Featuresv6.3.0
Release 6.3.0 restores support for `withSymlinks` resolving real paths via a `resolvePaths` option, and fixes a symlink path formatting bug where resolved paths could include a leading slash. Code changes introduce a new internal `useRealPaths` flag to select between two symlink resolution implementations (real-path vs original-path).
BreakingFeaturesv6.2.0
Release 6.2.0 focuses on improving directory handling when returning relative paths, specifically addressing incorrect behavior when `onlyDirs` is enabled. It also updates `picomatch` dependency expectations to support newer versions.