#watch #events #notify

hotwatch

A Rust library for conveniently watching and handling file changes

13 releases

0.5.0 Jun 1, 2023
0.4.6 Oct 12, 2021
0.4.5 Nov 25, 2020
0.4.3 Dec 3, 2019
0.1.0 Nov 12, 2016

#817 in Filesystem

Download history 936/week @ 2024-07-20 775/week @ 2024-07-27 1012/week @ 2024-08-03 1101/week @ 2024-08-10 1132/week @ 2024-08-17 903/week @ 2024-08-24 731/week @ 2024-08-31 1051/week @ 2024-09-07 897/week @ 2024-09-14 898/week @ 2024-09-21 733/week @ 2024-09-28 570/week @ 2024-10-05 583/week @ 2024-10-12 730/week @ 2024-10-19 539/week @ 2024-10-26 622/week @ 2024-11-02

2,552 downloads per month
Used in 28 crates (27 directly)

MIT/Apache

18KB
255 lines

hotwatch

Crates.io Docs.rs CI Status

hotwatch is a Rust library for comfortably watching and handling file changes. It's a thin convenience wrapper over notify, allowing you to easily set callbacks for each path you want to watch.

Only the latest stable version of Rust is supported.

use hotwatch::{Hotwatch, Event, EventKind};

let mut hotwatch = Hotwatch::new().expect("hotwatch failed to initialize!");
hotwatch.watch("war.png", |event: Event| {
    if let EventKind::Modify(_) = event.kind {
        println!("War has changed.");
    }
}).expect("failed to watch file!");

Why should I use this instead of warmy?

warmy is a more general solution for responding to resource changes. hotwatch is very simplistic and intends to be trivial to integrate.

I've never actually used warmy, though. It's probably awesome. I just know that hotwatch is really easy to use and has a sexy name.

Dependencies

~1–11MB
~68K SLoC