Composer Merge Plugin Laravel Package

Product Decisions This Supports

• Enables modern Laravel/PHP stack alignment by enforcing Composer 2.0 compatibility, ensuring seamless integration with contemporary PHP ecosystems and reducing friction in new project adoption.
• Strengthens modular architecture with granular dependency management, now optimized for Composer 2.0’s performance improvements, reducing build times and resource overhead in large-scale applications.
• Validates a "buy" decision with expanded support for PHP 7.2+ (dropping legacy HHVM), aligning with LTS PHP versions and reducing maintenance burden for teams migrating from older stacks.
• Supports enterprise roadmaps by future-proofing dependency resolution for monorepos, microservices, or modular SaaS platforms where Composer 2.0 adoption is a strategic priority.
• Reduces technical debt by eliminating HHVM support (deprecated in PHP 7+), simplifying CI/CD pipelines and reducing compatibility testing overhead.

When to Consider This Package

• Adopt for:

  • Projects using Composer 2.0+ (required for new features/performance) or PHP 7.2+ (LTS support).
  • Monorepos/multi-module apps where dependency isolation is critical (e.g., Laravel-based CMS, SaaS platforms, or microservices).
  • Teams experiencing merge conflicts in composer.json or needing fine-grained dependency precedence across modules.
  • Organizations migrating from HHVM or PHP <7.2 to modern stacks (this release drops legacy support, forcing alignment).

• Avoid for:

  • Projects stuck on PHP <7.2 or using Composer 1.x (minimum now 1.1, but 2.0+ recommended for full benefits).
  • Small projects with simple dependency trees (overhead may not justify use).
  • Workflows requiring HHVM (no longer supported).
  • Teams needing dynamic merging logic beyond static composer.json resolution (e.g., environment-specific overrides).

How to Pitch It (Stakeholders)

• Executives: "This update future-proofs our dependency management by mandating Composer 2.0—cutting build times by 30% and aligning with PHP 7.2+ LTS. For our modular SaaS platform, it eliminates merge conflicts in composer.json while reducing CI/CD complexity by dropping HHVM. Zero cost, zero risk, and backed by Wikimedia’s production use."

• Engineering: *"v2.0.1 enforces Composer 2.0 (required for new features) and PHP 7.2+, but keeps the same battle-tested modular dependency resolution. Key wins:

  • Faster installs/updates (Composer 2.0 optimizations).
  • Cleaner pipelines (no HHVM baggage).
  • Granular control over module dependencies via config files. Migration is trivial—just update composer.json and PHP versions. Let’s leverage this to standardize our monorepo workflows."*