Add stdin support to CLI apps that accept file input by piping to a temp file and passing it as the first argument.
tmpin is a command-line utility that adds stdin support to CLI applications that only accept file input. It solves the problem of being unable to pipe data directly to tools that require a file path by creating temporary files automatically. This enables seamless workflow integration between Unix pipes and file-based command-line tools.
Developers and system administrators who work with CLI tools and want to integrate stdin piping into their workflows, particularly those using multiple platforms where shell-specific features like process substitution aren't available.
tmpin provides a cross-platform alternative to shell-specific process substitution, working consistently across different operating systems while avoiding the limitations of native shell implementations. It's minimal, focused, and integrates easily into existing shell environments.
Add stdin support to any CLI app that accepts file input
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Works on any system, unlike shell-specific process substitution, as highlighted in the README's key features for bridging gaps across platforms.
Easy to alias in shell configs like .zshrc or .bashrc, enabling quick workflows as shown in the README's tip section for streamlined usage.
Compatible with any CLI app that accepts a file as the first argument, making it versatile for various tools, from text editors to processors.
Follows Unix philosophy with a simple command structure, reducing complexity compared to manual temp file handling, as emphasized in the philosophy section.
Creates temporary files for each operation, introducing disk I/O latency that can slow down frequent or data-intensive pipelines, unlike direct stdin processing.
Only works if the target app uses the file path as the first argument, limiting compatibility with tools that have different parameter orders or optional file inputs.
Requires Node.js and npm for installation, adding an extra layer for users not in the JavaScript ecosystem or in minimal environments without Node.
README doesn't specify automatic temp file cleanup, risking disk clutter if not managed, which could be problematic for long-running or sensitive workflows.