- What does lexicon/nova-action-button-selectors do?
- It is a Laravel Nova presentation-layer asset that lets an action button present a selector dropdown so the user picks an option before the action fires, instead of the action executing immediately on click. It consists of a small PHP registration layer plus a compiled JS/Vue component and adds no backend capability. Its entire value is saving custom Vue work in the Nova admin UI.
- How do I install nova-action-button-selectors in a Laravel Nova application?
- You install it with Composer, register the asset through your Nova service provider or nova.mix.js configuration, then run npm install and a Nova asset build such as npm run dev or npm run prod. Because the upstream repository is archived, most teams should fork it, pin it to their Nova, Laravel and PHP versions, and vendor the component as internal code rather than depending on it directly. Expect an integration spike of roughly one to three days for a mid-level Laravel engineer.
- Which Laravel Nova versions does this package support?
- Compatibility is effectively frozen at whatever Nova version existed when the upstream repository was archived, so there is no supported matrix for Nova 4 or Nova 5. Nova asset APIs, the Nova.booting hooks, mix helpers and the Vue 2 to Vue 3 transition all changed materially after its last commit. Verify it against your exact Nova major and minor version, and budget for porting rather than a drop-in install.
- Is lexicon/nova-action-button-selectors safe to use in production?
- The repository is archived with zero dependents and no maintenance or security response path, so any vulnerability in the transitive npm build chain becomes your team's ticket. The blast radius is contained because the package is admin-panel-only and inherits Nova's authorization, meaning a failure degrades an operator workflow rather than corrupting data or exposing endpoints. Treat it as reference source code or an internal fork with a named owner, not as a live dependency.
- Can I get the same result with native Nova action fields instead of this package?
- Yes, in most cases. Nova actions already support Action::fields() and ActionFields, including Select fields, to collect input in a confirmation modal before the action executes. Confirm whether the button-with-selector is a genuine product requirement rather than an aesthetic preference, because the first-party approach ships supported and avoids owning a forked Vue asset.
- Does this package work with Nova bulk actions?
- The available context does not document bulk behaviour, and bulk selection semantics are exactly where custom Nova action components most often break. There is also no test coverage signal for Nova assets of this vintage, so regressions only surface in manual QA. If you need bulk support, prototype and test it explicitly against your Nova version before committing.
- Do I need to compile JavaScript assets to use this package?
- Yes. It is a Nova asset made of a JS/Vue front-end component plus a thin PHP registration layer, so you need a Node build toolchain and a reproducible npm install and build step in CI/CD. If your UI compilation is ad hoc, that alone is a reason to pause. Confirm your Node version and pipeline can reproducibly compile a Nova asset before adopting.
- Does the package control who can see or run the action buttons?
- No. It is a presentation-layer extension with no data path or auth surface of its own, so it inherits Nova's authorization for the underlying actions. You should still define visibility and authorization rules on the action classes themselves. The component only changes how the action is invoked in the UI.
- What are the alternatives to nova-action-button-selectors?
- The primary alternative is first-party Nova: use Action::fields() with a Select field to gather input in a confirmation modal before execution. You can also build a custom Nova action component or Vue asset in-house, which gives you a supported upgrade path at the cost of development time. Other Nova action UI packages exist, but check their Nova 4 and 5 support and maintenance status before adding another unsupported asset to your upgrade surface.
- Is it worth adopting an archived Nova package like this one?
- Usually no, unless you value it as reference source code for a UX pattern you plan to reimplement or own. The technical evaluation verdict is replace, don't adopt: it is an archived, zero-dependent UI asset with a first-party equivalent. Adopting it also adds a second unsupported asset to your Nova upgrade surface whenever you move to a new Nova major.