dev module list
List all project modules with their configuration
- Command version
0.0.0- Command configuration
dev-tool:dev.module.list@0.0.0
Arguments
| Argument | Type | Required | Default | Description |
|---|---|---|---|---|
--repo-adapter | string | No | Optional target repoAdapter filter | |
--kind | string one of library, test-library, executable | No | Optional target kind filter | |
--self-declaring, --no-self-declaring | boolean | No | false | List instead the repositories in this tree that declare and publish their own packages, one checkout path per line |
It also takes the global arguments.
Output
It answers with a list.moduleList.
Types
list.moduleList
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
app | string | Yes | The project the manifest names | |
targetCount | integer | Yes | How many modules targets holds | |
targets | list[any] | Yes | Each module of the manifest that passed the --repo-adapter and --kind filters, as the manifest declares it and in its order. Empty under --self-declaring | |
commands | list[string] | Yes | Every command the application can be invoked with, each as the words that invoke it joined by spaces, sorted | |
repositories | list[string] | No | [] | Filled under --self-declaring alone, where targets is left empty: the checkout of each repository in the tree that declares and publishes its own packages, as a path from the root, sorted. Nothing in the tree's manifest names these, so each is published from its own checkout. |
selfDeclaring | boolean | No | false | Whether this is the --self-declaring listing, which is what says an empty repositories found none rather than was not asked. |