Getting Started

Install the release with composer require <vendor>/<package>:^1.0 (or update with composer update <vendor>/<package>), then run any required publish command for config/assets.
Start with the package README section covering copyable support added in 1.0.3, plus the service provider registration and any frontend asset build/publish steps.
First use case: make a single displayed value copyable in your admin UI or Blade view — for example an order reference, API token, or email address — and verify the copied value in the browser clipboard.
Confirm the package is loaded in the correct Laravel context (web middleware, Livewire/Filament panel, or Blade component) before rolling copyable behaviour out more broadly.

Implementation Patterns

Apply copyable support at the presentation layer: columns, table entries, detail views, or form fields where users routinely copy identifiers or secrets.
Use it for high-friction values such as invoice numbers, UUIDs, webhook URLs, API keys, and support ticket references; avoid making every field copyable, as it adds visual noise.
Centralise usage through base resources, shared Blade components, or table/configuration macros so copyable behaviour is consistent across the application.
Combine copyable values with existing formatting, tooltips, and permission checks; for sensitive values, gate copyable behaviour behind the same authorisation as viewing.
For Livewire/Filament-style components, attach copyable behaviour declaratively where the package exposes it, and keep custom JavaScript handlers as a fallback only when the built-in support is insufficient.
Add a browser-level test (Dusk or similar) for at least one copyable value to catch clipboard and asset-loading regressions.

Clipboard access generally requires a secure context (HTTPS or localhost). Test on a realistic origin; plain HTTP staging environments may silently fail.
Check interactions with existing click behaviour, row actions, sorting, and links. A copyable control should not trigger navigation or selection accidentally.
Verify exactly what gets copied. Formatters, truncation, and display-only decorators can mean the visible text differs from the clipboard payload.
Clear caches and republish frontend assets after upgrading to 1.0.3; stale compiled assets are a common reason new UI features appear broken.
Inspect the browser console first when copying fails, then confirm the package’s JS is present on the page and the relevant config/feature flag is enabled.
Use the package’s extension points — custom copy handler, view overrides, or published config — before forking behaviour. Keep overrides minimal so future 1.x releases remain easy to adopt.
Since copyable support is the only change in 1.0.3, treat it as additive: no migration is expected, but smoke-test existing table/detail views after upgrading.