- What is iracode-com/filament-notification used for?
- It is a Filament plugin that adds a notification center to Laravel admin panels. It lets you display, manage, and mark notifications as read inside a Filament dashboard or app. Check the README for the exact UI and feature set before adopting it.
- How do I install filament-notification in a Laravel app?
- Install it with Composer using composer require iracode-com/filament-notification. Then register the plugin with your Filament panel provider and follow the README for any config publishing or migration steps. Pin the exact version in composer.lock and try the upgrade in a dev branch first.
- Which Filament versions does this plugin support?
- The supplied context does not state a Filament version matrix explicitly. Treat the package's composer.json require constraints as the source of truth and compare them with your installed Filament major version. Verify in a scratch app before committing if you are on a newer Filament release.
- What Laravel and PHP versions are supported?
- The available release notes do not include a supported Laravel and PHP matrix. Check composer.json and the README, then validate against your pinned runtime, including the lowest PHP version you support. The technical assessment flags this as an open question for the maintainer.
- Do I need to publish config or run migrations after installing?
- A patch release such as 1.4.2 is unlikely to add config or migration stubs, but confirm by diffing the package's published assets between 1.4.1 and 1.4.2. If the plugin relies on Laravel's database notifications, make sure the notifications table exists. Follow the README for the authoritative setup steps.
- Can users mark notifications as read from the admin panel?
- Yes. The package's stated purpose includes displaying, managing, and marking notifications as read in the Filament admin panel. Confirm the exact UX, such as per-item and bulk read actions, in the README or a staging build.
- Is v1.4.2 safe to upgrade to in production?
- The assessment rates risk as low-to-moderate: the patch contains unspecified bug fixes plus a functional update to user notifications. Because notification surfaces are user-visible and often weakly covered by tests, obtain the changelog or diff and exercise each notification path in staging before deploying. Constrain to ^1.4 and pin the exact version.
- Will upgrading change my existing notifications or queue behavior?
- The 1.4.2 note mentions an update to user notifications, which could affect content, channels, recipients, or dispatch timing. Review the diff and confirm whether the change is opt-in. If notifications are queued, test a rolling deploy where jobs serialized under 1.4.1 are processed by 1.4.2 workers.
- How should I test the notification center before release?
- Run your full test suite plus any notification-specific tests, then manually exercise each notification path in staging across all channels, both queued and synchronous. Inspect rendered output and read and unread state changes. Static analysis alone will not prove parity for notification changes.
- Is filament-notification actively maintained, and what alternatives should I consider?
- The supplied data does not include maintainer history or release cadence, so treat maintenance activity as unverified and ask the maintainer directly. As alternatives, evaluate Filament's built-in database notifications or a custom notification page against this plugin. Compare feature coverage, Laravel and Filament version support, and recent release activity before adopting.