- How do I install sixlive/nova-text-copy-field in Laravel Nova?
- Install it with Composer: composer require sixlive/nova-text-copy-field. There is no service provider to register, no config file to publish, and no migration to run, so installation ends at the Composer step. Then import the field class in your Nova resource and use TextCopy::make('Column') in the fields method, exactly where you would normally use Text::make(). Because the package ships a pre-compiled Vue bundle in dist/, there is no npm build step on your side.
- Does sixlive/nova-text-copy-field support Nova 4 or Nova 5?
- The last release was March 2019, so it was authored against Nova 3 and its Vue 2 field contract. Nova 4 moved to Vue 3, and the package has not published a compatibility update since. Behaviour on Nova 4 and later ranges from graceful degradation, where you get plain text with no working button, to a broken asset build. Verify it empirically in a dev environment on your exact Nova major before relying on it; if you are on Nova 3, fit is essentially guaranteed.
- How do I add a copy-to-clipboard button to a Laravel Nova field?
- Require the package, then use TextCopy::make('api_token') or a similar column name in your resource's fields method. The field renders the value as text with an adjacent copy button that writes to the browser clipboard on click. It replaces Text::make() in place, so adoption is one line per field and equally reversible.
- Why is the copy button not working in my Nova admin panel?
- The most likely cause is an insecure context. navigator.clipboard is only available over HTTPS or localhost, so on plain HTTP, including internal or staging environments reached by IP, the modern Clipboard API is unavailable. If the component has no execCommand fallback, the button silently does nothing and shows no error. Serve the environment over HTTPS and retest before treating it as a package bug.
- Does the copy field work in Nova index views as well as detail views?
- The package is described as supporting both index and detail views. Index usage requires the Vue component to implement Nova's IndexField contract, and given the package's age you should confirm that in your environment rather than assume it. Test create and edit forms too, so you cover all four rendering contexts before rolling it out.
- Is sixlive/nova-text-copy-field still maintained?
- It has roughly 69 stars, zero dependents, a single maintainer, and no release since March 2019. There is no upstream to escalate to and no realistic expectation of a Nova 5 compatibility patch. Treat it as a disposable dependency: the blast radius is one field in one admin panel, and the fallback is manual text selection. Scope a small native-field reimplementation as the designated exit ramp if it breaks on an upgrade.
- Does the package require a service provider, config file, or migrations?
- No. Architecturally it is one PHP field class extending Laravel\Nova\Fields\Text plus a pre-compiled Vue bundle in dist/. There is no service provider, no publishable config, no routes, no middleware, and no migrations. That makes it a Composer-only install and trivially reversible one line at a time.
- Can I use it to display secrets such as API tokens?
- You can display them, but be clear internally that this is a convenience affordance, not a secrets control. There is no masking, no reveal-on-demand, no audit trail, and no rotation. Anything placed in the field is rendered in the admin panel like any other Nova text value. For sensitive material, pair it with proper access control and treat clipboard exposure as one more consideration.
- What should I do if the package does not work on my Nova version?
- Because the field is a thin subclass of Nova's Text field, reimplementing it natively is small, roughly 100 lines for a custom field with a copy button. Standardize your resources on an internal CopyableValue wrapper now, so a future swap is one file rather than an edit to every resource. That keeps the third-party Vue bundle a swappable detail instead of an architectural commitment.
- How should I test this field before using it in production?
- Install it in a dev environment on your exact Nova major and confirm the field renders with a functional button on index, detail, create, and edit. Click the button on each view and paste somewhere to verify the clipboard write actually happens. Then repeat on HTTPS the way production is served, since insecure staging will mask the real result. That smoke test takes an afternoon, not a project.