fix(@angular/build): ensure chokidar watcher is ready before returning

When initializing chokidar.watch with ignoreInitial: true, files visited during the initial scan are treated as the initial baseline and do not emit change events. If createChokidarWatcher returns before the initial scan completes, subsequent file modifications made shortly after setup can be visited for the first time during the initial scan, causing the change event to be dropped.

Author: alan-agius4

packages/angular/build/src/builders/dev-server/tests/behavior/build-errors_spec.ts

@@ -38,8 +38,8 @@ describeServeBuilder(executeDevServer, DEV_SERVER_BUILDER_INFO, (harness, setupT
             expectNoLog(logs, 'Unexpected character "EOF"');
           },
         ],
-        { outputLogsOnFailure: false, timeout: 90_000 },
+        { outputLogsOnFailure: false },
       );
-    }, 120_000);
+    });
   });
 });

packages/angular/build/src/tools/esbuild/watcher.ts

@@ -8,6 +8,7 @@
 
 import type * as ParcelWatcher from '@parcel/watcher';
 import type * as Chokidar from 'chokidar';
+import { once } from 'node:events';
 import * as fs from 'node:fs';
 import * as path from 'node:path';
 import picomatch from 'picomatch';
@@ -663,8 +664,15 @@ async function createChokidarWatcher(
     usePolling: !!options?.polling,
     interval: options?.interval,
   });
+
   const initTime = Date.now();
 
+  // Wait for the watcher to complete its initial filesystem scan before returning.
+  // With `ignoreInitial: true`, any file visited during the initial scan is treated as the initial baseline
+  // and will not emit 'add' or 'change' events. Awaiting 'ready' ensures that rapid file modifications
+  // made right after watcher setup (e.g. in rebuild tests) are not swallowed as initial files.
+  await once(watcher, 'ready');
+
   const handleEvent = (type: 'added' | 'modified' | 'removed', rawPath: string) => {
     const posixPath = toPosixPathNormalized(rawPath);
     const lookupKey = toLookupKey(posixPath, isCaseSensitive);