watchexec

name	watchexec
description	Software development often involves running the same commands over and over. Boring! WHEN: build command-line interfaces. Triggers: use watchexec, install watchexec, how to use watchexec.

watchexec

Software development often involves running the same commands over and over. Boring!

When to Use

• Build command-line interfaces

When NOT to Use

• Projects using Python or TypeScript (different ecosystem)

Quick Start

Install

• With your package manager for Arch, Debian, Homebrew, Nix, Scoop, Chocolatey…
• From binary with Binstall: cargo binstall watchexec-cli
• As pre-built binary package from Github
• From source with Cargo: cargo install --locked watchexec-cli

All options in detail: in the CLI README, in the online help (watchexec -h, watchexec --help, or watchexec --manual), and in the manual page.

Basic Usage

Watch all JavaScript, CSS and HTML files in the current directory and all subdirectories for changes, running npm run build when a change is detected:

$ watchexec -e js,css,html npm run build

Call/restart python server.py when any Python file in the current directory (and all subdirectories) changes:

$ watchexec -r -e py -- python server.py

More usage examples: in the CLI README!

Key Features

• Simple invocation and use, does not require a cryptic command line involving xargs
• Runs on OS X, Linux, and Windows
• Monitors current directory and all subdirectories for changes
• Coalesces multiple filesystem events into one, for editors that use swap/backup files during saving
• Loads .gitignore and .ignore files

Project Info

• Language: Rust, JavaScript
• Tests: Yes

File Structure

├── bin/
│   ├── completions
│   ├── dates.mjs
│   ├── manpage
│   └── release-notes
├── completions/
│   ├── bash
│   ├── elvish
│   ├── fish
│   ├── nu
│   ├── powershell
│   └── zsh
├── crates/
│   ├── bosion/
│   ├── cli/
│   ├── events/
│   ├── filterer/
│   ├── ignore-files/
│   ├── lib/
│   ├── project-origins/

Generated by repo2skill