Weave Code
Notificationbundle Laravel Package
flowcode/notificationbundle
A PHP notification bundle from flowcode that provides a structured way to create, manage, and deliver notifications within your application, with bundled components for quick setup and integration into existing projects.
This is a bundle for notifications for symfony
Frequently asked questions about Notificationbundle
- What is flowcode/notificationbundle used for?
- It is a PHP notification layer that lets you define a notification once and deliver it over email, SMS, push, or in-app channels. It bundles pluggable channel transports, per-channel templates with shared rendering data, queue-aware dispatch with retries, backoff and failure hooks, user-level preferences and opt-outs, and extensible events for logging and custom channels. The important caveat is that it is packaged as a Symfony bundle, not a Laravel package.
- Is flowcode/notificationbundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle. Bundles are a Symfony runtime packaging format built around a Bundle class, a DependencyInjection extension, a Configuration tree, services.yaml wiring, and hooks into the Symfony kernel lifecycle. Laravel has no bundle loader and this repository ships no adapter, so there is no real integration surface for a Laravel application.
- How do I install flowcode/notificationbundle in a Laravel application?
- There is no supported installation path. Composer may pull the source, but Laravel will never register the bundle, so none of its services or configuration load. The only workaround is a service provider that manually instantiates the bundle services while bypassing its DI extension, which throws away most of the package value and guarantees breakage on upstream changes. That is a fork with extra steps, not an integration.
- Which channels does flowcode/notificationbundle support and how are templates configured?
- The package advertises email, SMS, push, and in-app delivery through pluggable transports that share a consistent send contract. Per-channel templates share a common data payload so one notification definition can render differently per transport. Configuration lives in Symfony's Configuration.php tree and services.yaml wiring, which has no equivalent loading path inside a Laravel application.
- Does Laravel already have a native notification system that covers this use case?
- Yes. Laravel ships first-party notifications including the Notifiable trait, Notification classes, mail, database, broadcast and Slack channels, ShouldQueue support, retries, and failed_jobs visibility. The capability this package describes already exists in-stack, so adopting it would mean building a bridge to something strictly less integrated. The package shape is still a useful architectural reference if you write a notification spec.
- What are the alternatives to flowcode/notificationbundle for email, SMS, push, and in-app notifications?
- On Laravel, use the native notification system with queued channels and Horizon or failed_jobs for visibility. On genuine Symfony, the first-party symfony/notifier component is the correct target. If the real requirement is a cross-framework abstraction, that is a design problem to solve against a maintained component rather than an unvetted bundle.
- Which Laravel, PHP, and Symfony versions does flowcode/notificationbundle support?
- No version matrix, CI configuration, or published supported-version range is visible, and there is no evidence of tagged releases rather than a dev-main branch. Read composer.json constraints and Packagist release history before assuming compatibility. Because PHP and framework majors move annually, an unreleased bundle will not track them, which is a real drift risk even on Symfony.
- Is flowcode/notificationbundle actively maintained and safe for production?
- The adoption signals are disqualifying: zero stars, zero dependents, and no download history means no downstream project has validated that it installs or survives an upgrade. There is no visible CI badge, no test suite, no release cadence, and it appears to be a single-maintainer repository, so there is no clear CVE patch path or bus factor. Notifications touch outbound email and SMS, transactional messaging, and PII in payloads, which makes an unvetted dependency a bad trade even when the code itself looks fine.
- Does flowcode/notificationbundle have a license, and can I use it commercially?
- No LICENSE file is evidenced in the repository. An absent license is arguably a legal blocker for commercial use rather than a nice-to-have, so this needs resolution before any technical review continues. Confirm with the maintainer and with legal before writing a single line of integration code.
- How do I test notifications if I adopt flowcode/notificationbundle?
- There is no test suite in the repository to read or reuse, so you would be building your own harness from scratch. Because there is no Laravel integration, exercising the transports means booting Symfony kernel and container pieces manually. With Laravel's native notifications you get Notification::fake, assertSentOnDemand, and queued-job assertions out of the box instead.
Weaver
How can I help you explore Laravel packages today?