Plugins Laravel Package

Product Decisions This Supports

• Build vs. buy on extensibility: if the roadmap includes third-party or first-party "plugins/modules" (marketplace, white-label add-ons, customer-specific extensions), this package supplies the plugin registry, dependency resolution, and generated stubs you would otherwise spend a sprint or two building and a quarter maintaining.
• Roadmap timing — Laravel 13: v1.1.0 adds Laravel 13 compatibility. This is the decision-relevant item: it de-risks a framework upgrade and means the plugin layer is not the blocker on your Laravel 13 migration plan. Confirm the rest of your dependency graph before committing to a date.
• Frontend stack flexibility: new React support means the plugin scaffolding is no longer a single-stack bet. If your product is React/Inertia or you have teams split across Vue and React, this removes the "we'd have to standardize first" objection.
• Plugin ecosystem quality: fixes to plugin dependency handling and generated stubs directly affect the developer experience of anyone writing a plugin. Better stubs = shorter time-to-first-plugin for internal teams and external partners, which is the metric that predicts whether an extension ecosystem actually materializes.
• Release hygiene as a signal: the release is overwhelmingly Dependabot bumps plus a test-suite fix. Read that as a maintenance-mode-but-alive cadence: safe to adopt, but do not plan around a rapid feature roadmap.

When to Consider This Package

• You are building a modular Laravel application or a product where customers/partners ship their own extensions, and you need discovery, enable/disable, and inter-plugin dependency resolution.
• You are on, or about to move to, Laravel 13 and want the plugin layer already compatible.
• You need consistent scaffolding (stubs) so plugins across teams follow one structure rather than N bespoke conventions.
• Your frontend is React, Vue, or mixed and you do not want the plugin system to force a stack choice.

Look elsewhere or build in-house when:

• You only need internal module separation — Laravel's own service providers, package discovery, and nwidart/laravel-modules cover that with a larger community and more documentation.
• You need a guarantee of long-term support, a security-response commitment, or an SLA. This is a young package (first-time contributor on this release, v1.0.x → v1.1.0 within months) — budget for the possibility of forking.
• Plugin dependency semantics are core to your product. The dependency-handling fix in this release implies the previous behavior was wrong; validate your specific dependency graph with a spike before designing a marketplace around it.
• You need rich plugin lifecycle features (versioned migrations per plugin, sandboxing, licensing/billing hooks). Verify these exist before assuming; the release notes do not demonstrate them.

How to Pitch It (Stakeholders)

To executives: This is the extensibility layer for the platform — the piece that lets partners and customers add functionality without us shipping every feature ourselves. v1.1.0 makes it compatible with Laravel 13, so adopting it now avoids being locked out of the next framework upgrade, and it supports both React and Vue so we are not forced into a frontend standardization project first. Cost is low and it is a normal Composer dependency; the main risk is that it is a young package, so we should treat it as a candidate we validate with a time-boxed spike rather than a multi-year commitment.

To engineering: v1.1.0 is mostly dependency bumps, plus four things that matter: Laravel 13 compatibility, React support, a fix to plugin dependency handling, and corrected generated stubs. The dependency fix is the one to scrutinize — it suggests prior incorrect behavior, so re-test any dependency chains you rely on. The test suite was also repaired in this release, which means earlier CI signal was unreliable. Recommendation: one spike, one real plugin defined end-to-end, and an exit plan (thin internal abstraction over the registry) so a future fork or replacement is cheap.