Weave Code
Ux Live Component Laravel Package
symfony/ux-live-component
Build interactive UIs in Symfony with Live Components: stateful Twig components that update via Ajax without writing custom JavaScript. Handle actions, validation, and form binding, with predictable server-side rendering and smooth partial updates.
Live components for Symfony
Frequently asked questions about Ux Live Component
- Can I use Symfony UX Live Component in Laravel without migrating to Symfony?
- No, this package is Symfony-first and requires Symfony 7.4+, Twig, and Stimulus. Laravel projects would need to integrate Symfony’s kernel, replace Blade with Twig, and adapt to Symfony’s dependency injection and routing. This is technically possible but complex and untested in Laravel contexts.
- How does Live Component compare to Laravel Livewire for real-time UIs?
- Live Component mimics Livewire’s declarative reactivity but uses Symfony’s Twig/Stimulus/Mercure stack. Livewire integrates natively with Laravel’s Blade, Eloquent, and Alpine.js, while Live Component requires Symfony’s Doctrine, Twig, and Mercure. The mental model is similar, but implementation details (e.g., templating, validation) differ significantly.
- Will this work with Laravel’s Eloquent ORM, or do I need Doctrine?
- Live Component assumes Doctrine for database interactions. Laravel’s Eloquent would need a custom adapter or serialization layer to bridge with Symfony’s validator and serializer components. This adds complexity and may require rewriting data access logic.
- Can I use Alpine.js or Inertia.js alongside Stimulus in Laravel?
- Stimulus is the primary frontend framework for Live Component, but hybrid approaches (e.g., mixing Alpine.js or Inertia.js) are theoretically possible. However, this would introduce architectural inconsistencies, as Live Component relies on Stimulus controllers for reactivity and Mercure for real-time updates.
- What Laravel version and PHP version does this package support?
- This package does **not** support Laravel directly—it requires Symfony 7.4+ and PHP 8.4+. Laravel projects would need to run Symfony as a sub-application or migrate entirely, which may conflict with Laravel’s PHP version constraints (e.g., Laravel 10 supports PHP 8.1+).
- How do I handle CSRF protection in Laravel if using Symfony’s Live Component?
- Live Component relies on Symfony’s security layer, which may conflict with Laravel’s CSRF middleware. You’d need to either disable Laravel’s CSRF protection for Live Component routes or implement a custom bridge to reconcile both systems. Mercure also introduces its own security considerations for real-time updates.
- Is Mercure required for real-time updates, or can I use Laravel Echo/Pusher?
- Mercure is the default real-time transport for Live Component, but you could theoretically replace it with Laravel Echo or Pusher by extending the package’s `MercureHub` or writing a custom event dispatcher. However, this would require deep integration work and may break compatibility with Symfony’s UX ecosystem.
- How do I integrate Twig templates into a Laravel project using Blade?
- Replacing Blade with Twig in Laravel is non-trivial. You’d need to configure Twig as a service provider, rewrite all Blade templates to Twig syntax, and adapt asset pipelines (e.g., Webpack/Vite) to Symfony’s AssetMapper. This is a significant migration effort with no official Laravel support.
- Are there performance trade-offs for using Live Component in Laravel?
- Yes. Symfony’s component-based rendering and Mercure’s real-time updates may introduce latency compared to Laravel’s optimized Blade/Inertia stack. Additionally, running Symfony alongside Laravel (e.g., via a reverse proxy) could double server resource usage, which may not be ideal for high-traffic applications.
- What are the alternatives to Live Component for real-time UIs in Laravel?
- For Laravel, consider Livewire (native integration), Inertia.js with Vue/React for SPAs, or Alpine.js for lightweight reactivity. If you need Mercure-like functionality, Laravel Echo with Pusher/Ably is a drop-in alternative. Symfony UX Live Component is only viable if you’re fully adopting Symfony or willing to accept high integration risk.
Weaver
How can I help you explore Laravel packages today?