and-cli
command-line tool to manage the development of software applications.
From the root of the cloned or forked repository, run this command:
npm install && npm run build && ./dist/and-cli.js install
What this does:
and-cli
for the installed version of the npm package in your project, which defaults to globally installed package if not installed for projectand-cli-dev
for running the cli while developing for it, via the directory in which you cloned or forked the repositoryTo install and-cli
only for the current project, run this in its root directory:
# npm
npm install --save-dev and-cli
# yarn
yarn add and-cli --dev
To install the CLI globally, do:
# npm
npm install and-cli -g
# yarn
yarn global add and-cli
The documentation for and-cli
commands can be found in COMMANDS.md.
.
├── src/
| ├── modules/ # Modules are shared functions holding business logic to be imported & called by commands
| │ ...
| │ ├── command-registry.ts # Module holding abstractions around command registration (internal & external)
| │ ├── command-registry.test.ts # Unit test file for the command-registry module
| │ ├── commands.ts # Module exporting names & descriptions of each command to be registered for the CLI
| | ...
| │ └── zip.ts
| ├── tests/ # Setup, utilities and shared specs for the test suite
| | ...
| │ └── test-utils.ts
| ├── types/ # Custom types found in the project.
| │ └── command-definition-type.ts
| ├── utilities/ # Utility functions that aren't really categorized as a standard 'module'
| | ...
| | ├── option-string-builder.ts # Builder for constructing option strings to be passed to `program.option`, ie `-i, --info`
| | └── option-string-builder.test.ts # Unit tests file for the option-string-builder utility
| ├── and-cli.ts # Main entrypoint/parent command that registers subcommands
| ├── and-cli-copy.ts # Implementation of the 'copy' command
| ├── and-cli-copy.test.ts # Integration test file for the 'copy' command
| | ...
| ├── and-cli.test.ts # Integration test file for the main entrypoint/parent command
| └── index.ts # Index file that exports all modules, types, utilities, etc. for consumer usage
├── COMMANDS.md # Markdown file containing extra documentation for each command
├── package.json
└── package-lock.json
For testing, we use Jest
. We integration test top-level commands (such as and-cli-dotnet
) and unit test shared modules/utilities (such as modules/dotnet-build
or utilities/option-string-builder
).
While we do not have any coverage thresholds currently configured, we ask that new modules/utilities introduced to the codebase are unit tested for high-value paths. Integration tests should be considered, but written more sparingly due to the overhead of run-time.
The functionality of this CLI can be extended by adding it as a dependency in your node project and requiring the main module, ie require("and-cli")
. All commands should be registered through the command-registry
module, which provides multiple functions for adding, overriding, and removing commands.
A small example of a project that imports this package and pulls in all of the base commands:
#!/usr/bin/env node
// -----------------------------------------------------------------------------------------
// #region Imports
// -----------------------------------------------------------------------------------------
const { CommandRegistry, program } = require("and-cli");
// #endregion Imports
// -----------------------------------------------------------------------------------------
// #region Entrypoint
// -----------------------------------------------------------------------------------------
// Register all of the base commands from the and-cli with this application
CommandRegistry.registerAllBase();
program.parse(process.argv);
// #endregion Entrypoint
For more examples, or to see what the full project structure might look like, see this example repository:
AndcultureCode.Cli.PluginExample
Existing commands & options can be aliased so they are easier to type or remember. Aliases can be registered in your package.json
file, or registered in your extended CLI through the command-registry
module.
To add aliases without any additional code, add an and-cli
section with an aliases
object underneath. Each key of the aliases
section will be the alias you want to use (which cannot contain spaces), and the value will be the command and any options that should be run in place of it.
Note: when defining aliases, the command/option string to be mapped should not contain the CLI name itself. See example below.
{
"and-cli": {
"aliases": {
"d": "dotnet",
"dcRb": "dotnet -cRb",
}
}
}
If you are extending the and-cli
with your own commands, you will also need to call CommandRegistry.registerAliasesFromConfig()
to read the aliases from package.json
.
Note: Ensure you are calling CommandRegistry.parseWithAliases()
, or the preprocessing to handle the aliases will not run.
#!/usr/bin/env node
// -----------------------------------------------------------------------------------------
// #region Imports
// -----------------------------------------------------------------------------------------
const { CommandRegistry, program } = require("and-cli");
// #endregion Imports
// -----------------------------------------------------------------------------------------
// #region Entrypoint
// -----------------------------------------------------------------------------------------
// Register the base 'dotnet' command and register aliases from the package.json file
CommandRegistry
.registerBase("dotnet")
.registerAliasesFromConfig();
// Ensure you call parseWithAliases() in place of program.parse() to preprocess the arguments.
CommandRegistry.parseWithAliases();
// #endregion Entrypoint
Aliases can be registered just like commands would be with the CommandRegistry.registerAlias()
function.
Note: Ensure you are calling CommandRegistry.parseWithAliases()
, or the preprocessing to handle the aliases will not run.
#!/usr/bin/env node
// -----------------------------------------------------------------------------------------
// #region Imports
// -----------------------------------------------------------------------------------------
const { CommandRegistry, program } = require("and-cli");
// #endregion Imports
// -----------------------------------------------------------------------------------------
// #region Entrypoint
// -----------------------------------------------------------------------------------------
// Register the base 'dotnet' command and alias some of its options
CommandRegistry
.registerBase("dotnet")
.registerAlias({
command: "d",
description: "dotnet",
})
.registerAlias({
command: "dcRb",
description: "dotnet -cRb",
});
// Ensure you call parseWithAliases() in place of program.parse() to preprocess the arguments.
CommandRegistry.parseWithAliases();
// #endregion Entrypoint
Regardless of how they are registered, aliases will be specially noted in the help menu of the CLI.
Usage: and-cli [options] [command]
andculture cli
Options:
-V, --version output the version number
-h, --help display help for command
Commands:
copy Copy files and/or directories
d (alias) dotnet
dcRb (alias) dotnet -cRb
deploy Deploy various application types
dotnet Run various dotnet commands for the project
dotnet-test Run various dotnet test runner commands for the project
github Commands for interacting with AndcultureCode github resources
install Collection of commands related to installation and configuration of the and-cli
migration Run commands to manage Entity Framework migrations
nuget Manages publishing of nuget dotnet core projects
webpack Run various webpack commands for the project
webpack-test Run various webpack test commands for the project
help [command] display help for command
Due to POSIX auto path conversion if you have an argument that needs to start with a leading slash "/". Escape it with an additional slash "//".
Upon application startup the CLI will replace it with the single slash "/".
Depending upon the shell/terminal you are using, the node process sometimes requires the --
delimiter between the command and the arguments. Otherwise, especially in a shell like windows command prompt, the value for arguments gets piped out of order.
Example:
and-cli dotnet --cli "test db migrate"
and-cli dotnet -- --cli test db migrate
If you are using the project alias, check to make sure the version in your package.json
is up to date. You can ensure the latest is installed by running:
npm install --save-dev and-cli@latest
If you don't have the package installed in your project and you're using a global package, you can check the current version with:
npm list -g --depth=0 | grep and-cli
The latest version can be installed by running:
npm install --global and-cli@latest
Thanks goes to these wonderful people (emoji key):
Brandon Scott 💻 📖 🚇 🚧 ⚠️ |
Dylan Justice 💻 🚧 ⚠️ 👀 |
Winton DeShong 💻 📖 🚧 ⚠️ 👀 |
Kevin Busch 💻 ⚠️ 👀 |
Cody Spath 👀 |
Stefanie Leitch 💻 📖 ⚠️ |
Aaron 👀 |
Michael Tyson 👀 |
Joshua Hughes 👀 |
Jim Stevenson 👀 |
This project follows the all-contributors specification. Contributions of any kind welcome!