Mq React Laravel Package

Product Decisions This Supports

• Static analysis and type-safety roadmap. Typed handler arguments (v1.7.0, #51) let handlers declare concrete parameter types instead of relying on untyped, runtime-checked arguments. This is the enabling capability for teams gating merges on PHPStan/Psalm at high strictness — a prerequisite we should treat as a checklist item for any "modernize to strict types" initiative.
• Platform modernization / runtime currency. The suite now runs on PHP 8.3 and 8.4. That is a purchasing-style signal, not just a CI detail: it means the dependency will not be the thing blocking an org-wide PHP upgrade, and it keeps us inside the vendor security-patch window.
• Build vs. buy: buy, and keep buying. Scope is narrow (template dispatch plus handler registration). In-house equivalents look trivial to write and are not: the cost sits in typed-signature handling, edge-case dispatch behavior, and ongoing runtime-matrix maintenance. Re-implementing buys us a permanent maintenance line item to save a composer constraint.
• Use cases this unlocks. User- or tenant-supplied templates with custom handlers (notification/email templating, internal CMS-lite tooling, generated reports) where handler code is ours and static analyzability matters. Typed arguments make these integrations cheaper to review and safer to hand to less senior engineers.
• Documentation investment is a leading indicator. Two of the five merged PRs are docs/examples (#44, #47). For a small-scope utility package, docs quality is the dominant onboarding cost; treat this as reduced ramp-up time for new contributors rather than as a feature.
• Not a roadmap item. v1.7.0 adds no user-facing capability, no performance commitment, and no API surface we would market. Do not let it consume roadmap slot or launch narrative.

When to Consider This Package

Adopt when:

• The team's PHP baseline is 8.3+ (or the upgrade is already funded) and you want the dependency to track, not lag, the runtime.
• Your handlers are your own code and you want them typed, autocompleted in the IDE, and checked in CI rather than discovered in staging.
• The templating need is genuinely narrow: render templates, register discrete handlers, keep the rest of the application framework-idiomatic (Laravel's container, service provider registration).
• You want a small, single-responsibility dependency you can read in an afternoon — a real advantage for security review and for engineers inheriting the codebase.
• You are already standardizing on the ReactPHP-adjacent ecosystem (clue-maintained packages) and value consistent conventions over maximal feature surface.

Look elsewhere when:

• You need to execute untrusted templates. Sandboxing and resource limits are an architecture concern this package does not claim to solve; pick a template engine with an explicit security posture.
• You need a rich out-of-the-box feature set (inheritance, macros, i18n, caching layers). Composing those around a minimal core is work you should cost honestly against a batteries-included alternative.
• You require a commercial SLA, named support contacts, or a vendor security questionnaire with a counterparty. This is community-maintained; the bus factor is a genuine procurement objection, not a formality.
• Handler signatures are currently written loosely against this package's earlier behavior. Minor-version typed-argument improvements are semver-compatible in intent, but verify with a dependency-update branch and the full test suite before rollout — a "typing improvement" is exactly the class of change that surfaces latent runtime-only assumptions.

How to Pitch It (Stakeholders)

For executives (30 seconds). This is a routine maintenance update to a small, narrow-scope open-source dependency — no new product capability, no user-visible change, no new spend. Its value is risk reduction: it confirms the library runs on the PHP versions we are standardizing on, and it improves integration safety by letting our code be type-checked before it ships. Recommendation: keep it current, no roadmap impact, no decision required.

For engineering leadership. v1.7.0 is a semver-minor release with three things that matter to us. First, templates now support typed handler arguments — handler signatures can be statically checked and IDE-assisted, so integration mistakes fail in CI instead of at runtime. Second, the test matrix covers PHP 8.3 and 8.4, which keeps this dependency off the critical path of our runtime upgrade and inside the security-patch window. Third, documentation and examples were materially improved, lowering the cost for the next engineer who touches this code. Cost of adoption is a composer bump plus a green pipeline; the only meaningful residual risk is single-maintainer concentration, which we should track on the dependency register rather than solve by forking. Ask: schedule the bump in the next maintenance window and add a one-line static-analysis check on handler signatures so we actually capture the benefit this release provides.