docs/build/cli/dev/impact/index.md
Snider 85bbb8e828 docs: initial import of CorePHP documentation
173 markdown files covering:
- Framework architecture (lifecycle events, module system, multi-tenancy)
- Package docs (admin, api, mcp, tenant, commerce, content, developer)
- CLI reference (dev, build, go, php, deploy commands)
- Patterns (actions, repositories, seeders, services, HLCRF)
- Deployment (Docker, PHP, LinuxKit, templates)
- Publishing (Homebrew, AUR, npm, Docker, Scoop, Chocolatey)

Source: core-php/docs (core.help content)

Co-Authored-By: Virgil <virgil@lethean.io>
2026-03-03 17:51:03 +00:00

1.2 KiB

core dev impact

Show impact of changing a repository.

Analyses the dependency graph to show which repos would be affected by changes to the specified repo.

Usage

core dev impact <repo-name> [flags]

Flags

Flag Description
--registry Path to repos.yaml (auto-detected if not specified)

Examples

# Show what depends on core-php
core dev impact core-php

# Show what depends on core-tenant
core dev impact core-tenant

Output

Impact of changes to core-php:

Direct dependents (5):
  core-tenant
  core-admin
  core-api
  core-mcp
  core-commerce

Indirect dependents (12):
  core-bio (via core-tenant)
  core-social (via core-tenant)
  core-analytics (via core-tenant)
  core-notify (via core-tenant)
  core-trust (via core-tenant)
  core-support (via core-tenant)
  core-content (via core-tenant)
  core-developer (via core-tenant)
  core-agentic (via core-mcp)
  ...

Total: 17 repos affected

Use Cases

  • Before making breaking changes, see what needs updating
  • Plan release order based on dependency graph
  • Understand the ripple effect of changes

See Also