Support Laravel Package

Product Decisions This Supports

• Frontend stack choice (Vue vs. React): v1.1.0 adds React support alongside the existing Vue foundation, so the package no longer forces a frontend decision. A PM can now scope a single Laravel back end serving both component ecosystems instead of picking one at the architecture stage.
• Framework upgrade timing: Explicit Laravel 13 compatibility means the package is a viable dependency when planning the next framework upgrade, reducing the risk of blocking on third-party UI layers.
• Build vs. buy for shared UI primitives: Parity fixes between React and Vue (Modal closeOnBackdrop now honored in both) indicate an actively maintained shared component layer — a candidate to adopt rather than rebuild modals, overlays, and foundational UI behaviors in-house.
• Roadmap sequencing: Additive, minor-version scope with no breaking changes means adoption can be scheduled in a normal sprint; the React track is new and should be treated as an emerging path (first contribution from this author) rather than fully mature.
• Cross-team reuse: A single support package with two frontend bindings supports decisions about consolidating design-system primitives across teams rather than maintaining parallel Vue and React implementations.

When to Consider This Package

Consider adoption when:

• You are on (or planning) Laravel 13 and need a maintained support/UI foundation layer.
• You have — or anticipate — both Vue and React surfaces and want consistent behavior for primitives like modals, rather than two divergent in-house implementations.
• Your team is small and would rather consume shared foundation code than own the maintenance of component-level parity.
• You value predictable, small-scope releases: v1.1.0 is additive, with no deprecations or breaking changes, so upgrade cost is low.

Look elsewhere or defer when:

• You need React support that is battle-tested: the React path is effectively new in this release and arrives via a first-time contributor. Validate it against your own use cases before committing.
• Your stack is Vue-only and stable; the incremental value of this release is mostly parity bug-fixing (Modal closeOnBackdrop), which may not justify a version bump on its own.
• You require a formal support policy, LTS guarantees, or documented deprecation windows — nothing in these notes speaks to that.
• You are not on Laravel 13 and have no near-term upgrade plan; the headline compatibility work is not yet load-bearing for you.
• Your needs are heavier than primitives (full admin panel, routing, auth). Confirm whether a support layer is the right altitude before adopting.

How to Pitch It (Stakeholders)

To executives: This is a low-risk, incremental release of a Laravel support package we are evaluating. It removes a strategic constraint — we are no longer forced to choose Vue or React for shared UI foundations — and it keeps us current on Laravel 13. There are no breaking changes, so the cost of adoption is contained. The caveat is that the React support is brand new; we would treat it as promising but unproven until we run our own validation.

To engineering: v1.1.0 adds React support and Laravel 13 compatibility, and ports the React foundation fixes to Vue so that both bindings now honor Modal closeOnBackdrop. Practically: one support layer, two frontend bindings, consistent primitive behavior. Two things to note — the React track lands via a first-time contributor, so budget time for evaluation rather than assuming parity with the Vue path; and the rest of the diff is CI dependency bumps (actions/checkout, setup-node, action-gh-release, fetch-metadata), which are housekeeping, not functionality. Recommended next step: spike the React path against two or three of our real modal/overlay use cases and confirm Laravel 13 behavior in a staging branch before we commit it to the roadmap.