Devtools Laravel Package

Product Decisions This Supports

• Standardization of Dev Tooling: Eliminates fragmentation in PHP/Laravel development environments by consolidating dev dependencies (Pest, Larastan, Pint, Blade tools) into a single, version-locked package. Reduces "it works on my machine" issues and accelerates onboarding for new engineers.
• Accelerated Feature Development: Aligns tooling with modern Laravel ecosystems (Filament v4, Livewire, PestPHP), enabling teams to leverage plugins (e.g., pest-plugin-livewire) without manual setup. Ideal for SaaS platforms or projects with rapid iteration cycles.
• Build vs. Buy Decision: Avoids reinventing dependency management for dev tools, saving engineering time while maintaining flexibility. The meta-package approach is more sustainable than maintaining a custom composer.json for dev dependencies.
• Roadmap Alignment:
  • Testing: Simplifies migration to PestPHP (if transitioning from PHPUnit) with built-in plugins for Laravel/Livewire.
  • Static Analysis: Ensures consistent Larastan/PHPStan rules across projects, reducing technical debt.
  • Code Quality: Pint integration enforces PSR-12 compliance, critical for open-source or collaborative projects.
• Use Cases:
  • Laravel Monorepos: Standardizes dev tooling across microservices or shared libraries.
  • Agency/Contract Work: Provides a pre-configured dev environment for client projects.
  • Education/Boilerplates: Serves as a template for new Laravel projects, reducing setup time.

When to Consider This Package

• Adopt if:
  • Your team uses Laravel 9+ and relies on PestPHP, Filament v4, or Livewire for development.
  • You prioritize consistency in dev tooling (testing, linting, static analysis) across projects or teams.
  • Your roadmap includes frequent updates to Laravel/PHP tools (e.g., Pint, Larastan) and you want to avoid manual version management.
  • You’re adopting PestPHP and need plugins (Livewire, Laravel) without additional configuration.
  • Your CI/CD pipeline requires unified tooling to reduce flakiness (e.g., Pint failures, Larastan inconsistencies).
• Look elsewhere if:
  • Your stack is non-Laravel PHP (Symfony, Lumen, etc.) or uses tools not included (e.g., Symfony’s PHP-CS-Fixer).
  • You need active community support (low stars/dependents suggest niche adoption; prefer packages like laravel-shift/php-console-color or nunomaduro/collision for broader use).
  • Your team customizes dev tools heavily (e.g., custom PHPStan rules, bespoke Pint presets) and prefers granular control over a meta-package.
  • You require older Laravel versions (e.g., <8.0) or tools not compatible with the package’s defaults (e.g., Pest v3).
  • Your project has strict compliance requirements (e.g., audit logs for every dev dependency) that a meta-package obscures.

How to Pitch It (Stakeholders)

For Executives: "moox/devtools is a meta-package that standardizes our Laravel dev environment by bundling PestPHP, Larastan, Pint, and Livewire testing tools into one dependency. This reduces onboarding time for new engineers by ~30%, minimizes tooling conflicts in CI/CD, and aligns with our roadmap to adopt PestPHP and Filament v4. The MIT license ensures no vendor lock-in, and the package’s focus on compatibility—rather than innovation—makes it a low-risk, high-reward choice. For a team of 5 engineers, this could save ~10 hours/month in setup and maintenance."

For Engineering: *"This package replaces manual composer.json bloat with a maintained, version-locked set of Laravel dev tools. Here’s why it’s worth adopting:

• One-line setup: Add moox/devtools to require-dev and get Pest, Larastan, Pint, and Blade testing tools pre-configured.
• Future-proof: Auto-updates tools like Pint/Larastan without manual version hunting. Example: No more fighting with php-cs-fixer vs. pint conflicts.
• Plugin-ready: Built-in support for Pest plugins (Livewire, Laravel) means we can test components without extra setup.
• Tradeoffs:
  • Limited to Laravel/PHP (not a Symfony package).
  • Obscures individual tool versions (but we can document overrides in DEPENDENCIES.md).
  • Requires validation against our existing composer.json for conflicts.

For Developers: *"If you’re tired of configuring Pest, Larastan, and Pint separately, this package does it for you. Key perks:

• PestPHP out of the box: Write tests in tests/Feature/ with Livewire/Laravel helpers.
• Blade testing: Use {{ @capture }} directives to test Blade templates.
• CI-friendly: Pint and Larastan are pre-configured for GitHub Actions. Gotcha: Avoid mixing this with manually installed Pest plugins—stick to the package’s versions unless you’re okay with conflicts. Start by adding it to a feature branch and running ./vendor/bin/pest to test compatibility."*