- What is laravel-enso/tables used for?
- Laravel Enso Tables is a Bulma-themed, VueJS-powered datatable component for Laravel Enso applications. It provides a fluent backend API for server-side querying, filtering, sorting, pagination, and customizable columns using JSON template setup. It is not a generic Laravel datatable and is meant for Enso's Vue interfaces.
- Is laravel-enso/tables compatible with Laravel 10 or 11?
- Compatibility with current Laravel versions is unproven. The last release was 2018-05-07, which points to Laravel 5.x-era, PHP 7.x-era, Vue 2, and Bulma 0.x assumptions. Treat modern Laravel and PHP support as unconfirmed until a time-boxed compatibility spike proves it.
- Does laravel-enso/tables require Laravel Enso core?
- It is an Enso-ecosystem component, so expect it to rely on Enso core packages, conventions, routes, auth patterns, and frontend build assumptions. The exact coupling should be confirmed from the dependency tree before adoption. Outside an Enso application, architectural fit is low.
- Can I use laravel-enso/tables in a standalone Laravel app?
- Not recommended. The package assumes Laravel Enso, Vue 2, and Bulma, and is not a drop-in generic datatable for standalone Laravel, Vue 3, React, Inertia, or Livewire stacks. For those stacks, use it as a reference implementation rather than a dependency.
- How do I install laravel-enso/tables?
- Install it with Composer as laravel-enso/tables, but success depends on a compatible Enso release and matching Laravel, PHP, Vue, Bulma, Node, and auth middleware versions. Because the last release was in 2018, validate the dependency tree and security advisories first. A small compatibility spike and one representative table prototype are safer than a direct production install.
- What is the JSON template setup in laravel-enso/tables?
- JSON templates define table structure and column configuration for Enso's Vue interfaces, which can reduce bespoke UI work. The provided context does not document the schema contract, so treat it as an undocumented internal contract. If adopted, document the schema and add regression tests before rollout.
- Is laravel-enso/tables actively maintained?
- No. The last release was 2018-05-07, so the package is effectively stale by current standards. Expect to vendor or fork it, maintain CI coverage, track dependency advisories, and patch Laravel/PHP compatibility yourself. MIT licensing is favorable but does not remove the maintenance burden.
- Can laravel-enso/tables handle large datasets?
- Yes, its server-side loading model is the right pattern for large datasets because querying, filtering, sorting, and pagination happen on the backend. Scaling still depends on query design, so require indexed filters, bounded page sizes, query timeouts, N+1 prevention, and export limits. The frontend is unlikely to be the bottleneck.
- What should I check before using laravel-enso/tables in production?
- Run a compatibility spike on your target Laravel, PHP, Vue, Bulma, and Node toolchain versions. Inventory transitive dependencies and known security advisories, then prototype a representative table with real authorization, pagination, search, and expected data volume. Document the JSON template contract, add regression tests, and wrap routes and frontend registration behind an internal adapter so the component remains replaceable.
- What alternatives exist to laravel-enso/tables?
- If you are on Laravel Enso with Vue 2 and Bulma, native Enso integration or a vendored fork may be reasonable. For standalone Laravel or modern Vue 3, React, Inertia, or Livewire applications, choose a maintained datatable component or build a custom server-side table. Isolating any choice behind an adapter preserves a replacement path.