Weave Code
Datatablesbundle Laravel Package
sst/datatablesbundle
SST DataTablesBundle integrates jQuery DataTables with Symfony apps, enabling server-side AJAX grids backed by Doctrine. Build sortable, filterable, paginated tables with customizable columns, minimal configuration, and support for admin dashboards and data-heavy CRUD screens.
SST DataTablesBundle provides a Symfony integration for jQuery DataTables, making it easy to build interactive, server-side-powered tables in PHP applications. It handles AJAX requests, pagination, sorting, and searching so you can focus on defining columns and data sources instead of wiring frontend and backend logic.
- Server-side processing for large datasets
- Flexible data source and query integration
- Configurable columns, filters, and search
- Symfony bundle configuration and services
- JSON responses ready for DataTables
Frequently asked questions about Datatablesbundle
- Is sst/datatablesbundle a Laravel package?
- No. sst/datatablesbundle is a Symfony bundle built for Symfony's dependency injection container, kernel, and Doctrine2 entities, not Eloquent models. Running it in Laravel requires a Doctrine ORM bridge plus a Symfony compatibility layer, which is substantial work.
- Can I use sst/datatablesbundle with Eloquent models?
- Not out of the box. The bundle builds queries through Doctrine QueryBuilder and DQL, so Eloquent models are not supported. You would need laravel-doctrine/orm plus adapter code, and the cost/benefit is poor compared with native Laravel datatables packages.
- How do I install sst/datatablesbundle?
- In a Symfony application, install it with Composer, register the bundle in bundles.php or your kernel, configure entity mappings, add a controller that returns the JSON payload, and point DataTables ajax at that route. There is no supported Laravel installation path; adapting it means building a Doctrine and Symfony compatibility layer first.
- Which Laravel versions does it support?
- No Laravel versions are officially supported because this is a Symfony bundle rather than a Laravel package. Check the package constraints for Symfony 5, 6, or 7 and Doctrine ORM alignment in your own application. Treat Laravel compatibility as unsupported and unverified.
- How does server-side processing work in this bundle?
- jQuery DataTables sends parameters such as draw, start, length, search, order, and columns to your endpoint. The bundle parses those into a Doctrine QueryBuilder, applies paging, sorting, and filtering, then returns JSON containing draw, recordsTotal, recordsFiltered, and data. Your front-end DataTables version must match the expected response contract.
- Is it safe from SQL injection and expensive queries?
- Treat it as a real risk until the code has been audited. Sort, filter, and search parameters flow into DQL, so SQL/DQL injection and expensive-query denial of service are the main threat vectors. Allow-list sortable and filterable columns, cap query cost, and review parameter handling before exposing any endpoint.
- Is sst/datatablesbundle actively maintained?
- The signals are weak: zero stars, zero dependents, a single vendor, and a release date of 2026-07-03 that looks anomalous and should be verified. There is no visible community validation or production battle-testing. Plan for owning a fork if upstream goes dormant.
- What is the best Laravel alternative for DataTables?
- For Laravel, yajra/laravel-datatables is the mature, widely used option and works with Eloquent and the query builder. For Symfony, choose a maintained DataTables bundle with recent releases and Doctrine support. Compare maintenance cadence and security review before committing.
- Can I run sst/datatablesbundle in Laravel using laravel-doctrine/orm?
- It is technically possible, but you would also need to bridge Symfony's container and event dispatcher, which is significant bespoke work. With no community validation, that cost is hard to justify. In most cases a rewrite against Eloquent or yajra/laravel-datatables is the more realistic path.
- Is it ready for production with large datasets?
- Server-side processing helps with large datasets by pushing paging, sorting, and filtering to the database. However, expensive sort and filter combinations are a denial-of-service vector, so add indexes, allow-lists, and query limits. With no third-party review or production track record, audit the code before production use.
Weaver
How can I help you explore Laravel packages today?