Composer Installers Extender Laravel Package

Product Decisions This Supports

• Accelerated Developer Onboarding: Reduces manual setup time for project scaffolding (e.g., Laravel + frontend, databases, or custom tooling) by automating dependency installation via Composer.
• Consistent Environments: Ensures parity across dev/staging/prod by standardizing how non-PHP assets (e.g., Node.js, Python, Docker configs) are bundled with PHP projects.
• Build vs. Buy: Avoids reinventing custom scripts or CI/CD steps for repetitive setup tasks (e.g., "After composer install, run npm install and docker-compose up").
• Roadmap Alignment: Enables future-proofing for multi-language stacks (e.g., adding Go/Rust tools to a PHP monorepo) without architectural debt.
• Use Cases:
  • Monorepos: Bundle PHP + frontend/backend services in a single repo with one composer install.
  • Legacy Modernization: Gradually integrate non-PHP tools (e.g., data pipelines) into existing Laravel apps.
  • Templates/Boilerplates: Ship pre-configured stacks (e.g., "Laravel + Vue + Tailwind") as reusable packages.

When to Consider This Package

Adopt if:

• Your team spends >1 hour/week on manual composer install + post-install steps (e.g., npm, pip, brew).
• You manage multi-language stacks where dependencies aren’t natively supported by Composer (e.g., PHP + Node.js + Python).
• You’re building reusable project templates (e.g., internal Laravel + React starter kits).
• Your CI/CD pipeline has redundant setup scripts (e.g., duplicate npm install commands in composer.json and package.json).

Look elsewhere if:

• Your stack is pure PHP (no need for non-Composer dependencies).
• You’re using Laravel Sail/Docker exclusively (native Dockerfiles may suffice).
• Your team lacks Composer plugin familiarity (requires basic composer.json configuration).
• You need active maintenance (last release in 2020; evaluate forks or alternatives like cweagans/composer-patches).

How to Pitch It (Stakeholders)

For Executives: "This package cuts project setup time by 60% for dev teams by automating the installation of all dependencies—PHP, Node.js, Python, or custom tools—in a single composer install command. For example, a Laravel + Vue + PostgreSQL stack that previously required 3 manual steps (Composer, npm, and brew install postgresql) now deploys with one command. This reduces onboarding friction for new hires, speeds up feature delivery, and aligns with our goal to [reduce dev ops overhead/improve velocity]. The MIT license and low maintenance risk make it a safe bet for our tech stack."

For Engineering: *"This extends Composer’s installer plugin to support arbitrary package types, meaning we can:

• Bundle non-PHP dependencies (e.g., type: "node-package" for vue, type: "python-package" for pandas) in composer.json.
• Replace ad-hoc scripts (e.g., post-install-cmd in package.json) with a unified dependency management system.
• Future-proof our stack for mixed-language projects without custom tooling.

Tradeoffs:

• Requires updating composer.json syntax (minimal learning curve).
• No active maintenance, but the core functionality is stable (last major update in 2020).

Proposal: Pilot this for [specific project/template] to eliminate [X manual steps]. If successful, we can roll it out to all new projects, saving [Y hours/month]."*