Fixed all path resolution logic in dependency-resolver.js to handle the new
directory structure where bmm is directly under src/ instead of src/modules/.
**Bugs Fixed:**
1. Line 341: Strip leading slash after removing {project-root} prefix
- `{project-root}/bmad/` became `/bmad/` which failed `startsWith('bmad/')` check
2. Lines 358, 378, 385: Use bmm/ directly instead of modules/bmm/ for explicit deps
- Updated both direct paths and glob patterns
3. Lines 537, 549, 565: Update resolveCommandToPath for @task/@agent/@bmad refs
- Task search now checks src/bmm/tasks/ not src/modules/bmm/tasks/
- Agent search now checks src/bmm/agents/ not src/modules/bmm/agents/
- Direct bmad/ paths now resolve to src/bmm/ not src/modules/bmm/
**Test Results:**
- Before: 350/352 passing (2 failing)
- After: 352/352 passing (100% ✅)
Tests fixed:
- "should resolve bmad/bmm/tasks/task.md (module path)"
- "should resolve bmad-path for module files"
|
||
|---|---|---|
| .. | ||
| 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.