Weave Code
Inertiajs Tables Laravel Query Builder Laravel Package
adesin-fr/inertiajs-tables-laravel-query-builder
Build interactive Inertia.js data tables in Laravel with Laravel Query Builder. Supports server-side search, filters, sorting, and pagination, making it easy to create fast, reusable tables for admin panels and apps.
Inertia.js Tables for Laravel Query Builder
Frequently asked questions about Inertiajs Tables Laravel Query Builder
- What is adesin-fr/inertiajs-tables-laravel-query-builder used for?
- It is a Laravel Composer package for building interactive Inertia.js data tables backed by Laravel Query Builder. It centralizes server-side search, filtering, sorting, and pagination so admin panels and apps can reuse table behavior instead of writing bespoke query-string handling. It fits best when your app already uses Laravel, Inertia.js, and a supported frontend adapter such as Vue or React.
- How do I install inertiajs-tables-laravel-query-builder in a Laravel app?
- Install the PHP package with Composer and add the matching frontend adapter/assets for your Inertia stack. Then update your controller to return Query Builder results in the shape the table component expects and render the table from your Inertia page component. Check the repository for the exact Composer command, adapter package name, and component registration steps because public documentation is limited.
- Which Laravel, PHP, Inertia, and frontend versions are supported?
- The package targets Laravel applications using Inertia.js and Laravel Query Builder, but the provided information does not include a definitive compatibility matrix. Before adopting it, verify composer.json peer constraints and CI coverage against your Laravel 10, 11, or 12 version, PHP version, Inertia v1 or v2, and frontend framework version. Compatibility risk is medium because Inertia protocol changes and Laravel major releases can break integrations.
- Does it support Vue 3, React, and Svelte?
- The package is described as supporting Inertia.js frontend adapters, and the evaluation references Vue, React, and Svelte as possible targets. However, official adapter support and whether each adapter is maintained at the same cadence as the PHP side should be confirmed in the repository. Do not assume parity across frameworks until you check the published frontend packages and examples.
- How does server-side search, filtering, sorting, and pagination work?
- The package sits between spatie/laravel-query-builder on the server and Inertia page components on the client. Your controller applies allowlisted Query Builder filters and sorts, returns paginated results, and the Inertia table component renders rows while preserving table state through query strings. Confirm how pagination is represented, such as length-aware or cursor pagination, and whether query strings persist across Inertia visits.
- Do I need spatie/laravel-query-builder to use this package?
- Yes, the package is designed around spatie/laravel-query-builder for server-side filtering, sorting, and pagination. You should already be comfortable defining allowed filters and sorts in Laravel Query Builder before adding the Inertia table layer. If your app does not use Laravel Query Builder, adopting this package likely adds unnecessary coupling.
- Is it safe to pass request filters and sorts directly to Laravel Query Builder?
- No, you should explicitly allowlist filters and sorts server-side rather than passing arbitrary request parameters through to Query Builder. The package may encourage a secure pattern, but application code remains responsible for preventing unintended columns or expensive queries. Treat filter and sort allowlisting as a required integration step, especially for customer-facing tables.
- Can I use it with Inertia SSR, and are there hydration issues?
- Inertia SSR is not confirmed in the provided information, so treat it as a verification item before production use. The evaluation flags low-to-medium SSR and hydration risk and recommends checking that table components render deterministically and pagination state hydrates correctly. Test SSR and client-side navigation with your chosen frontend adapter if server-side rendering matters to your app.
- Is this package production-ready given its low star count and single maintainer?
- It can be reasonable for internal admin surfaces if you accept maintainer and abandonment risk. The evaluation highlights a low star count, likely single-maintainer bus factor, limited public documentation, and medium API stability risk. The MIT license substantially mitigates abandonment because you can fork and patch internally, but wrap it behind your own component abstraction to limit future customization constraints.
- What are alternatives if I need a more mature Laravel/Inertia table solution?
- If maturity is the priority, compare against building your own thin Inertia table layer on top of spatie/laravel-query-builder or adopting a more established table package with active maintenance and documented Laravel and Inertia compatibility. This package is a product-surface dependency rather than infrastructure, so evaluate release cadence, issue responsiveness, adapter support, and production references. Avoid it for API-only backends, Livewire admin panels, or highly customized virtualized or inline-editing grids.
Weaver
How can I help you explore Laravel packages today?