Nova Button Laravel Package

Getting Started

• Install/update with composer require <vendor>/<package> and run composer update so the 1.0.11 dependency security bumps are reflected in the lockfile.
• Check the package README, CHANGELOG, and service provider first; then look for the new Dusk attribute introduced in 1.0.11 and any related tests/docs.
• First use case: add the package’s Dusk attribute to the relevant Blade component, Livewire component, or test-facing class, then verify the rendered HTML includes the expected Dusk selector and use it from a Laravel Dusk test.

Implementation Patterns

• Prefer the new Dusk attribute over hard-coded selectors in Dusk tests; centralize stable test selectors on components rather than scattering CSS/XPath strings through test files.
• Treat 1.0.11 as a low-risk additive release: security-related dependency bumps plus a new Dusk attribute. Run composer audit and the existing test suite after upgrading.
• Use the Dusk attribute only where browser tests need a stable hook; avoid adding it broadly to production markup unless the package explicitly supports and documents that use.
• In CI, run the dependency update in a clean install, execute Dusk/browser tests, and verify the attribute output in at least one rendered view.
• Publish package config if available, keep environment-specific settings in .env, and cache config only after confirming the new attribute behaves correctly in local and CI environments.

Gotchas and Tips

• The Dusk attribute may depend on Laravel Dusk being installed in dev dependencies; confirm it is not required in production.
• After upgrading, clear caches with php artisan optimize:clear and rebuild frontend assets if the attribute is emitted through compiled Blade/component output.
• Dependency security bumps can change transitive constraints; use composer why-not and composer outdated if the update conflicts with existing packages.
• If the Dusk selector does not appear, inspect the rendered HTML first, then check attribute imports, service provider registration, Blade component compilation, and whether the attribute is conditionally applied outside tests.
• Use the package’s published config and documented extension points before overriding internals; keep customizations small and covered by tests.