Weave Code
Nova Busy Resource Field Laravel Package
the-3labs-team/nova-busy-resource-field
A Laravel Nova field that displays whether a resource is currently busy, helping teams spot records in use and avoid conflicting edits. Add it to your Nova resource definitions for a clear at-a-glance status indicator.
A Laravel Nova field.
Frequently asked questions about Nova Busy Resource Field
- What does the-3labs-team/nova-busy-resource-field actually do?
- It is a Laravel Nova field that lets you mark a resource record as busy and display that status inside the Nova admin panel, so you can see which user is currently occupying a record. It integrates with Nova forms and index views to show at-a-glance busy states, helping teams avoid conflicting edits and accidental changes. You add it to any Nova resource the same way you add other Nova fields.
- How do I install nova-busy-resource-field with Composer?
- Require the package with Composer using the the-3labs-team/nova-busy-resource-field constraint ^2.1, then run composer update scoped to the package. Laravel package auto-discovery handles service provider registration, and config and asset publishing are available if you need them. If your workflow mirrors the package frontend assets locally, rebuild them after upgrading.
- Which Laravel and PHP versions does v2.1 support?
- Version 2.1 targets Laravel 12 and PHP 8.3 or 8.4. The framework and PHP floor were raised in this release, so applications still on Laravel 10 or 11, or on PHP 8.2, cannot take the upgrade until they migrate. Confirm your platform version before bumping the Composer constraint.
- Is upgrading to ^2.1 a breaking change from 2.0?
- At the code level it is non-breaking: there are no public API changes, no new runtime configuration keys and no announced deprecations. However, raising the Laravel and PHP floor is a breaking change for any consumer still on older stacks. Treat it as a platform-gated upgrade rather than a drop-in patch, and check whether the 2.0.x line will keep receiving fixes.
- Do I need to rebuild frontend assets after upgrading this Nova field?
- Only if your workflow mirrors or vendors the package frontend assets locally instead of consuming them from vendor. The release notes explicitly ask teams that mirror assets to rebuild the package frontend assets because the shipped build output changed with the toolchain refresh. Skipping that step is the most likely real-world defect source, since you can silently run a stale bundle. If you consume assets from vendor, there is no rebuild step.
- Does v2.1 add new config keys or .env changes?
- No. This release adds no new runtime configuration keys and no environment variable changes, so there is no config-cache invalidation work to plan. The integration surface is unchanged: service provider registration, config publishing and asset publishing all work as before. That makes the upgrade low risk for teams with strict configuration governance.
- How do I add the busy status field to a Nova resource?
- Add the field to your resource fields method just like any other Nova field, and it renders in Nova forms and index views. The index view gives an at-a-glance indication of which records are currently busy and who is occupying them. Keep the field definition consistent across resources so the busy state is easy to scan in the admin panel.
- Can I use this package on Laravel 11 or PHP 8.2?
- Not with v2.1, which requires Laravel 12 and PHP 8.3 or 8.4. Older stacks are effectively stranded on the 2.0.x line, so confirm with the maintainer whether 2.0.x still receives security patches and for how long. If you cannot move the framework yet, this package upgrade is a downstream task of your Laravel migration, not an independent workstream.
- What should I check before rolling this out to production?
- Run your application test suite plus a smoke pass on the Nova surfaces where the field renders, mainly forms and index views. Inspect the lockfile diff rather than accepting it wholesale, since this maintenance wave bundled dependency refreshes that can surface indirect constraint conflicts your package CI would not catch. If you mirror assets, verify published output, hashes, manifests and cache-busting entries match the new build. Nothing in the release adds a new runtime service, queue, cache or storage dependency, so deployment topology is unchanged.
- What are my alternatives if I cannot upgrade to Laravel 12 yet?
- You can stay on the 2.0.x line while it remains supported, or implement occupancy tracking yourself with cache locks or a locked-by column rendered through Nova built-in fields. Nova has no native busy or occupancy indicator, which is the gap this package fills. Before committing to the older line, ask the maintainer about the support window, security patch policy and any published end-of-life timeline.
Weaver
How can I help you explore Laravel packages today?