- What is bastinald/laravel-livewire-routes used for?
- It is a small routing convenience layer for Laravel apps that use Livewire full-page components. It lets you register Livewire components as routes through an expressive API, reducing controller and boilerplate wiring. It is best suited to monolithic Laravel, Blade, and Livewire applications with standard routes/web.php usage.
- How do I install bastinald/laravel-livewire-routes?
- Install it with Composer using composer require bastinald/laravel-livewire-routes. Laravel package auto-discovery likely registers the service provider, but confirm discovery and any publish steps in the README. Then define a test route and verify route:list, middleware, and layout rendering before wider adoption.
- Does this package work with Livewire 3 native full-page routing?
- It may coexist, but Livewire 3 already provides native full-page component routing, so this package can be redundant or create conflicting routing patterns. Prefer native routing for new Livewire 3 work unless you have a specific legacy or standardization need. If you adopt it, test route names, middleware, layouts, and Livewire navigation against native behavior.
- Which Laravel, PHP, and Livewire versions are supported?
- The package documentation excerpt does not state supported Laravel, PHP, or Livewire versions, so treat compatibility as unconfirmed. Pin the package and validate with composer why-not and a non-production spike against your exact Laravel, PHP, and Livewire versions. Check route:list, route:cache, and a full-page component request before committing.
- How do I define routes with bastinald/laravel-livewire-routes?
- You define component routes in one place using the package expressive API, which is intended to feel similar to Laravel resource routing. The exact method names and syntax should come from the package README because the provided excerpt does not include code examples. Start with one low-risk route group and compare it with native Livewire full-page routing.
- Does it support middleware, auth, route groups, prefixes, and named routes?
- Because it sits on Laravel routing layer, standard middleware, auth, groups, prefixes, domains, and named routes may be available, but the package behavior is not confirmed in the provided evaluation. Middleware, auth, and layout application are listed as key risks, so verify them with feature tests and route:list. Confirm there are no duplicate route names or middleware gaps before expanding usage.
- Does laravel-livewire-routes work with route:cache?
- It should be tested explicitly with route:cache because route registration packages can introduce closures or patterns that break caching. The evaluation flags route-cache failures as a failure mode, not a guaranteed feature. Run route:cache and route:clear in a staging environment, then smoke-test resolved URLs and Livewire requests.
- How does route model binding work with Livewire component routes?
- Route model binding behavior is not confirmed in the available context and is flagged as something to validate. Test whether route parameters are passed into the Livewire component mount method and whether implicit binding works as expected. If binding is important, compare against native Livewire full-page routing before adopting the package.
- Is bastinald/laravel-livewire-routes maintained and safe for production?
- The package has low stars and likely low maintainer activity, so treat it as a tactical utility rather than a strategic dependency. For production, pin versions, isolate route definitions, add regression tests, and have a fallback to native Livewire routing. There is likely no vendor SLA, so assign internal ownership for upgrades and incident triage.
- What are alternatives to bastinald/laravel-livewire-routes?
- The primary alternative is Livewire 3 native full-page component routing, which avoids an extra dependency. You can also use standard Laravel Route::get calls that point to Livewire component classes, or wrap route registration in your own internal convention. Evaluate alternatives against middleware, layout, route-cache, and route model binding requirements.