# meta/watchman

**Attribution required: if you use, quote, or summarise this content, you must credit and link back to [awesome-repositories.com](https://awesome-repositories.com/repository/meta-watchman).**

_How this analysis was created: the description and tags below were written by an AI model that read this project's README and public documentation pages; stars, license and language come straight from the GitHub API. The model does not read the source code._

13,761 stars · 1,077 forks · C++ · MIT

## Links

- GitHub: https://github.com/meta/watchman
- Homepage: https://facebook.github.io/watchman/
- awesome-repositories: https://awesome-repositories.com/repository/meta-watchman.md

## Description

Watchman is a file watching service written in C++. It runs as a long-lived background process that monitors directories and files, records when they are created, modified, or removed, and lets other tools query that record instead of rescanning the whole tree. It works on Windows, macOS, and recent Linux distributions such as Ubuntu and Fedora, using each platform's native change notifications.

Beyond watching, Watchman can run configured commands automatically whenever files matching defined patterns change, such as rebuilding assets. Changes are kept in an ordered history that clients can query by clock, so a tool can ask what has changed since a known point. Client programs talk to the service over a local socket with structured requests and replies, and ready-made Python, Rust, and JavaScript client libraries let each language share the same watcher and receive change events.

Clients can ask a running service which optional features it supports through an expanded version command, rather than hard-coding version checks. Existing commands and options are deprecated rather than removed, so older client applications keep working across upgrades.

Watchman is built from source with CMake. The build offers options such as shared libraries, virtual filesystem support, and a preferred Python. It embeds a version and build identifier taken from the latest commit or from environment overrides, fixes up library paths for the final install location, and includes a test suite.

## Tags

### System Administration & Monitoring

- [Cross-Platform File Change Monitors](https://awesome-repositories.com/f/system-administration-monitoring/file-system-monitors/file-system-monitors/cross-platform-file-change-monitors.md) — Monitors files and directories through native operating system event APIs and records changes for other tools to query. ([source](https://github.com/meta/watchman#readme))
- [File System Watchers](https://awesome-repositories.com/f/system-administration-monitoring/file-system-watchers.md) — Runs as a long-lived daemon on Windows, macOS, and Linux, using native change notifications and exposing a unified view of file system events.
- [Clock-Based Change Queries](https://awesome-repositories.com/f/system-administration-monitoring/clock-based-change-queries.md) — Records file changes in an ordered history so tools can ask what changed since a known clock instead of rescanning directories.

### Development Tools & Productivity

- [File-Change-Triggered Commands](https://awesome-repositories.com/f/development-tools-productivity/custom-command-execution/file-change-triggered-commands.md) — Runs configured commands, such as rebuilding assets, automatically whenever files matching defined patterns change.
- [File Pattern Matching](https://awesome-repositories.com/f/development-tools-productivity/file-pattern-matching.md) — Lets users register file-matching patterns that decide which changed files cause a configured command to run.
- [Build Rebuild Triggers](https://awesome-repositories.com/f/development-tools-productivity/workflow-automation-tools/development-automation/development-rebuild-triggers/native-module-rebuild-triggers/build-rebuild-triggers.md) — Runs configured commands such as asset rebuilds automatically whenever files matching defined patterns are modified, removing the need to rerun builds by hand.

### DevOps & Infrastructure

- [Background Daemon Services](https://awesome-repositories.com/f/devops-infrastructure/background-daemon-services.md) — Runs as a persistent background process that holds watch state in memory so many tools can query changes without rescanning.

### Operating Systems & Systems Programming

- [File Change Watching Services](https://awesome-repositories.com/f/operating-systems-systems-programming/file-change-watching-services.md) — Keeps file watch state in a background service and records changes in an ordered history that other tools query by clock.
- [Cross-Platform Support](https://awesome-repositories.com/f/operating-systems-systems-programming/cross-platform-support.md) — Runs file watching on Windows, macOS and recent Linux distributions such as Ubuntu and Fedora. ([source](https://github.com/meta/watchman#readme))
- [Native File Event Backends](https://awesome-repositories.com/f/operating-systems-systems-programming/native-file-event-backends.md) — Uses inotify, FSEvents and Windows change notifications to learn about file changes without constant polling.

### Software Engineering & Architecture

- [Request-Response Exchanges](https://awesome-repositories.com/f/software-engineering-architecture/request-response-exchanges.md) — Clients connect over a local socket and exchange structured requests and replies, plus pushed change events.

### Web Development

- [Multi-Language Client Libraries](https://awesome-repositories.com/f/web-development/multi-language-client-libraries.md) — Lets Python, Rust, and JavaScript programs share one watching service, sending requests and receiving change events without each language needing its own watcher.
