If you develop in Dart or Flutter and use tools like json_serializable, freezed, or riverpod_generator, you’re likely familiar with the ritual of opening a terminal and running dart run build_runner watch every time you start your IDE. It’s a small friction point, but one that adds up over time, especially when jumping between multiple projects.
Automating the Ritual
I created build_runner_hook to solve this exact problem. It is a Dart analyzer plugin that acts as a silent guardian for your code generation. When your IDE opens a Dart or Flutter project, the analyzer spins up. The plugin immediately analyzes your source files, and if it detects any part directives, it seamlessly spawns and manages the build_runner process in the background.
Process Management and Lifecycles
Managing background child processes from within an analyzer plugin comes with unique challenges, primarily avoiding zombie processes. The plugin is designed with a graceful lifecycle management system. When the analyzer shuts down (e.g., when you close VS Code), it intercepts the shutdown signal and terminates the build process cleanly.
By removing the need to manage terminal windows for code generation, build_runner_hook creates a truly zero-friction environment where generated files stay in sync automatically as you code, with all terminal output safely logged to a file for debugging.