google/wireit
Wireit
Wireit is a build system orchestrator and npm script task runner that manages complex dependencies between scripts. It functions as a development workflow automator by tracking input files and dependencies to skip redundant executions and optimize total build time.
The project features a content-addressable build cache that saves generated files to bypass expensive computations. It includes a file watcher that monitors project changes and automatically triggers only the affected scripts within a dependency graph.
The tool covers task orchestration through parallel script execution, background process management, and dependency mapping. It also provides build management utilities for artifact cleanup and resource-constrained execution to prevent system exhaustion.
The project provides IDE integration for configuration assistance, including autocompletion and script format conversion.
Features
- Development Trigger Automations - Automates development workflows by watching file changes and lock files to trigger only necessary scripts.
- Build Orchestrators - Functions as a build orchestrator that tracks input files and dependencies to optimize total build time.
- Cache Input and Output Specifications - Uses rules to determine result validity based on file and environment state, restoring output files from previous runs.
- NPM Script Runners - Provides a system for defining and executing scripts defined in package configuration files with strict dependency management.
- Parallel Task Execution - Executes independent scripts simultaneously based on system capacity and dependency graphs to reduce processing time.
- Script Dependency Managers - Establishes strict execution sequences to ensure all necessary prerequisites run before dependent tasks start.
- Task Dependency Management - Allows defining scripts as prerequisites for other tasks to establish a strict execution order.
- Content-Addressable Caches - Implements a content-addressable cache that uses input hashing to skip redundant build computations.
- Build Pipeline Optimization - Reduces build times by skipping unchanged tasks and running independent scripts in parallel using a dependency graph.
- File-Change-Triggered Restarts - Automatically triggers the execution of affected scripts in the task graph when monitored files are modified.
- Input-State Skipping - Skips running a script if its input files and configuration match the state of the last successful run.
- Hash-Based Change Detection - Uses cryptographic hashes of input files and environment variables to detect changes and determine if tasks need re-execution.
- Directed Acyclic Graph Pipelines - Orchestrates script execution by building a directed acyclic graph to manage dependencies and maximize parallelism.
- File System Monitors - Monitors the filesystem for changes to automatically trigger the re-execution of affected tasks in the dependency graph.
- Background Service Management - Orchestrates persistent background processes that start and stop automatically with their dependent build tasks.
- Frontend Build Tools - Manages output artifacts and caching for web-based assets to avoid redundant computations during development.
- Dependency Cascade Controls - Prevents dependent tasks from triggering if a prerequisite script completes without producing new output files.
- Environment Variable Management - Manages environment variables to influence script fingerprints and control caching behavior.
- Resource-Aware Parallelization - Limits simultaneous process spawns based on available CPU cores to prevent system resource exhaustion.
- Dependency Lock Files - Monitors package manager lock files to trigger script re-runs when project dependencies are updated.
- Failure Handling Policies - Controls whether to terminate the entire process or continue execution when a script returns a non-zero exit code.
- Output-Based Execution Controls - Prevents dependent tasks from triggering if a prerequisite script completes without producing new output files.
- Background Process Orchestration - Manages persistent background scripts as services that remain active throughout the build process.
- Concurrency Limiters - Caps the number of simultaneous scripts based on available CPU cores to prevent system resource exhaustion.
