Tappable Laravel Package

Product Decisions This Supports

• Accelerating feature development: Enables rapid implementation of customizable, macro-based functionality (e.g., dynamic request/response transformations, middleware extensions) without reinventing core Laravel/Hyperf patterns. Reduces dev time for reusable logic (e.g., API payload formatting, validation hooks).
• Consistency with Laravel ecosystem: Leverages illuminate/tappable (Laravel’s foundation) to ensure compatibility with existing Laravel packages or future Hyperf-Laravel integrations. Avoids fragmentation in hybrid PHP stacks.
• Build vs. buy: Justifies buying this lightweight abstraction over custom middleware/macros, especially for teams already using Hyperf/Laravel. Low risk due to MIT license and minimal overhead.
• Roadmap alignment: Critical for:
  • Teams migrating from Laravel to Hyperf (gradual adoption of Hyperf’s ecosystem).
  • Products requiring extensible pipelines (e.g., event dispatching, command processing).
  • Use cases like plugin architectures or dynamic workflows (e.g., SaaS multi-tenancy hooks).

When to Consider This Package

• Adopt if:

  • Your stack includes Hyperf and you need Laravel-like macro/method tap functionality (e.g., tap(), macro(), after()).
  • You’re building modular systems where runtime method interception (e.g., logging, analytics) is needed without polluting core classes.
  • You prioritize minimalism: The package is ~50 LOC, with no external dependencies beyond Hyperf core.
  • Your team is already familiar with Laravel’s tappable patterns (e.g., from Eloquent or Illuminate containers).

• Look elsewhere if:

  • You’re not using Hyperf: This is Hyperf-specific (though Laravel’s native tappable may suffice).
  • You need advanced AOP (Aspect-Oriented Programming): Consider PHP libraries like goaop/go-aop or brick/math for cross-cutting concerns.
  • Your use case requires performance-critical paths: Macros add reflection overhead; benchmark if used in hot loops.
  • You’re constrained by Hyperf’s maturity: The package is new (last release 2026) with no dependents—validate Hyperf’s long-term viability for your project.

How to Pitch It (Stakeholders)

For Executives: "This package lets our Hyperf-based services adopt Laravel’s battle-tested ‘tappable’ patterns—enabling teams to add reusable, non-intrusive logic (like hooks or middleware) with minimal code. Think of it as ‘Laravel macros for Hyperf’: it’s lightweight, MIT-licensed, and reduces dev time for extensible features. Ideal for products needing dynamic workflows (e.g., plugins, analytics) without locking into Laravel. Risk is low—it’s a thin abstraction with no external dependencies."

For Engineering: *"hyperf/tappable brings Laravel’s illuminate/tappable to Hyperf, giving us tap(), macro(), and after() methods for classes like requests, responses, or commands. Use cases:

• Dynamic middleware: Add cross-cutting logic (e.g., audit trails) without modifying core classes.
• Plugin systems: Let third parties extend our Hyperf services via macros.
• Migration aid: Gradually adopt Hyperf while keeping Laravel-like patterns. Tradeoff: Tiny reflection overhead (~50 LOC), but avoids reinventing wheels. Perfect for teams already using Hyperf or planning Laravel-Hyperf interop."*