- How do I install sietse85/nova-button in a Laravel Nova application?
- Install it with Composer using composer require sietse85/nova-button, then add the button field to a Nova resource's fields method. Pin an explicit release tag in production so Nova and the package upgrade together deliberately. There are no migrations, published config files, or manual service provider registrations required beyond Composer auto-discovery.
- Does sietse85/nova-button support Laravel Nova 4 and Nova 5?
- The package documents Laravel Nova 4+ as its support floor, so Nova 4 and later are the expected target. Treat that as an asserted compatibility range rather than a tested guarantee, because Nova's internal Vue component API is not a public stability contract. Pin the package and Nova versions together and upgrade them as a pair.
- How do I trigger a Nova action from a button instead of using the actions dropdown?
- Configure the field to reference the Nova action you want to run, and the button renders on the resource index or detail screen as a one-click trigger. Keep this pattern to single-record, click-to-run affordances; bulk or queued operations belong in Nova Actions. The action itself must still enforce authorization, CSRF, and your policies on the server.
- Can a nova-button open a URL or external link in a new tab?
- Yes, the field can be configured to navigate to a URL instead of dispatching a Nova action. That makes it useful for open-in-vendor, documentation, or internal admin links directly from a resource page. Treat the link target like any other privileged admin surface and avoid exposing sensitive URLs to users who should not see them.
- How do I add a confirmation prompt before a destructive button action runs?
- The package supports an optional confirmation prompt through its fluent configuration, typically via a confirm method on the field. Use it for destructive or irreversible operations to prevent accidental clicks in the Nova UI. Remember that confirmation is client-side UX hygiene, not a security control, so the backing route or action must independently enforce authorization.
- How can I hide a nova-button from users who are not authorized?
- Use Nova's canSee authorization callback on the field so the button is only rendered for permitted users. This controls visibility in the UI, but it does not secure the underlying endpoint. Every action or route the button calls must separately enforce Nova's guard, CSRF protection, and your application policies.
- Can I customize the button label, icon, color, and style?
- Yes, the field exposes configurable labels, icons, colors, and button styles so the control fits the surrounding Nova UI. That flexibility is the main reason to use the package instead of hand-writing a Vue component for each resource. Keep the configuration consistent across resources so operators recognize the same affordance everywhere.
- Does sietse85/nova-button work on both index and detail views?
- The package is designed to render inline on Nova resource index and detail screens. The same field configuration can place a button where operators already work rather than sending them into a separate tool. It is intended for single-record affordances, not bulk selections or multi-step forms.
- Is sietse85/nova-button safe to use in production?
- The package is a view-layer Nova field with a prebuilt Vue component in dist, so treat that JavaScript as a supply-chain review item because it runs inside your highest-privilege authenticated admin UI. Rebuild from source in CI and diff the output, or have someone review the compiled bundle. Also budget separately for authorization, idempotency, and audit trails behind each button, since the package makes the button visible but does not provide those backend controls.
- How does nova-button compare with Nova Actions or building a custom Nova Tool?
- Use nova-button for narrow, single-record, click-to-run affordances such as approve, resend, sync, or open-in-vendor. Use Nova Actions for bulk or multi-record operations, and use a Nova Tool when the workflow needs a form, wizard, or branching logic. Building a custom Vue component is the more expensive alternative for the same simple button outcome, which is why a thin internal wrapper class around the package is a sensible exit-cost hedge.