@rljson/fs-agent 0.0.61 → 0.0.62

package/dist/fs-agent.js

@@ -684,6 +684,32 @@ class FsScanner {
     } catch {
     }
   }
+  /**
+   * Whether a watcher event's path should be ignored.
+   *
+   * `fs.watch` in recursive mode reports a path RELATIVE TO THE ROOT
+   * (`sub/dir/.fsagent-tmp-abc`), while the ignore patterns are basenames.
+   * {@link _shouldIgnore} tests `startsWith`, so a nested match never fired:
+   * every atomic write the agent itself makes during a restore came back as a
+   * change event, each event triggered a scan, and the debounce that batches a
+   * push was reset before it could fire.
+   *
+   * Measured on the customer's folder: after a 3 642-file restore the watcher
+   * reported the SAME newly added file nine times and the agent never emitted a
+   * ref for it — `[fs] added: …/probe-….txt` nine times, no `sync:out`. The
+   * file did not fail to arrive; it was never sent.
+   *
+   * Every segment is tested, because the pattern may match a directory as
+   * easily as a file.
+   * @param relativePath - Path as the watcher reports it.
+   * @returns True when any segment matches an ignore pattern.
+   */
+  _shouldIgnorePath(relativePath) {
+    for (const segment of relativePath.split(/[\\/]/)) {
+      if (segment && this._shouldIgnore(segment)) return true;
+    }
+    return false;
+  }
   _shouldIgnore(name) {
     if (!this._options.ignore) {
       return false;
@@ -704,7 +730,7 @@ class FsScanner {
     }
     const onEvent = async (eventType, filename) => {
       if (!filename) return;
-      if (this._shouldIgnore(filename)) {
+      if (this._shouldIgnorePath(filename)) {
         return;
       }
       await this._handleFileChange(eventType, filename);

package/dist/fs-scanner.d.ts

@@ -141,6 +141,27 @@ export declare class FsScanner {
      * (temp + rename). Best-effort: a failed cache write never fails the scan.
      */
     private _persistCache;
+    /**
+     * Whether a watcher event's path should be ignored.
+     *
+     * `fs.watch` in recursive mode reports a path RELATIVE TO THE ROOT
+     * (`sub/dir/.fsagent-tmp-abc`), while the ignore patterns are basenames.
+     * {@link _shouldIgnore} tests `startsWith`, so a nested match never fired:
+     * every atomic write the agent itself makes during a restore came back as a
+     * change event, each event triggered a scan, and the debounce that batches a
+     * push was reset before it could fire.
+     *
+     * Measured on the customer's folder: after a 3 642-file restore the watcher
+     * reported the SAME newly added file nine times and the agent never emitted a
+     * ref for it — `[fs] added: …/probe-….txt` nine times, no `sync:out`. The
+     * file did not fail to arrive; it was never sent.
+     *
+     * Every segment is tested, because the pattern may match a directory as
+     * easily as a file.
+     * @param relativePath - Path as the watcher reports it.
+     * @returns True when any segment matches an ignore pattern.
+     */
+    private _shouldIgnorePath;
     private _shouldIgnore;
     watch(): Promise<void>;
     /**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rljson/fs-agent",
-  "version": "0.0.61",
+  "version": "0.0.62",
   "description": "Rljson fs-agent description",
   "homepage": "https://github.com/rljson/fs-agent",
   "bugs": "https://github.com/rljson/fs-agent/issues",