BMAD-METHOD/tools/cli/installers/lib/core
Diego Szychowski bb2f311a5e fix: retrieve installed modules during manifest processing for compiling agents
The problem was that the installedModules variable was being used at line 1987 but was never defined in the compileAgents method's scope.

Issue: When compiling agents the compilation failed.
Installation failed: installedModules is not defined
ReferenceError: installedModules is not defined at Installer.compileAgents (BMAD-METHOD/tools/cli/installers/lib/core/installer.js:1987:30) at async Command.action (BMAD-METHOD/tools/cli/commands/install.js:26:24)

The fix:

- Added the declaration let installedModules = []; at line 1968
- Added code to populate installedModules by reading the bmad directory and filtering for module directories (lines 1975-1979)
- This follows the same pattern used in other methods like  generateManifests (line 1237) and update (line 2050)
2025-12-07 19:54:19 -03:00
..
config-collector.js custom module installer improved, and removed agent-install 2025-12-07 02:10:03 -06:00
dependency-resolver.js installer fixes 2025-10-26 19:38:38 -05:00
detector.js customize installation folder for the bmad content 2025-11-08 15:19:19 -06:00
ide-config-manager.js fix quick udpate status bug in installer 2025-11-04 21:16:52 -06:00
installer.js fix: retrieve installed modules during manifest processing for compiling agents 2025-12-07 19:54:19 -03:00
manifest-generator.js fix: nested agents now appear in CLI commands 2025-12-06 16:39:28 -06:00
manifest.js fix: ensure POSIX-compliant newlines in generated files (#856) 2025-11-04 20:18:12 -06:00
post-install-sidecar-replacement.js remove hardcoded agent sidecar locations to fully use config option 2025-12-06 21:37:43 -06:00