# Livewire: Dynamic Laravel UI Components Without Writing JavaScript > Livewire is a full-stack framework for Laravel that lets PHP developers build reactive, dynamic UI components entirely in PHP, using Alpine.js and a bundled reactivity layer to handle the browser-side updates. **livewire/livewire** — A full-stack framework for Laravel that takes the pain out of building dynamic UIs. - Repository: https://github.com/livewire/livewire - Stars: 23,587 · Forks: 1,753 - Language: PHP - License: MIT - Published: 2026-09-21 · Updated: 2026-09-21 · Language: en - Canonical page: https://hysenlabs.com/projects/livewire-livewire ## What Problem Livewire Solves for Laravel Developers Building interactive UI features in a Laravel application traditionally requires writing PHP to handle server logic and JavaScript to manage the browser side. For straightforward features like live search, paginated tables, or dynamic form validation, the overhead of maintaining two codebases, a REST endpoint and a JavaScript client, is disproportionate to the complexity of the feature itself. Livewire collapses that boundary. A Livewire component is a PHP class with a corresponding Blade template. When a user interacts with the component, Livewire sends the interaction to the server, re-renders the affected portion of the page, and updates the browser using a DOM-diffing algorithm. The developer writes PHP throughout and does not need to build or maintain a separate API layer for component state. The framework targets Laravel developers who want reactive UIs with less front-end tooling. It does not aim to replace JavaScript for every browser task; the bundled Alpine.js handles lightweight client-side interactions that do not need a server round-trip. ## How Livewire Works: PHP Components, Alpine.js, and Vue Reactivity Livewire ships as two packages: a Composer package for the PHP component system and an npm package (`laravel-livewire`) for the browser runtime. The browser bundle, built with esbuild and output to `dist/livewire.js`, includes Alpine.js 3.17.4 and all official Alpine.js plugins (anchor, collapse, csp, focus, intersect, mask, morph, persist, resize, sort) as bundled dependencies. It also includes `@vue/reactivity` for the reactivity primitives that power component state tracking in the browser. When a Livewire component renders, the server sends the full HTML of the component along with a snapshot of its state. The browser runtime intercepts user events declared with Livewire directives, sends a network request to a Livewire endpoint, receives the updated HTML and state snapshot, and uses Alpine.js morph to apply the diff without replacing the entire component. The `nprogress` dependency provides the loading bar visible during round-trips. The `src/` directory in the repository contains the PHP source. The JavaScript source lives in `js/`. Running `npm run build` recompiles the browser bundle from the JavaScript source using the build script in `scripts/build.js`. Two release lines are maintained simultaneously. The `4.x` branch is the default and receives new features. The `3.x` line still receives bug fixes and security patches: v3.8.10 and v4.4.7 were both released on 2026-09-28. ## Setting Up a Livewire Development Environment To work on Livewire itself, clone the repository and run the setup command, which installs both PHP and JavaScript dependencies and configures ChromeDriver for browser-based tests: ```bash git clone git@github.com:livewire/livewire.git && cd livewire composer setup ``` Unit tests run with: ```bash composer test:unit ``` Browser tests run headlessly or in a visible Chrome window: ```bash composer test:browser composer test:browser:headed ``` To run a specific test suite by name, use the filter flag: ```bash composer test:browser -- --filter="SupportCSP" ``` After making changes to the JavaScript source, rebuild the browser bundle: ```bash npm run build ``` For using Livewire in a Laravel application rather than contributing to it, the official documentation at livewire.laravel.com covers installation via Composer and the component API. The README deliberately defers to that documentation rather than duplicating it. ## Versioning, Breaking Changes, and the v4 Migration Version 6 of Livewire introduced significant changes that affected existing component implementations. The repository includes a migration guide (`MIGRATION-5-TO-6.md`) for users upgrading from v5. The current major version is v4, which lives on the `4.x` default branch. The dual-line maintenance (v3 and v4 simultaneously) reflects a pragmatic reality: projects built on v3 are not always ready to migrate, and the Livewire team continues to ship security and compatibility patches for that line. The version numbering jumped significantly between the early Livewire releases and v4; users arriving from older projects should consult the migration guides in the repository before upgrading. Both the `3.x` and `4.x` lines are licensed under the MIT license, meaning there are no restrictions on commercial use, modification, or redistribution. ## Where Livewire Falls Short Livewire's server-round-trip model has a latency floor. Every interaction that requires server-driven state change sends an HTTP request and waits for a response. On high-latency connections or overloaded servers, this becomes noticeable. Components that need to react instantly to rapid user input, such as a real-time text editor with collaborative editing, are a poor fit for this architecture. The bundled Alpine.js handles client-side interactivity well for most cases, but it is not a substitute for a full JavaScript framework when a component needs to manage complex local state, work with WebSockets, or integrate with third-party JavaScript libraries that expect direct DOM control. The repository README does not provide component usage examples. All documentation lives externally at livewire.laravel.com. This means the repository alone gives a contributor or evaluator limited insight into the API surface. New users must read the external docs to understand how to write a component, declare properties, or handle events. ## Livewire vs. Inertia.js Inertia.js is a different approach to the same problem: building Laravel-backed UIs without a traditional API. Where Livewire renders components on the server and syncs the DOM via its own protocol, Inertia.js acts as a bridge between a Laravel backend and a client-side framework, typically Vue.js or React. The server renders JSON responses that Inertia passes to a client-side component tree. The practical difference is ownership of the front end. With Livewire, the component logic stays in PHP and the developer interacts with Alpine.js for small client-side tasks. With Inertia.js, the front-end component lives in Vue or React and the developer writes JavaScript for anything interactive. Livewire is a better fit when the team wants to minimize JavaScript; Inertia.js is a better fit when the team has JavaScript expertise and wants a full component model on the client side. ## Maintenance Status and License Livewire is under active development. The last push was on 2026-09-21, and both the v3 and v4 lines received releases on 2026-09-28. The project was created by Caleb Porzio and is maintained under the MIT license. The MIT license permits use in commercial projects, modification, and redistribution without requiring source disclosure. There are no network-use clauses or copyleft conditions. This makes Livewire straightforward to adopt in any Laravel project, commercial or otherwise, without license review beyond confirming the MIT terms meet your organization's policy. ## Conclusion Livewire is the right fit for Laravel teams who want server-driven interactivity without maintaining a separate JavaScript front end. It works best on projects that already use Laravel's templating and routing, where switching to a full SPA would introduce disproportionate complexity. Teams who need a fully decoupled front end, plan to share API endpoints with mobile clients, or require fine-grained client-side state outside of what Alpine.js offers should look at Inertia.js or a dedicated SPA framework instead. Before starting, check that your Laravel version is compatible with the Livewire 4.x requirements documented at livewire.laravel.com. ## FAQ ### What is Livewire used for in Laravel? Livewire is used to build dynamic, reactive UI components in Laravel applications without writing a separate JavaScript front end. It handles server-side rendering and browser DOM updates through a PHP component model, with Alpine.js bundled for lightweight client-side interactions. ### How do I install Livewire in a Laravel project? The official documentation at livewire.laravel.com covers installation. The README directs users there rather than duplicating the steps. The npm package name is `laravel-livewire`, and the Composer package is `livewire/livewire`. ### How do I use Livewire components in Laravel? The README defers all component usage documentation to livewire.laravel.com. The repository itself is the framework source; component authoring guides, lifecycle hooks, and directive references are in the external documentation. ### How do I use Livewire in Laravel in 2025? Livewire v4 is the current release line. The official documentation at livewire.laravel.com covers component authoring, lifecycle hooks, and directives. Both v3 and v4 received patch releases on 2026-09-28, and the v4.x branch is the default for new projects. ### How do I use Select2 with Livewire? The README does not document Select2 integration directly. The official Livewire documentation at livewire.laravel.com covers integrating third-party JavaScript libraries with Livewire components using Alpine.js lifecycle hooks. ## Sources - [Issues](https://github.com/livewire/livewire/issues) - [License: MIT](https://github.com/livewire/livewire/blob/4.x/LICENSE) - [livewire/livewire on GitHub](https://github.com/livewire/livewire) - [README](https://github.com/livewire/livewire/blob/4.x/README.md) - [Releases](https://github.com/livewire/livewire/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/livewire-livewire