Weave Code
Notifications Laravel Package
orchestra/notifications
Orchestra Notifications adds a complete notification layer to Laravel and Orchestra Platform: define notification types and templates, deliver messages across channels like database and mail, and let users read or dismiss alerts from a central inbox.
Orchestra Notifications provides a structured notification layer for Laravel applications built on the Orchestra Platform, giving developers a consistent way to define, dispatch, and manage user-facing notifications. It integrates with Laravel's native notification system while adding Orchestra-specific conventions for message templates, delivery channels, and event-driven dispatch.
- Seamless integration with Laravel notifications and mail
- Configurable, reusable message templates
- Support for multiple delivery channels
- Event-driven dispatching via Orchestra hooks
- Extensible architecture for custom notification types
Frequently asked questions about Notifications
- What is orchestra/notifications used for in Laravel?
- It provides a ready-to-use notification layer for Laravel applications, letting you store, manage, and display user notifications through a simple API. It also includes extensible drivers and integrates with Orchestra Platform components for consistent UI and backend handling. It is aimed at applications that need more than Laravel's base notification sending and want managed user notification records.
- How do I install orchestra/notifications with Composer?
- The package is published as orchestra/notifications, so installation is normally done with Composer in a Laravel application. Before installing, check the package's composer.json constraints against your application's Laravel version rather than assuming the latest tag will resolve. The overview does not document exact install or publishing steps, so follow the repository README and service provider registration guidance.
- Which Laravel versions does orchestra/notifications support?
- The reviewed v6.0.0 release documents support for Laravel Framework v8 only. Laravel 8 reached end-of-life in January 2023, so that release should not be treated as a current compatibility statement. Check the latest release tag and its composer.json for support of newer Laravel versions.
- Is orchestra/notifications compatible with Laravel 10 or 11?
- Based on the reviewed release, v6.0.0 targets Laravel 8 and is unlikely to install cleanly in a Laravel 10 or 11 application due to Composer constraint resolution. That failure is preferable to a silent incompatibility, but it means you must find a newer tag if one exists. Do not assume compatibility without checking the package constraints.
- How do I upgrade orchestra/notifications from v5 to v6?
- The v6.0.0 changelog only documents Laravel 8 support, so there is no documented upgrade guide for breaking changes. You should diff the package's public surface, including config keys, published assets, service provider bindings, and facade signatures, against your current version. Run the full test suite and a static analysis pass in a disposable branch before merging.
- Can I use orchestra/notifications without Orchestra Platform?
- The package is described as a notifications component for Orchestra Platform and integrates with its UI and backend components. Whether the notification layer works standalone depends on its service provider dependencies and configuration, which the provided overview does not detail. Inspect composer.json and the README before assuming standalone Laravel use.
- How do I store and display user notifications with orchestra/notifications?
- The package is intended to let you store, manage, and display user notifications using a simple API and extensible drivers. Display typically involves integrating the package's UI layer or reading stored notifications in your own views. The exact API methods and driver configuration are not covered in the overview, so refer to the repository documentation and source.
- How should I test orchestra/notifications before using it in production?
- Install the candidate version in isolation on a disposable branch, then run your application's full test suite and a static analysis pass. Diff the package's public surface, including config, assets, bindings, and facades, against any version you already reference. Also verify that your Laravel version is pinned correctly against the package's Composer constraints.
- What are alternatives to orchestra/notifications for Laravel notifications?
- Laravel's built-in notification system supports channels such as mail, database, and broadcast and is the default choice for many applications. Orchestra Notifications may be preferable if you specifically need its managed notification UI and Orchestra Platform integration. Evaluate alternatives against your Laravel version, maintenance status, and whether you need a database-backed notification inbox.
- Is orchestra/notifications actively maintained?
- The v6.0.0 release shows willingness to cut a major version for framework compatibility, which is a positive semver signal. However, that release only adds Laravel 8 support, and Laravel 8 is end-of-life, suggesting the reviewed tag is behind current framework generations. Check the latest release date, open issues, pull request activity, and maintainer responsiveness before relying on it.
Weaver
How can I help you explore Laravel packages today?