- What is perform/notification-bundle used for?
- It provides a structured notification layer for defining, dispatching, and managing notifications through configurable publishers. It is actually a Symfony bundle, so in Laravel it is not a drop-in for Illuminate\Notifications. Use it as a reference for notification-domain scoping unless you deliberately build a Laravel bridge.
- Can I install perform/notification-bundle with Composer in a Laravel app?
- Composer installation is possible in principle, but integration is the real cost. You would need service container bindings, a config publisher, event mapping, and possibly a mailer shim if it composes Symfony Mime messages directly. Confirm PHP and framework constraints before spending evaluation time.
- How does perform/notification-bundle compare to Laravel's built-in notifications?
- Laravel already ships channel-based dispatch, the Notifiable trait, queueing, on-demand routing, and database and broadcast channels. This package offers a configurable notification layer but does not demonstrate capability the native stack lacks cheaply. Default to Illuminate\Notifications plus a thin internal dispatcher interface.
- What Laravel versions does perform/notification-bundle support?
- No Laravel version support is established because the package is Symfony-oriented. The assessment says to confirm PHP and Laravel version constraints before evaluating further. Do not assume compatibility; test in a branch with exact pinning.
- How do I configure perform/notification-bundle for Laravel?
- Configuration would require a Laravel bridge: service container bindings, publishing the Symfony config tree into Laravel config, and mapping events. There is no described Laravel config publisher. Budget permanent maintenance for that bridge because you own it regardless of vendor activity.
- Is perform/notification-bundle safe for production notifications like password resets and receipts?
- Be cautious; notifications sit on the critical path for support and compliance. The package has 0 stars, 0 dependents, no audit, no CVE history, and a single-vendor shape. A silent delivery regression is an incident, so use exact pinning, lockfile review, and monitoring if you trial it.
- How do I test perform/notification-bundle in a Laravel application?
- Write contract tests around your own dispatcher interface and integration tests around the bridge. Test channel dispatch, queue behavior, recipient routing, and failure paths. There is no third-party corpus or external adoption to rely on.
- What are alternatives to perform/notification-bundle for Laravel?
- Laravel's native notification system is the main alternative and covers channel dispatch, queueing, and on-demand routing. A thin internal NotificationDispatcher interface keeps delivery logic clean and maintainable. Use this package only behind that interface if upstream health checks pass.
- Who maintains perform/notification-bundle and what happens if it is abandoned?
- The repository is a read-only subtree split of an upstream monorepo, so fixes go upstream, not to the split. The adoption signal is effectively nil and abandonment risk is high. If upstream goes quiet, you own a fork; verify the license permits forking and internal maintenance.
- Can perform/notification-bundle implement Laravel's notification dispatcher contract?
- It is unproven whether it can implement Illuminate\Contracts\Notifications\Dispatcher or whether it forces callers onto its own contract. The assessment lists this as a key question before design. Confirm it early; otherwise keep native Laravel notifications behind your own interface.