BMAD-METHOD/tools/cli/installers/lib/core
Paul Preibisch d9b10490b4 fix: Clear all npm config env vars before calling AgentVibes installer
When BMAD is invoked with --prefix flag, npm sets many npm_config_*
and npm_package_* environment variables. These caused npx agentvibes
to look for files in the wrong directory (/prefix/lib instead of cwd).

Changes:
- tools/cli/commands/install.js: Filter out ALL npm_config_* and
  npm_package_* env vars before calling npx agentvibes
- tools/cli/installers/lib/core/installer.js: Add AgentVibes prompt
  to Quick Update flow so existing installations can enable TTS
- tools/cli/installers/lib/core/manifest-generator.js: Track
  agentVibes configuration in manifest.yaml

This ensures AgentVibes runs in a clean environment regardless of
how BMAD was invoked (with or without --prefix flag).

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-12-06 12:02:50 -07:00
..
config-collector.js feat: default installer username to system user (#939) 2025-11-19 20:36:54 -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: Clear all npm config env vars before calling AgentVibes installer 2025-12-06 12:02:50 -07:00
manifest-generator.js fix: Clear all npm config env vars before calling AgentVibes installer 2025-12-06 12:02:50 -07:00
manifest.js fix: ensure POSIX-compliant newlines in generated files (#856) 2025-11-04 20:18:12 -06:00