Weave Code
Larahook Laravel Package
coinvestor/larahook
LaraHook brings WordPress-style actions and filters to Laravel. Register and run hooks anywhere in your app or packages, prioritize callbacks, and extend behavior without editing core code. A lightweight, familiar API for clean, decoupled customization.
A Hooks Library for Laravel
Frequently asked questions about Larahook
- How do I install coinvestor/larahook in a Laravel app?
- Install it with composer require coinvestor/larahook. Laravel auto-discovery registers the service provider, then publish the config and migrations with vendor:publish. Set your queue connection and run supervised workers before sending real traffic. Feature-flag one endpoint first to validate delivery and logging.
- Which Laravel and PHP versions does LaraHook support?
- LaraHook supports Laravel 11 and 12 today, and version 1.4.3 widens the framework constraint so it can install on Laravel 13. That release is a patch-level compatibility change, not proof of CI validation on Laravel 13. Check the composer.json PHP constraint and diff 1.4.2 against 1.4.3 to confirm no older illuminate/* or PHP ranges were dropped.
- Does LaraHook require a queue driver?
- Yes. LaraHook is built around queue-backed delivery, so you need a durable queue driver such as Redis, SQS, or the database queue plus supervised workers. Synchronous delivery would be a design smell in production because third-party endpoint latency would block requests. The database queue works for low volume but will contend with application writes at scale.
- How are LaraHook actions and filters different from Laravel events and listeners?
- LaraHook brings WordPress-style actions and filters to Laravel, letting you register callbacks and run hooks anywhere in your app or packages. Use priorities to control callback order and extend behavior without editing core code. It is complementary to Laravel events and listeners, not a replacement for an internal event bus. For outbound notifications, treat it as an egress adapter.
- Can I prioritize hook callbacks in LaraHook?
- Yes, callbacks can be registered with priorities so you control execution order. Use priorities to make package extensions predictable and document the convention for your team. Keep critical business logic out of low-priority callbacks that another package could reorder. Test the final order, because hook priority collisions are easy to miss in code review.
- Does LaraHook support signed webhook deliveries and secret rotation?
- Signing secrets are part of a production webhook integration, and you should wire them before enabling external endpoints. Confirm whether LaraHook supports HMAC or shared-secret signing with multiple simultaneously active secrets, which is required for rotation without downtime. If only one active secret is supported, plan a rotation window or handle signing at the endpoint layer. Also confirm the signature header and payload canonicalization your consumers should verify.
- What are the default timeout, retry count, and backoff strategy in LaraHook?
- Timeout, retry count, and backoff defaults become your production behavior, so treat them as configuration, not package trivia. Review the published config and confirm whether these can be set per endpoint. If they are global-only, document the limitation and route high-risk endpoints through a separate queue or wrapper. Do not assume the defaults match your partners' SLAs.
- Is there delivery logging, idempotency, and replay support?
- Check the persistence model for delivery attempts and expose retry and dead-letter visibility to support staff. Ask whether each delivery carries an idempotency or delivery-ID header so consumers can dedupe repeated attempts. Define a pruning and retention policy for delivery logs before volume grows. Replay tooling is usually custom product surface, not something the package fully solves.
- How do I migrate to LaraHook from hand-rolled webhooks or spatie/laravel-webhook-server?
- Greenfield: install 1.4.3, publish assets, map domain events to payloads, and ship behind a feature flag to one partner endpoint. From hand-rolled webhook code, dual-send to the new pipeline while the legacy sender remains authoritative until delivery logs match for about two weeks or a defined delivery count. From spatie/laravel-webhook-server, expect different data models, so write a one-off backfill of endpoint and subscription records. Do not attempt in-place table reuse; stand up new tables alongside the old ones.
- Is LaraHook actively maintained and does it have a security policy?
- LaraHook is maintained by CoInvestor as a single-maintainer or small-team package with a modest 1.x release cadence. Laravel major-version support tends to arrive reactively, and 1.4.3 is a positive signal that Laravel 13 support landed. Confirm the maintainer-of-record and whether a published security policy exists. Pin the version, review composer.json diffs between releases, and keep an exit path if maintenance stalls.
Weaver
How can I help you explore Laravel packages today?