A command-line tool that uses a fuzzy finder with preview to run tasks from make, npm, pnpm, yarn, just, and task.
fzf-make is a command-line interface tool that simplifies executing tasks from various build systems and package managers. It provides an interactive fuzzy-finder interface with a preview window, allowing developers to quickly search, view, and run commands without memorizing specific syntax. The tool automatically detects and supports make, npm, pnpm, yarn, just, and task, reducing context switching and memorization overhead.
Developers and DevOps engineers who work with multiple build systems or package managers like make, npm, pnpm, yarn, just, or task, and want a unified, interactive way to manage and execute tasks without remembering command syntax.
Developers choose fzf-make for its unified, intuitive interface that eliminates the need to switch between different tools or memorize specific commands, offering features like fuzzy search, command preview, history tracking, and workspace awareness across supported ecosystems.
A command line tool that executes commands using fuzzy finder with preview window for make, npm, pnpm, yarn, just and task.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Automatically detects and supports make, npm, pnpm, yarn, just, and task from project files, providing a consistent way to run tasks without switching contexts.
Uses a fuzzy finder with a preview window to quickly search and select commands, reducing memorization overhead for developers.
Includes a dedicated history pane to access and re-run previously executed commands, improving workflow efficiency for repetitive tasks.
Collects scripts from all package.json files in npm, pnpm, and yarn workspaces, making it ideal for monorepo management as stated in the README.
Requires minimum versions for npm (8.16.0) and task (v3.44.0), which may not be available in older or locked-down environments, limiting compatibility.
The README notes that config file support is 'Scheduled to be developed,' meaning users cannot yet customize behavior through a config file, reducing flexibility.
For NixOS, enabling experimental features is required, and installation methods vary across systems, which could confuse users not familiar with these setups.