← All open source projects

Livewire

livewire/livewire

Livewire is a full-stack framework for Laravel that lets developers build dynamic components without leaving PHP.

Forks 1,736
Author livewire
Language PHP
License MIT
Synced 2026-06-27

In Short

Livewire connects a Laravel component with the browser interface: state lives on the server, users interact with the page, and updates arrive without hand-written JavaScript for every action.

What It Is

Livewire is a Laravel framework for building dynamic UI components in PHP. It is especially useful when a team is strong in Laravel and wants to write less client-side JavaScript.

What Is Inside

The project contains the server side, JavaScript bridge, test infrastructure, and documentation. A component describes state and methods, while Livewire synchronizes it with the DOM.

How People Use It

Livewire is used for forms, filters, tables, modals, small interactive dashboards, and admin interfaces. It works well with Blade, Alpine.js, and Laravel validation.

Example

Livewire Component

The example shows server-side state and a method that changes it after a user action.

Language: PHP
class Counter extends Component
{
    public int $count = 0;

    public function increment(): void
    {
        $this->count++;
    }
}

Strengths

Livewire’s strength is development speed inside Laravel. A lot of interactivity can be built without a separate API layer and large client architecture.

Limits

The limitation is interface class. Complex client applications with heavy local state, offline behavior, or many instant interactions may fit a separate JavaScript approach better.

Project Context

Livewire is maintained in the livewire/livewire repository; its public history starts on 2019-02-12. The primary metadata language is PHP, and the license is MIT.

This context keeps the page grounded in a specific repository: the project has an owner, technical base, license, change history, and real constraints of its ecosystem.

Livewire should be evaluated through a concrete scenario: who will maintain it, where it fits in the existing stack, which updates must be tracked, and what happens if it fails. That view is more useful than installing a project just because it is popular, because open source helps only when its role in the system is clear to the team.