Weave Code
Notification Bundle Laravel Package
modera/notification-bundle
Modera Notification Bundle adds a flexible notification system to Modera CMS applications, letting you compose, queue, and deliver messages through channels like email and SMS, with reusable templates, recipient handling, and simple integration into Laravel-based projects.
Provides functionality for storing/retrieving notifications.
Frequently asked questions about Notification Bundle
- Is modera/notification-bundle a Laravel package?
- No. It is a Symfony bundle from the Modera business-application platform, shipping a Bundle subclass, dependency-injection extension, compiler passes, and Doctrine ORM entity mappings. It has no Laravel service provider, facade, or publishable config, so it is not a drop-in Laravel package.
- Can I install modera/notification-bundle in Laravel 10 or 11?
- Not practically. The last release was 2017-12-12 and targets the PHP 5.6/7.0 and Symfony 2.x/3.x era, so Composer resolution against a modern Laravel app on PHP 8.2 or 8.3 is likely an unsolvable conflict. Forcing compatibility would mean pinning Doctrine ORM 2.x and maintaining a Symfony container bridge, which is a large permanent tax for a notification table.
- What does modera/notification-bundle actually do?
- It adds a reusable notification layer to Symfony applications, separating what to notify from how it is delivered. You define notification types, render content from templates with overridable layouts, dispatch through configurable channels, and use event hooks before and after sending. The capability is useful, but the implementation is Symfony-specific.
- Does modera/notification-bundle support email and SMS delivery channels?
- It is designed around pluggable delivery channels and transport configuration, and the blurb cites email and SMS as examples. The overview does not document a Laravel notification channel integration, so any transport details would need source-level verification. Because the bundle is stale, audit each channel before relying on it.
- Does modera/notification-bundle support queued notifications, digests, or batching?
- That is not confirmed in the provided overview or evaluation. The technical assessment explicitly asks whether any queue, digest, or batching abstraction exists, and warns that dispatch may be synchronous. Treat dispatch as synchronous until the source proves otherwise, and use Laravel's queueable notifications if you need background delivery.
- Is modera/notification-bundle maintained or abandoned?
- The last release was 2017-12-12, roughly eight years ago, with 2 stars, 0 dependents, and an adoption score of 0.16. There is no production usage to learn from and no crowd-sourced bug surface. Unless a Modera commercial support path exists, treat it as an abandoned internal artifact.
- What Laravel and PHP versions does modera/notification-bundle support?
- It does not list Laravel support at all; it is a Symfony bundle from the PHP 5.6/7.0 and Symfony 2.x/3.x era. On PHP 8.1+ with a modern Doctrine ORM, its docblock annotation mappings are likely a hard failure rather than a warning. Laravel 10 or 11 on PHP 8.2+ is the wrong host for this package.
- What are the best Laravel alternatives to modera/notification-bundle?
- Laravel already provides Illuminate\Notifications with the database channel, the Notifiable trait, a notifications table, read/unread state via read_at, and channel fan-out. You can add mail or SMS channels through Laravel's notification system and keep delivery logic in framework-native code. For custom persistence, build a narrow NotificationStore interface rather than porting a Symfony bundle.
- Can I extract the data model or schema from modera/notification-bundle for Laravel?
- Yes, data-model extraction is the feasible part, estimated at roughly one to two engineer-days. Read the Doctrine entity schema, port it to Eloquent migrations, and reimplement the store and retrieve service behind a clean interface such as create, forRecipient, markRead, and unreadCount. Check whether the recipient model is user-only or supports roles, groups, or tenancy, because that schema may be the only asset worth reading.
- How should I test or evaluate modera/notification-bundle before using it?
- Treat the repository as a design document, not a dependency. Check composer.json requirements and whether it resolves on PHP 8.2 or 8.3, inspect the Doctrine annotations, confirm the recipient model, and determine whether dispatch is synchronous. If the target is Laravel, prototype an Eloquent migration and NotificationStore interface, then test persistence, read/unread state, and channel dispatch in your own app.
Weaver
How can I help you explore Laravel packages today?