Laravel Package Tools Laravel Package

Product Decisions This Supports

• Build vs. Buy: Accelerates internal package development by reducing boilerplate code, avoiding reinventing Laravel package infrastructure.
• Roadmap: Enables faster iteration on reusable components (e.g., Blade views, migrations, CLI tools) for cross-cutting features like auth, reporting, or integrations.
• Feature Prioritization: Justifies investment in internal package ecosystems (e.g., a "Design System" package, "Analytics" package) by streamlining maintenance and adoption.
• Use Cases:
  • Monorepo teams: Standardize package structure across microservices.
  • Marketplace products: Ship Laravel packages with consistent UX (e.g., vendor:publish workflows, config defaults).
  • Legacy modernization: Refactor spaghetti code into modular packages with minimal refactoring overhead.

When to Consider This Package

• Adopt if:
  • Your team builds 3+ Laravel packages or maintains reusable components (e.g., Blade views, migrations).
  • You need consistent vendor:publish workflows (configs, assets, migrations) across packages.
  • Your packages require Blade components, Inertia support, or CLI tools with minimal setup.
  • You want to reduce onboarding friction for developers consuming your packages (e.g., auto-publishing migrations).
• Look elsewhere if:
  • Your packages are trivial (e.g., single-file utilities) or don’t need Laravel’s ecosystem.
  • You’re using non-Laravel frameworks (e.g., Symfony, Livewire-only apps).
  • Your team lacks PHP/Laravel expertise to leverage the package’s conventions (e.g., stub files, service providers).
  • You need advanced package features (e.g., dynamic package discovery, conditional registration) not covered by this tool.

How to Pitch It (Stakeholders)

For Executives:

"This tool cuts the time to ship Laravel packages by 80%, reducing technical debt and accelerating feature delivery. For example, our [Auth Package] currently requires 2 weeks of setup—this would shrink that to 2 days. It also standardizes how our teams publish configs, migrations, and assets, making updates 10x faster and reducing support tickets from inconsistent installations."

ROI:

• Dev Velocity: Teams build and maintain packages 3x faster.
• Consistency: Eliminates "works on my machine" issues with standardized vendor:publish workflows.
• Scalability: Enables a package-first architecture for large codebases (e.g., splitting monoliths into modular services).

For Engineering:

*"This is the Laravel Package Starter Kit—it handles all the boring setup so you can focus on business logic. Key benefits:

• Zero boilerplate: Register configs, migrations, Blade components, and CLI tools in one fluent API.
• Developer experience: Auto-generates vendor:publish tags and stub files (e.g., service providers).
• Future-proof: Works with Blade, Inertia, and Livewire; integrates with Spatie’s other tools (e.g., laravel-activitylog).

Example: To add a Blade component, you just:

$package->hasViewComponent('alert', Alert::class);

No manual composer.json tweaks or service provider hacks.

Tradeoff: Requires adopting Spatie’s directory structure (but their package-skeleton makes this trivial)."*