Comprehensive fix for installer failures related to Astro/Starlight peer dependencies: 1. Update @astrojs/starlight from 0.37.0 to 0.37.5 (latest stable) 2. Add .npmrc with legacy-peer-deps to prevent peer dependency warnings 3. Update module installer to use --legacy-peer-deps flag for external modules This resolves issues where: - npm shows peer dependency warnings that users interpret as failures - External module installations fail due to strict peer dependency checking - Different npm versions handle peer dependencies inconsistently Technical note: Starlight 0.37.x requires astro@^5.5.0, which is compatible with astro@5.16.0 (^5.5.0 means >=5.5.0 <6.0.0). The issue was npm's warning display, not actual incompatibility. Fixes: Installation errors reported in v6.0.0-Beta.2 Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| 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.