nodejs-cli-apps-best-practices
cli-guidelines
Our great sponsors
| nodejs-cli-apps-best-practices | cli-guidelines | |
|---|---|---|
| 11 | 47 | |
| 3,257 | 2,782 | |
| - | 2.8% | |
| 6.4 | 3.6 | |
| 4 months ago | about 1 month ago | |
| JavaScript | CSS | |
| Creative Commons Attribution Share Alike 4.0 | Creative Commons Attribution Share Alike 4.0 |
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.
nodejs-cli-apps-best-practices
-
Mastering Node.js CLI: Best Practices and Tips
This article is inspired by this awesome GitHub repository created by @lirantal, please go ahead and have a look it's worth.
- Node.js CLI Apps Best Practices
-
Is it possible to use node outside web devlopment/ creating servers?
Indeed! I'm co-maintaining blessed-contrib and https://github.com/lirantal/nodejs-cli-apps-best-practices :-)
-
What are your preferred guides to write cool command line app?
Mine are: an article - https://blog.developer.atlassian.com/10-design-principles-for-delightful-clis/ node cli apps best practices - https://github.com/lirantal/nodejs-cli-apps-best-practices
-
Writing a CLI for others, check this out
I also maintain the Node.js CLI Apps Best Practices repository here: https://github.com/lirantal/nodejs-cli-apps-best-practices with over 2k stars 🌟
- The largest Node.js CLI Apps best practices list
- The largest Node.js CLI Apps best practices list ✨
- Show HN: I curated empathic and dev-friendly Node.js CLI apps Best Practices
- A collection of curated best practices on how to build successful, empathic, and user-friendly Node.js Command Line Interface (CLI) applications.
cli-guidelines
- Ask HN: Where to read about terminal UIs?
-
Ask HN: Do you read Secrets from Environment Variables
The Command Line Interface Guidelines [1] says:
> Do not read secrets from environment variables
> Secrets should only be accepted via credential files, pipes, `AF_UNIX` sockets, secret management services, or another IPC mechanism
Which one of these do you use? On github it seems common for projects to use environment variables for secrets.
[1] https://clig.dev/#environment-variables
-
Command Line Interface Guidelines
Seems they took a small step back from their previous "don't bother with man pages" stance. Now it's "Consider providing man pages."
I still find it a rather shocking order of priority, honestly.
https://clig.dev/#documentation
-
Ask HN: Best way to do scoped commands in a CLI app
- E. `blah project foo --edit`
Wondering if there was any guidance on this from the UNIX people. Perhaps scoping should be done using the file system. `cd path/to/project && blah edit`. Like git does with `git --cwd=path/to/project`. Maybe a virtual FS could even be used. Then you wouldn't have to continuously type in the scope with each command. Interesting thinking about how to maintain state in the terminal...thinking about how Python's virtual env bin/activate modifies the shell.
Found an interesting guide here: https://clig.dev/
-
CLI user experience case study
Capturing these guidelines is one of the primary reasons that https://clig.dev/ exists.
-
Introducing my Password Manager project - Seeking Feedback and Contributions
You may want to take a look at various existing CLIs to get inspiration on how they operate, the user feedback loop and the ergonomics on using them. Here is a great website on some CLI structing guidance https://clig.dev/
What are some alternatives?
cobra - A Commander for modern Go CLI interactions
redox - Mirror of https://gitlab.redox-os.org/redox-os/redox