- Is pierres/datatables-api-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle, not a Laravel package. It wraps the framework-agnostic pierres/datatables-api core with Symfony DI registration, a configuration tree, and kernel wiring. In a Laravel codebase, only the core is portable; the bundle layer is dead weight and should not be installed.
- How do I install and configure pierres/datatables-api-bundle in a Laravel app?
- You should not install the bundle itself in Laravel. Pull the pierres/datatables-api core, write a Laravel service provider, bridge Illuminate\Http\Request to PSR-7 using Nyholm or Symfony's PSR bridge, and replace the bundle's config-driven column definitions with Laravel config plus FormRequest validation. The Eloquent query adapter is the main piece you must build and own.
- Does pierres/datatables-api-bundle support Laravel 10 or 11 and PHP 8.2 or 8.3?
- There is no verified Laravel 10/11 or PHP 8.2/8.3 support. The package has a Symfony 3/4-era lineage and an inactive upstream, so expect compatibility gaps. Run composer why-not against your PHP and Laravel constraints and plan to fork with widened constraints and a pinned PSR version.
- Does pierres/datatables-api-bundle work with Eloquent, or is it Doctrine-only?
- The core is Doctrine-oriented and assumes Doctrine ORM/DBAL semantics. An Eloquent or Query Builder implementation must be written and owned internally. Define a DataTablesQuery interface so Doctrine and Eloquent implementations are swappable, then implement column whitelisting and filtering on top.
- How does server-side processing handle pagination, ordering, and search?
- The core parses DataTables' draw, start, length, order, search, and per-column filter parameters and emits the expected JSON envelope. It is middleware that translates the request contract rather than a query builder, so your adapter must apply those values safely to the database query. Pay close attention to recordsTotal versus recordsFiltered semantics, which are a classic source of silent pagination bugs.
- Is pierres/datatables-api-bundle safe to use in production?
- It carries high technical risk: zero stars, zero dependents, an inactive upstream, and a Symfony 3/4-era lineage. DataTables server-side processing maps client-supplied column, order, and search parameters directly onto query construction, so the adapter must whitelist columns and validate operators or it becomes an injection surface. There is also supply-chain risk in adopting unmaintained code with no dependents.
- Is pierres/datatables-api-bundle actively maintained and tested?
- Assume it is not. The package shows zero stars, zero dependents, and a package score of 0, and it does not appear to have verified test coverage on the query-building path. Check the last commit date, open-issue count, and license before relying on it, and do not expect PHP 8.2/8.3 or Laravel 10/11 fixes upstream.
- What is the best alternative to pierres/datatables-api-bundle for Laravel?
- yajra/laravel-datatables is the practical alternative: it is Laravel-native, maintained, and widely adopted. Run it against the same endpoint in parallel during your spike. If it meets your requirements, the build-versus-buy answer is buy, and an unmaintained bundle with no dependents does not justify owning a fork.
- Can I use pierres/datatables-api-bundle with DataTables.js 2.x?
- Only after verifying the request contract. The DataTables 1.10 and 2.x request formats differ enough to break parsing, and that breakage is often silent in the UI. Confirm major version alignment and test the JSON envelope against real requests before committing to the integration.
- How much engineering effort does a Laravel integration actually take?
- Budget two to three engineer-weeks for a production-grade, tested Eloquent adapter, service provider, and PSR-7 bridge. Start with a timeboxed spike that runs the core middleware against a PSR-7 request inside a Laravel test and confirms correct parsing and JSON output. The bundle contributes almost none of that effort; the query adapter and validation work are yours to own.