Run details

NxWorkspace

CI Pipeline Executions
- Current executionCanceled
  sj/daemon-outdated-check-events
- Runs and Agents
- TimelineBeta
- Configuration
- Self-Healing CI
- Project Graph
- Circular DependenciesEnterprise
- Resource Usage
- Analysis
- ConformanceEnterprise
Runs

Insights

Compare tasks
Analytics

Sign in

fix(core): check the lockfiles on watch events instead of every 20 ms The daemon's outdated check ran on a 20 ms interval. Every tick read the process file, resolved the installed nx version and hashed every lockfile at the workspace root. With a 1.7 MB yarn.lock an idle daemon read the file 34 to 50 times a second: 8 to 12% of a core and 57 MB/s on a Windows laptop, 5 to 6% of a core on an M4 Mac, for a daemon doing nothing. The watch already names every changed path. The lockfile hash is now recorded once, before the watch starts, and compared only when a batch names a lockfile at the root; a change the kernel dropped arrives as an ordinary batch after the re-walk. The process-file check already ran on the watch event for that file, and now also runs when the watch reports dropped events, since that event may have been among them. A client connection runs all three checks once before the daemon serves it, so a change the watch never reported is still caught at the next request. The interval is gone.

nx run-many -t check-imports check-lock-files check-codeowners --parallel=1 --no-dte

Succeeded

4 CPU cores

read access token used

d8157d7737113

Get faster results

Learn how to enable distribution.

Atomizer enabled

1 group of tasks optimized.

Machine

4 cores · 15.61 GB

CPU (avg / max)

96.22% / 191.81%

Memory (avg / max)

1,004.57 MB / 1.3 GB

© 2026 - Nx Cloud

Terms of Service Privacy Policy Changelog Status Docs Contact Nx Cloud Pricing Company @NxDevTools

NxWorkspace