- How do I install cswni/filament-spotlight in a Laravel Filament panel?
- Install it with Composer, pinning the exact version for your first adoption cycle: composer require cswni/filament-spotlight:1.0.0. Then register the plugin object in the Filament panel provider where you want the palette, and run the Filament asset publish or build step so its JavaScript and CSS are available. The package is a low-intrusion integration, so no application domain code needs to change, and removal is a one-line rollback plus composer remove.
- Which Filament, Laravel and PHP versions does filament-spotlight support?
- That constraint set is the first thing to verify, because it is not documented in the package overview provided here. Filament v3 and v4 use materially different plugin and asset-registration APIs, so a constraint mismatch is the most likely cause of an aborted spike. Open the composer.json of the 1.0.0 tag and check the declared Filament, Laravel and PHP requirements against your panel before committing.
- Does Filament Spotlight respect per-resource authorization and multi-tenancy scoping?
- This is the gating question for adoption, not a cosmetic one. A global search surface aggregates records across resources, so if the palette does not delegate to Filament's canGloballySearch() and canView() checks and to global search scoping, users can enumerate record titles they have no right to see. Probe it explicitly: create two roles with disjoint record visibility and confirm results are filtered per user before rolling out to any panel.
- Do I need to publish or build assets for the Spotlight command palette?
- Expect a vendor:publish or filament:assets step, since the palette ships front-end JavaScript and CSS, most likely Alpine and Tailwind based. Confirm that step works inside your CI image and deploy pipeline, not just on a developer machine. If assets are not published, the palette will not render even though the plugin is registered.
- How do I register SpotlightPlugin in a Filament panel provider?
- Add the plugin to the specific panel you want it on, typically by chaining the plugin object inside the panel's plugin() call in your PanelProvider. Because registration is opt-in per panel, you can enable it on one low-traffic internal panel first and leave the rest of your application untouched. Keep the registration line isolated so rollback is a single edit.
- Can I customize the keyboard shortcut and which resources appear in Spotlight?
- The package overview describes resource, page and record navigation, but it does not document configuration keys or a published config file. Check the repository source for published config options before promising a custom shortcut or a restricted resource list to your team. If customization is not exposed, treat the default behaviour as the contract and plan around it.
- Is filament-spotlight production ready, and does it have tests and CI?
- The 1.0.0 tag asserts semver stability intent, but the release notes referenced in this assessment contain only a changelog URL, with no feature summary, breaking-change statement or upgrade guide. There is no evidence yet of test coverage or CI for the search and authorization path. Adopt it as a staged experiment on one panel and reassess at the first upstream minor release to see whether the stability promise holds.
- Is cswni/filament-spotlight actively maintained, and what is the bus factor?
- It is a single-maintainer package with a small audience, and no support commitment is documented. That means low code footprint but a non-zero ongoing cost: you inherit a dependency on an unpredictable release cadence. Keep the integration thin and budget review time at each Filament upgrade so you can drop it if maintenance lapses.
- What are the alternatives to Filament Spotlight for global search?
- Filament already ships built-in global search across resources, and it respects resource authorization and global search scoping by default, which makes it the natural baseline. Evaluate Spotlight against that baseline on the specific gap you need, such as a keyboard-first command palette overlay. If maintainer risk matters more than the palette UX, staying on the built-in search is the safest option.
- How do I roll back or uninstall filament-spotlight if something breaks?
- Removal is a one-line rollback: delete the plugin registration from the panel provider, run composer remove cswni/filament-spotlight, then clear your config and view caches. Because the package does not touch application domain code, no data migration is involved. Document that sequence and announce it to users before you promote the keyboard shortcut.