Weave Code
Notification Bundle Laravel Package
idci/notification-bundle
A Symfony bundle for building in-app notification systems: define notifications, queue and dispatch them to users through configurable channels, and manage read/unread state with Doctrine-backed entities and event-driven notifiers.
Symfony2 notification bundle
Frequently asked questions about Notification Bundle
- Is idci/notification-bundle compatible with Laravel?
- No. It is a Symfony2 full-stack bundle built on AppKernel registration, XML/YAML DI service definitions, Doctrine ORM entities and Symfony's EventDispatcher. It ships no Laravel ServiceProvider, no facade, no publishable config and no package auto-discovery. Making it work in Laravel would require a shim running a foreign container and ORM inside your app, which is a net-negative architecture decision.
- Can I install idci/notification-bundle in a Laravel 10 or 11 app with Composer?
- You can attempt it, but Composer will most likely fail dependency resolution on a modern PHP 8.2+ runtime. The package targets PHP 5.x/7.0-era constraints, Doctrine and Swiftmailer, none of which line up with current illuminate/* requirements. Even if resolution succeeded, nothing would register with Laravel's container automatically. The practical answer is to not install it and use Laravel's native notifications instead.
- Which PHP and Symfony versions does idci/notification-bundle support?
- The bundle is written for Symfony2-era conventions, so expect PHP 5.x and early PHP 7 constraints. Symfony2 reached end of life in November 2018, and there is no PHP 8 support, no Symfony 5/6/7 support and no Laravel version constraint of any kind. Treat it as legacy code rather than a maintained dependency.
- How do you install and configure idci/notification-bundle in a Symfony application?
- In a Symfony2 project you would require it via Composer, register the bundle class in AppKernel, and define your notification channels and notifiers through the bundle's Symfony configuration tree and DI service definitions. Notification content is template-driven, and persistence uses Doctrine entities and repositories. None of these steps have a Laravel equivalent in the package.
- What features does idci/notification-bundle actually provide?
- It separates notification creation from delivery using notifiers, configurable channels and reusable services so messages are generated and dispatched consistently. It supports template-driven content, extensible custom delivery logic, and Doctrine-backed read/unread state for recipients. Dispatch is event-driven through Symfony's EventDispatcher. The domain model is sound, but Laravel has shipped equivalent capabilities natively since 5.3.
- Is idci/notification-bundle maintained and safe for production use?
- There is no meaningful maintenance signal: roughly four stars, zero dependents and no downstream usage to surface bugs or drive patches. The Symfony2 dependency tree pins unsupported PHP versions and third-party libraries, some with known CVEs. Installing it on a modern stack risks either failed resolution or vulnerable transitive packages. For a Laravel application the answer is clearly no.
- How do I replace idci/notification-bundle with Laravel's native notification system?
- Model notifications with the Notifiable trait and the standard notifications table migration, then express each delivery route as a via() method returning channel identifiers. Implement delivery through MailMessage, DatabaseNotification, or a maintained channel package for SMS, chat and push. Do not attempt an incremental install path; frame it as a small build decision and budget days, not weeks. The upstream repository is best treated as a specification, not a dependency.
- What Laravel alternatives exist for building in-app notifications?
- Laravel's built-in notification system covers mail, database and broadcast channels out of the box, and laravel-notification-channels adds maintained drivers for SMS, Slack, push and similar transports. For in-app inbox UIs, packages built on database notifications give you read/unread state without a custom schema. These cover everything the IDCI bundle advertises, with active maintenance and PHP 8 support.
- How do I test notifications after migrating from idci/notification-bundle to Laravel?
- The original bundle offers no Laravel-aware test helpers, so you cannot reuse its testing approach directly. Once ported, use Notification::fake() with assertSentTo, assertNotSentTo and assertSentTimes in Pest or PHPUnit feature tests. Pin any ported routing or batching rules with plain unit tests on the extracted service classes. This gives you far stronger coverage than the upstream code ever had.
- Which domain logic from idci/notification-bundle is worth porting to Laravel?
- Only the non-obvious rules: recipient resolution, channel routing rules and digest or batching behavior. Port those as explicit service classes behind an interface, bound in a Laravel service provider, with unit tests pinning the existing behavior. The notifier-per-channel pattern itself adds no value because Laravel's via() methods already express it. Everything else is framework plumbing you should leave behind.
Weaver
How can I help you explore Laravel packages today?