Weave Code
Nova Notification Feed Laravel Package
coreproc/nova-notification-feed
A Laravel Nova package that adds a notification feed to your admin panel, with unread counts, a slide-out feed, and read/unread management. Built for Nova 4.
A Laravel Nova package that adds a notification feed in your Nova app.
Frequently asked questions about Nova Notification Feed
- How do I install coreproc/nova-notification-feed in a Laravel Nova app?
- Require the package with Composer, publish its assets and configuration with artisan vendor:publish, and register it as a tool inside NovaServiceProvider::tools(). You also add the package's trait to the model that authenticates into Nova, typically your User model, so it can resolve its notifications. Run any published migration if the package ships one, then verify the bell renders in the Nova navbar.
- Does coreproc/nova-notification-feed work with Nova 4 and current Laravel versions?
- The package markets itself as built for Nova 4, but its last tagged release dates to March 2020, which predates Nova 4's Vue 3 frontend rewrite. Before committing, confirm the composer.json constraints resolve against your lockfile and smoke-test the navbar Vue components on a current Nova license. Treat the frontend components as the most likely break point rather than assuming a clean install.
- Does this package create its own notifications table or use Laravel's native notifications table?
- It is a presentation layer over Laravel's built-in notifications table: it reads rows your existing notification classes already write rather than introducing a parallel notification platform. Depending on the version, installation may include publishing a migration, so check whether that migration is required and whether it is idempotent against your current schema. This distinction matters because it decides whether swapping the UI later is a frontend change or a data migration.
- How do I show the unread notification count badge in the Nova navbar?
- Once the tool is registered in NovaServiceProvider and the trait is on your authenticating model, the package renders a bell with an unread badge in the Nova navbar that reads from the model's unread notifications relation. The count reflects Laravel's own read/unread state rather than a separate counter table. If the badge does not appear, check tool registration first, then the trait, then asset publishing.
- How does read/unread management work in the slide-out feed?
- The slide-out feed lists notifications and lets the operator mark items as read, which flips Laravel's read_at timestamp on the notification row. Before shipping, confirm whether your product means seen when a feed is opened or acknowledged when a human deliberately acts, because those are different semantics and the package only gives you one flag. If you need explicit acknowledgement, add your own column and UI rather than overloading read_at.
- Does the feed poll for new notifications or use broadcasting, and can I change the interval?
- Historically this kind of Nova bell polls the endpoint at a fixed interval, with the interval typically exposed in the published config file. Check the config for a polling interval key and whether broadcasting is supported at all before you plan around real-time delivery. Also confirm you can disable or lengthen polling during an incident, since every open panel is a recurring request against your application.
- How do I customize how each notification type renders in the feed?
- Out of the box the feed has limited knowledge of your payloads, so complex notification data can render as a raw payload dump instead of readable content. Look for a per-type rendering contract or Vue component hook you can extend; if none exists, budget real work for custom rendering. This is where a one-day install quietly becomes a week, so test with your actual notification classes early.
- Is coreproc/nova-notification-feed still maintained, and what should I use instead?
- The last release was 1.4.0 in March 2020, it has zero Packagist dependents, and its roughly 99 stars reflect historical interest rather than active use. There is no downstream community to surface breakage first and no fork ecosystem to lean on. Because it is MIT licensed you can legally fork and own it, but that turns a dependency into a codebase with a named internal owner; the alternative is writing a small Nova tool yourself over Laravel's notifications table.
- Can I use this package to build an end-user notification inbox or notification center?
- No. This is an internal-operator convenience inside the Nova admin panel, aimed at support and ops staff who already have the panel open. It does not provide channel preference management, digest scheduling, delivery guarantees, mobile parity, per-tenant scoping, or compliance-grade audit such as retention and PII redaction. If a roadmap item says notification center, disambiguate in writing whether you mean an internal observability bell or a customer-facing inbox before citing this package as progress.
- How do I test the feed and avoid multi-tenant leakage?
- Use Laravel's notification fakes plus Nova's testing helpers to assert that notifications are created, scoped to the right user, and flip read state correctly. Scoping flows through the authenticating model's notifications relation, so widening the audience or adding tenant constraints requires explicit query scoping and a leakage test per tenant. Do not assume the package enforces tenancy for you.
Weaver
How can I help you explore Laravel packages today?