shell-driver
plugins
| shell-driver | plugins | |
|---|---|---|
| 1 | 3 | |
| 4 | 161 | |
| - | 1.9% | |
| 4.1 | 5.4 | |
| about 2 years ago | 7 months ago | |
| TypeScript | TypeScript | |
| Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
shell-driver
-
Ask HN: What Are You Up To? (April 2022)
I needed a way to document my shell scripts (or code snippets) and to quickly replace “parameters”. For example, if you want to download a YT video as mp3, you have to remember this command “youtube-dl --extract-audio --audio-format mp3 ” . You can use the autocomplete & history in the terminal but you still have to remember parts of the command and replace the old URL with the new one. You can also save it in a text file, and replace … too many select/replace/copy/paste ops…
A few months ago I made a good enough solution for my problem https://github.com/alexadam/reactive-doc - it saves ~ 10 minutes/day when I have to run complex devops scripts. And I can quickly share the ‘docs’ because they are just plain html files / or markdown.
Now I just finished the next iteration - better ‘syntax’ for input widgets, runnable @shell commands and a web based terminal https://github.com/alexadam/shell-driver with custom filters and selection actions (useful for me)
Next steps: add more features to the web based terminal -> convert history to scripts, autocomplete with parameters, command palette & context aware menus, multiple terminals (with tabs or panels). I also want to add support for React components in the MD editor.
plugins
-
My terminal Rickrolled me
We are also hoping to open up more of the codebase over time. For example, the plugins that we are launching soon will be OSS. The manual pages we launched this week are also OSS. We currently can't do it for all of our codebase because It's just very hard to maintain a large fully OSS codebase. As a startup with a small dev team, we simply don't have resources to do that right now and our efforts are currently concentrated on more critical things like supporting Linux and Windows.
-
IDE-style autocomplete for your terminal
For example, the plugins we are launching soon will be OSS.
What are some alternatives?
vue-styleguidist - Created from react styleguidist for Vue Components with a living style guide
powerline-shell - A beautiful and useful prompt for your shell
sandpack - A component toolkit for creating live-running code editing experiences, using the power of CodeSandbox.
fzf-tab - Replace zsh's default completion selection menu with fzf!
reactive-doc - Create Interactive Documents with Plain Text
ohmyzsh - 🙃 A delightful community-driven (with 2,300+ contributors) framework for managing your zsh configuration. Includes 300+ optional plugins (rails, git, macOS, hub, docker, homebrew, node, php, python, etc), 140+ themes to spice up your morning, and an auto-update tool so that makes it easy to keep up with the latest updates from the community.
zoxide - A smarter cd command. Supports all major shells.
tshellout - Typescript Shell Out library, to simplify writing and composing shell commands for NodeJS
autocomplete - IDE-style autocomplete for your existing terminal & shell
replugged - A lightweight Discord client mod focused on simplicity and performance.
aacod - Write typescript code to automate your environment setup
awesome-shell - A curated list of awesome command-line frameworks, toolkits, guides and gizmos. Inspired by awesome-php.