rubys/listen — explained in plain English
Analysis updated 2026-07-16 · repo last pushed 2015-06-29
Automatically refresh your browser when you save a source file during development.
Re-run your test suite instantly every time a file changes, without manual commands.
Automatically compile stylesheets the moment you save a design file.
Trigger a data processing script as soon as a new CSV file lands in a watched folder.
| rubys/listen | 100rabhg/masterdetailapp | 100rabhg/pizzafactroy | |
|---|---|---|---|
| Language | Ruby | Ruby | Ruby |
| Last pushed | 2015-06-29 | 2024-02-20 | 2025-01-26 |
| Maintenance | Dormant | Dormant | Stale |
| Setup difficulty | easy | moderate | moderate |
| Complexity | 2/5 | 2/5 | 3/5 |
| Audience | developer | developer | pm founder |
Figures from each repo's GitHub metadata at analysis time.
Just add the gem to your Ruby project and write a short callback script to start watching directories.
Listen is a tool for Ruby that watches your folders for changes and tells your program whenever a file is added, modified, or deleted. This is what powers live-reloading tools, when you save a file, your browser automatically refreshes or your tests instantly re-run, saving you from manually switching windows and hitting refresh all day. At a high level, you point the tool at one or more directories and provide a short script, a "callback", that says what to do when a change happens. It then sits quietly in the background. When it notices a file change, it hands your script a list of exactly which files were modified, added, or removed. You can also fine-tune what it watches, telling it to ignore certain file types (like temporary logs) or to only track specific files (like your source code). Under the hood, it uses fast, built-in operating system features on Mac and Linux to get instant notifications with minimal performance impact. On other setups or certain network drives, it falls back to "polling", repeatedly checking the files for changes, which is slower but works everywhere. The project is currently looking for new maintainers to take over its ongoing development. A wide range of people use this, mostly behind the scenes. If you are building a developer tool, a static website generator, or an automated testing suite, you need a reliable way to trigger actions when files change. For example, a web developer might use it to automatically compile fresh stylesheets the moment they save a design file, or a data team might use it to trigger a data processing script the second a new CSV lands in a directory.
A Ruby tool that watches your folders and tells your program when files are added, changed, or deleted. It powers live-reloading features so browsers refresh and tests re-run automatically when you save.
Mainly Ruby. The stack also includes Ruby.
Dormant — no commits in 2+ years (last push 2015-06-29).
No license information was provided in the explanation, so it is unclear what permissions you have for using or modifying this software.
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.