- How do I install christophrumpel/nova-notifications?
- Install it with Composer using composer require christophrumpel/nova-notifications inside your Laravel application. Because it is a Nova tool, you then register it in the tools() array of your app's NovaServiceProvider. Check the repository README for the exact registration snippet used by your Nova version, and run composer why-not christophrumpel/nova-notifications if Composer reports a conflict.
- Does christophrumpel/nova-notifications support Laravel 6?
- Yes. Release 1.0.11 is the version that adds Laravel 6 support, so a Laravel 6 application needs at least that release. Keep in mind that Laravel 6 reached end of security fixes in September 2022, so this support is mainly relevant for legacy applications that have not yet upgraded. If you are running Laravel 8 or newer, that release delivers no functional value for you.
- Which Laravel and Nova versions does nova-notifications require?
- The only confirmed capability change in the available release information is Laravel 6 support in version 1.0.11, so the illuminate/support constraint in composer.json should include ^6.0 if you are on Laravel 6. Laravel 6 itself requires PHP 7.2 or higher, so validate your PHP platform version against the target runtime. Run composer why-not christophrumpel/nova-notifications 1.0.11 against each target app to surface blocking constraints before committing engineering time.
- How does nova-notifications display Laravel notifications inside Nova?
- The package registers a dedicated Nova tool that surfaces Laravel's notifications as a resource inside the Nova dashboard. Admins can browse, read, and manage notifications from a clean inbox without leaving the Nova UI. This is useful when you already send notifications through Laravel's notification system and want visibility into them without building a custom Nova screen.
- Do I need to publish config or configure anything after installing nova-notifications?
- The published evaluation notes explicitly say no data was supplied on config publishing, migrations, routes, or middleware, so verify this in the repository rather than assuming. Inspect the package's composer.json and service provider, and look for a publishable config or migration by running php artisan vendor:publish with the package's provider tag. If it ships migrations, run php artisan migrate after publishing them.
- Can admins mark notifications as read or delete them from the Nova inbox?
- The package is described as letting you browse, read, and manage notifications directly inside Nova, which is the core of the inbox experience. The word manage implies state changes such as reading or removing entries, but the exact set of actions should be confirmed against the README for your installed version. Test the intended admin workflow in a staging environment before relying on it in production.
- Is christophrumpel/nova-notifications safe to run in production?
- It integrates at the framework layer as a standard Laravel and Nova tool, so risk is driven mainly by your Laravel and Nova major versions rather than by application architecture. The main caution is that adding Laravel 6 support in a patch release signals the maintainer is tracking a legacy install base, which is worth weighing when planning long-term maintenance. Treat your first integration as a timeboxed spike rather than a scheduled delivery commitment.
- Why was Laravel 6 support added in a patch release 1.0.11 instead of a minor version?
- The available information does not document the maintainer's reasoning. Framework-version support changes are conventionally minor-version events, and publishing one as a patch means a routine composer update can shift resolved framework constraints without a deliberate decision. Review the 1.0.11 diff to confirm constraints were widened additively rather than by dropping a previously supported framework major, and check the lockfile diff after upgrading.
- How should I test nova-notifications before deploying to production?
- Run composer why-not against each target application to identify constraint conflicts, then bump the package and inspect the lockfile diff to confirm no illuminate/* or symfony/* components moved. Verify whether Laravel 6 is actually exercised in the package's CI matrix, since declared-but-untested support is a common quiet failure mode. Follow up with a short staging test of the Nova inbox flow and the read and manage actions admins will use.
- What are alternatives if nova-notifications does not support my Laravel or Nova version?
- Avoid Composer constraint overrides in production, since they bypass the compatibility guarantees you rely on. A practical alternative is a small custom Nova tool or resource backed by Laravel's built-in database notifications table, which gives you full control over supported framework versions and the actions admins can take. Re-evaluate the package once it publishes a minor release that formally targets your Laravel and Nova majors.