Weave Code
Wired Tables Laravel Package
defstudio/wired-tables
defstudio/wired-tables is a Laravel Livewire package for building interactive data tables. It helps you render sortable, searchable, and paginated tables with customizable columns and a clean, component-driven API. Designed to keep table logic in PHP while staying easy to extend and style.
Laravel Livewire Datatables
Frequently asked questions about Wired Tables
- How do I install defstudio/wired-tables in a Laravel application?
- Install it with composer require defstudio/wired-tables, then register the package as a plugin with a one-line entry in your Filament PanelProvider. No service contracts, queues, or external services are involved, so setup is quick.
- Does wired-tables work with Laravel Livewire and Filament panels?
- Yes. It is built for Laravel Livewire data tables and plugs into the Filament admin panel via panel plugin registration. It extends table and Livewire behavior at the presentation layer of the admin UI rather than sitting in your domain or data path. Fit is good for teams already standardized on Laravel and Filament, and irrelevant otherwise.
- What PHP, Laravel, Filament, and Livewire versions does wired-tables 2.0.0 support?
- The 2.0.0 release notes declare PHP 8.4 support but do not publish the exact PHP, Laravel, Filament, and Livewire support matrix. Diff composer.json between v0.2.43 and v2.0.0 to see which majors were dropped or added. Verify the result against your stack before upgrading.
- Is upgrading wired-tables from 0.2.43 to 2.0.0 a breaking change?
- Treat it as potentially breaking until you inspect the code. The jump from 0.2.43 to 2.0.0 skips 1.x entirely, and the changelog lists no application-facing changes beyond PHP 8.4 support. There is no documented upgrade guide, so diff src/ for renamed or removed classes, config keys, Blade views, and asset tags.
- Why did wired-tables skip version 1.0.0 and jump straight to 2.0.0?
- The release notes do not explain the skip. It could be a versioning-hygiene reset with no consumer-visible breakage, or it could encode a dropped support matrix for older PHP, Laravel, or Filament majors that is real but unstated. Because 0.x releases never guaranteed semver, treat the jump as potentially breaking until you compare the tags.
- How do I build sortable, searchable, and paginated tables with wired-tables?
- You define table columns and behavior in PHP using the package's component-driven API, then render sortable, searchable, and paginated tables in your Livewire or Filament views. Customizable columns and styling stay easy to extend because the table logic lives in PHP. The goal is to keep table logic out of Blade templates while remaining easy to override.
- How should I test a wired-tables upgrade before it reaches production?
- Create an isolated branch, run your full test suite, then manually smoke-test every admin table that uses the plugin, including column ordering, filters, inline actions, and pagination. Because the package overrides table rendering and Livewire component behavior, a subtle break may not fail the build. Keep the lockfile revert one command away and roll forward only after the smoke pass passes.
- Does wired-tables support PHP 8.4?
- Yes, version 2.0.0 explicitly declares PHP 8.4 support, which is the headline runtime change in the release. Treat that as additive, not as proof that nothing else changed. If you are on PHP 8.3 or below, this release gives you no functional benefit unless you need to stay on a supported branch.
- What are the production risks of using wired-tables in an admin panel?
- Architectural coupling is low and the blast radius is bounded to back-office screens because the package sits at the presentation layer, not in your data path. The real risk is behavioral: a subtle backward-compatibility break manifests as broken admin tables in production rather than as a failed build. That makes it hard to detect without UI coverage, so plan a manual smoke pass over every table that uses the plugin.
- Is defstudio/wired-tables actively maintained, and what alternatives should I consider?
- The release notes do not state a maintainer or backer model, bus factor, or commercial support path, so confirm those details in the repository before standardizing. Ask whether the previous 0.2.x line still receives security fixes and for how long. If your stack is not on Laravel and Filament, native Filament tables or other Livewire datatable packages may fit better.
Weaver
How can I help you explore Laravel packages today?