Weave Code
Support Laravel Package
laravilt/support
A Laravel support package offering reusable helpers, utilities, and foundational components for common development tasks. It streamlines everyday PHP and Laravel workflows, helping keep application code cleaner, more consistent, and easier to maintain.
Foundation package providing base components, utilities, and contracts for all Laravilt packages. Build custom components with reusable traits, utilities, and base classes.
Frequently asked questions about Support
- What is laravilt/support used for?
- laravilt/support is the foundation package for the Laravilt ecosystem. It ships reusable PHP helpers and utilities, base classes and contracts, plus a publishable frontend component layer with Vue and, since v1.1.0, React implementations. Most Laravel apps use it to keep shared backend utilities and UI primitives consistent across projects.
- How do I install laravilt/support with Composer?
- Install it with composer require laravilt/support; the package registers through Laravel package auto-discovery. After that, publish its config and frontend assets with php artisan vendor:publish, choosing the relevant tags. Because v1.1.0 adds a React layer alongside Vue, confirm which publish tag and Vite entry points apply to your stack before wiring components in.
- Does laravilt/support support Laravel 13?
- The package declares Laravel 13 compatibility, but Laravel 13 is not yet a stable release at the time of v1.1.0. That means the constraint is likely validated against a dev branch or a widened constraint rather than a GA framework. Treat Laravel 13 support as forward-looking for evaluation, not as production-proven.
- Does laravilt/support work with Inertia, Vue 3, and React?
- Yes, for Inertia-based frontends it supports both Vue 3 and React 18+ component layers, sharing the same backend helpers. React support arrived in v1.1.0, with foundation fixes later ported back to Vue. Confirm peer dependency ranges against your Inertia and framework versions before assuming drop-in parity.
- Can I use laravilt/support in a Blade or Livewire-only application?
- The PHP-side helpers still work in Blade or Livewire apps, but the Vue and React component layer would go unused. For a Blade/Livewire-only estate the value reduces to the backend utilities, so weigh that against lighter dedicated helper packages.
- What changed with Modal closeOnBackdrop in laravilt/support 1.1.0?
- In v1.1.0 the Modal component now honours closeOnBackdrop, a behavioural change shipped in a minor release. If your app relied on modals always dismissing on backdrop click, that behaviour may differ after upgrading. Grep your Modal usages and audit any that depended on the old dismissal default.
- Do I need to re-publish assets with --force when upgrading laravilt/support?
- You should re-publish frontend assets to pick up the Vue foundation fixes ported in v1.1.0. Whether --force is required depends on your publish tags and whether the assets are already in place. Be aware that forcing an overwrite can clobber local customisations, so check for overrides first.
- What React peer dependencies does laravilt/support require?
- React support likely introduces its own peer dependencies, so check the package's composer.json and package.json for pinned React and Inertia ranges. Validate them against your existing Vite and Inertia/React setup rather than assuming compatibility. The React path is a new surface area in v1.1.0, so verify versions before adopting.
- Is the React support in laravilt/support battle-tested?
- React support is a first contribution from a new contributor, with fixes later ported to the Vue implementation. That sequencing suggests the React path is newer and less battle-tested, and parity between the frameworks is asserted rather than proven. Run your own JS tests against it before relying on it in production.
- How should I test or roll out an upgrade to laravilt/support safely?
- Upgrade on a branch with composer update laravilt/support, re-publish assets, and grep for Modal usages affected by closeOnBackdrop. Rebuild Vite bundles and run your JS test suite, then deploy to staging to manually verify modal open, close, backdrop, and escape behaviour. For React adopters, treat it as a new integration and validate peer dependencies rather than a simple upgrade.
Weaver
How can I help you explore Laravel packages today?