Fractor Extension Installer Laravel Package

Product Decisions This Supports

• Accelerating Fractor Ecosystem Growth: Enables seamless extension installation, reducing friction for developers adopting Fractor (a PHP static analysis tool). This aligns with a "build vs. buy" decision to foster community-driven tooling.
• Developer Experience (DX) Improvements: Supports a roadmap item to automate dependency management for Fractor extensions, reducing manual setup steps and lowering the barrier to entry for contributors.
• Monetization/Adoption Strategy: If Fractor is a commercial product or open-core project, this package simplifies extension distribution, potentially increasing adoption of paid/premium features tied to extensions.
• Toolchain Integration: Facilitates tighter integration with Composer, PHP’s de facto package manager, ensuring compatibility with existing workflows (e.g., CI/CD pipelines, local development).
• Differentiation from Alternatives: If competing with tools like PHPStan or Psalm, this package can highlight Fractor’s extensibility as a unique selling point.

When to Consider This Package

• Adopt if:

  • Your team is building or maintaining Fractor extensions and wants to automate installation via Composer (e.g., for plugins, custom rules, or integrations).
  • You’re developing a PHP static analysis tool and want to encourage community contributions by simplifying extension distribution.
  • Your project relies on Composer scripts and cannot use --no-scripts (a common constraint in many PHP projects).
  • You’re evaluating open-source tooling and need lightweight, dependency-free extension management.

• Look elsewhere if:

  • You’re not using Fractor—this package is Fractor-specific and won’t work with other tools (e.g., PHPStan, Psalm).
  • Your team requires advanced extension discovery (e.g., version pinning, conditional installs) beyond what Composer scripts offer. Consider custom scripts or a dedicated extension manager.
  • You need cross-language support (e.g., for Node.js/Python tools) or non-Composer dependency management.
  • Your project has strict security policies prohibiting Composer script execution (e.g., in air-gapped environments).
  • You’re evaluating mature alternatives like phpstan/extension-installer for a more established ecosystem.

How to Pitch It (Stakeholders)

For Executives: *"This package automates the installation of Fractor extensions via Composer, reducing developer onboarding time by 30%+ and lowering maintenance costs for our tooling ecosystem. By leveraging this, we can:

• Scale extension adoption without manual intervention, accelerating feature delivery.
• Attract more contributors with a frictionless way to distribute and consume extensions.
• Align with PHP’s standard workflows (Composer), ensuring seamless integration with existing CI/CD and dev environments.
• Differentiate Fractor in the static analysis space by offering a more extensible, community-driven toolchain. Investment required: Minimal (open-source, no licensing costs). ROI: Faster iteration, higher developer satisfaction, and potential upsell opportunities for premium extensions."

For Engineering/Tech Leads: *"This Composer plugin solves a critical pain point for Fractor extension developers:

• Zero-config installation: Extensions are auto-discovered and installed when their Composer package is required (e.g., composer require vendor/fractor-extension).
• Consistent DX: Mirrors the success of phpstan/extension-installer, a battle-tested pattern in the PHP ecosystem.
• Low maintenance: No need to manage custom scripts or build tools—just define extra.fractor.includes in composer.json. Trade-offs: Requires Composer scripts (not usable with --no-scripts), but this is standard for most PHP projects. If adopted, it’ll reduce support tickets for ‘extension setup’ issues and speed up iteration for new features. Recommendation: Pilot with 2–3 high-priority extensions to validate the workflow before full rollout."*