UI5 / cli / 31781859307

94%

push

github

fix(project): Add polling file watcher for containers

On a bind-mounted volume inside a container, Linux inotify reports the
container's own writes but not writes made to the same volume from
outside the container. Podman is the common case. The incremental build
derives "what changed" solely from @parcel/watcher events, so those
missed events break rebuilds and live reload with no error to catch.

Add a fileWatcher.js module that all three watcher consumers call instead
of @parcel/watcher directly. It selects a backend once per process and
exposes a subscribe() matching @parcel/watcher's exact contract, so a
caller cannot tell which backend is active. The native backend stays
@parcel/watcher.

Both backends are imported lazily, only when selected. @parcel/watcher
resolves a native binding at load time and throws when the platform's
prebuilt binary is not installed (for example on an unsupported platform
or after an install with --omit=optional), so a static import would break
every consumer before the polling fallback could run. Loading it on demand
contains that failure: when the native backend is selected but cannot
load, subscribe() logs a warning and falls back to polling, which needs no
native code.

Parcel offers no polling subscription (its brute-force backend is
query-only), so the polling backend lives in a separate pollingWatcher.js
that fileWatcher.js imports lazily. It walks the tree and diffs an
mtimeMs+size snapshot every 250 ms (rescheduling itself after each walk so
a slow crawl cannot overlap the next), emitting the same {type, path}
events the native backend would. Errors flow through the callback so each
consumer's existing recovery path fires unchanged. The 250 ms interval
stays below WATCHER_BURST_SETTLE_MS (550 ms) so downstream event batching
still holds. Ignore globs reuse micromatch (already a direct dependency)
and prune ignored directories so node_modules is never crawled.

The backend is chosen once per process and memoiz... (continued)

7287 of 8033 branches covered (90.71%)

Branch coverage included in aggregate %.

106 of 119 new or added lines in 5 files covered. (89.08%)

13961 of 14562 relevant lines covered (95.87%)

5261.5 hits per line