the complete solution for node.js command-line programs
the complete solution for node.js command-line programs
Infer strong typings for commander options and action handlers
A module for making CLI applications with NestJS. Decorators for running commands and separating out config parsers included. This package works on top of commander.
Export commander command as a Fig spec
A testing utility for nest-commander. It builds on top of ideas from @nestjs/testing and is not tied to any test framework directly.
🛹 Modern TypeScript tools for SVG
A JS implementation of JSONPath with some additional operators
Commander.js with integrated interactive prompts
MCP server for terminal operations and file editing
A small collection of option validators for commander
rehype plugin to highlight code blocks in HTML with Prism (via refractor) with line highlighting and line numbers
Checkbox with autocomplete and other additions for Inquirer
A Component Library for Vue 3
Terminal Commander: local MCP-operated terminal/file signal channel with native Linux, Windows, and macOS packages.
The Unified Toolchain for the Web
Extends the Angular CLI's build process
the complete solution for node.js command-line programs
Extra assertions on top of node's assert module
A wrapper for Commander that automatically sets the version based on your package.json
Javascript FNV-1a Hashing Algorithm up to 1024 bits, with highly optimized 32bit and 52bit implementations.
Redis web-based management tool written in node.js
Supplementary rules introduced by ESLint Stylistic.
Universal Drag-and-Drop Component Supporting both Vue 3 and Vue 2
A metagem to tersify "gem 'pry-plus'; gem 'pry-rails'; gem 'better_errors'", and some additional commands
A minimal Motivosity API v1 wrapper for Ruby, plus a command-line tool
A calculator for the command line supporting postfix, prefix, infix, and lisp notation (plus a REPL)
This gem can generate a scaffold flex application based on PureMVC Multicore using the pipes utility abstracted by the fabrication framework. The initial application will be generated based on custom project name, title, src folder and package. Plus will include two modules: an authentication module and a dashboard module. It is intended that the gem in the future will be able to add new scaffold modules integrated with the application. New commands, proxies etc.
CreepCheck is a Ruby library that provides an API for checking romantic age compatibility based on the popular half-plus-seven formula for determining when it is socially (in)appropriate for people to date based on their relative ages. It comes with a sample command line interface utility. Opinions vary on appropriate age differences in romantic relationships, but the half-plus-seven formula seems to approximate United States cultural biases about appropriate age differences pretty well. This library and utility package was originally created as a joke related to assessing the ap propriateness of relationships between characters in fictional contexts, such as in fantasy/sci-fi prose and roleplaying games. It is not intended to be treated as a substitute for moral fiber or individual judgement, and no guarantees are made about the likelihood one's family or local courts of law will approve of a given relationship on the basis of the age of one's partner even if "approved" by the half-plus-seven formula. This tool's major release version is published on April Fool's Day under the terms of the DPL, or Detachable Public License. It is intended for entertainment purposes only. It is not even particularly well-written.
OptimistXL is feature filled but lightweight commandline option parser. It contains all of the features of the Optimist gem, plus lots of additional features you didnt know you needed. One line of code per option is all you typically need to write. For that, you get a nice automatically-generated help page, robust option parsing, command subcompletion, and sensible defaults for everything you don't specify. This gem is an enhanced-feature fork of the Optimist gem.
Context-aware secret scanning for Ruby projects. A thin wrapper around the native leakferret binary (written in Rust): it finds hardcoded secrets, confirms which ones are actually live by calling the provider, and rewrites them to read from environment variables instead. The platform binary is downloaded automatically on first use, so no Rust toolchain is required. The API exposes Leakferret.scan, Leakferret.verify, and Leakferret.rewrite (each returning Finding objects), plus a `leakferret` command-line tool.
pikuri-code adds the shell-and-dev-loop layer on top of pikuri-workspace's filesystem tools: a +Pikuri::Code::Bash+ that runs commands via the +Pikuri::Subprocess+ chokepoint with +Confirmer+ gating (optionally wrapped in a +Pikuri::Code::Bash::Sandbox::Bubblewrap+ filesystem sandbox), plus the demo +bin/pikuri-code+ binary that wires file + shell + web tools into an interactive coding agent rooted at the current working directory. The +Pikuri.prompt+ search path picks up this gem's +prompts/coding-system-prompt.txt+ automatically on require.
This is a fork of Zach Holman's amazing boom. Explanation for the fork follows Zach's intro to boom: God it's about every day where I think to myself, gadzooks, I keep typing *REPETITIVE_BORING_TASK* over and over. Wouldn't it be great if I had something like boom to store all these commonly-used text snippets for me? Then I realized that was a worthless idea since boom hadn't been created yet and I had no idea what that statement meant. At some point I found the code for boom in a dark alleyway and released it under my own name because I wanted to look smart. Explanation for my fork: Zach didn't fancy changing boom a great deal to handle the case of remote and local boom repos. Which is fair enough I believe in simplicity. But I also believe in getting tools to do what you want them to do. So with boom, you can change your storage with a 'boom storage' command, but that's a hassle when you want to share stuff. So kaboom does what boom does plus simplifies maintaining two boom repos. What this means is that you can pipe input between remote and local boom instances. My use case is to have a redis server in our office and be able to share snippets between each other, but to also be able to have personal repos. It's basically something like distributed key-value stores. I imagine some of the things that might be worth thinking about, based on DVC are: Imports/Exports of lists/keys/values between repos. Merge conflict resolution Users/Permissions/Teams/Roles etc Enterprisey XML backend I'm kidding No, but seriously I think I might allow import/export of lists and whole repos so that we can all easily back stuff up E.g. clone the whole shared repo backup your local repo to the central one underneath a namespace