Getting Started

Install via Composer: composer require laravilt/support. Laravel 13 is now supported; on older versions check the package constraints.
Publish config and frontend assets: php artisan vendor:publish --tag=support-config and --tag=support-assets (confirm exact tags in the README). Rebuild your frontend (npm run build) after publishing.
First place to look: the package README for frontend setup, then config/support.php and the published resources/js components (React and Vue variants). The service provider is auto-discovered in typical Laravel apps.
First use case: drop the support modal/widget into an existing Inertia + React or Vue page. With v1.1.0 you can choose React or Vue; start with the Modal component and verify closeOnBackdrop behaves as expected.

Implementation Patterns

Frontend stack selection: Use the React components if your app uses React/Inertia; use the Vue components otherwise. Both are maintained in v1.1.0, but React support is new, so validate against your build tooling.
Modal integration: Pass closeOnBackdrop={false} (React) or the equivalent Vue prop to prevent accidental dismissal. v1.1.0 now honours this prop consistently; use it for destructive or multi-step support flows.
Inertia pages: Import the package’s page components directly into your Inertia routes. Keep package routes separate from app routes to avoid collisions.
Customisation workflow: Publish views/components, then override only what you need. Prefer extending the provided components over copying entire directories.
Laravel 13 compatibility: If upgrading from Laravel 12, test the package’s service provider and any queued jobs/events after the upgrade. The release explicitly adds Laravel 13 support, so dependency constraints should resolve cleanly.

Frontend build step is mandatory: The package ships uncompiled React/Vue sources. If components render empty, check that you published assets and rebuilt.
Modal backdrop behaviour changed: v1.1.0 “honours Modal closeOnBackdrop”. Existing modals that previously closed on backdrop click may now stay open if the prop defaults to false. Audit your modals after upgrading.
React support is fresh: Treat the React foundation as new. Run your test suite and check for hydration or SSR issues, especially if using Inertia SSR.
Clear caches after publishing: php artisan optimize:clear and restart Vite/HMR when config or published assets change.
Debugging: Use browser devtools to confirm the correct component bundle is loaded. If the modal does not appear, verify the package’s service provider is registered and any required middleware is applied.
Extension points: Publish the config to adjust defaults, and publish views/components to override markup. Prefer config overrides for behaviour (e.g. default backdrop closing) and component overrides for presentation.