The non-interactive --custom-content CLI flag builds a customContentConfig object missing the `sources`, `selected`, and `selectedFiles` properties that the installer expects. This causes findModuleSource() to fail with "Source for module X is not available" because customModulePaths is never populated. Align both CLI code paths (modify and fresh install flows) with the config shape produced by the interactive promptCustomContentSource() method. Fixes #1623 |
||
|---|---|---|
| .. | ||
| commands | ||
| installers | ||
| lib | ||
| README.md | ||
| bmad-cli.js | ||
| external-official-modules.yaml | ||
README.md
BMad CLI Tool
Installing external repo BMad official modules
For external official modules to be discoverable during install, ensure an entry for the external repo is added to external-official-modules.yaml.
For community modules - this will be handled in a different way. This file is only for registration of modules under the bmad-code-org.