- Is sigmasoft/datatable-bundle a Laravel package or a Symfony bundle?
- The sources conflict, and you must resolve this before anything else. The package description markets it as a Laravel/Eloquent package that renders tables in Blade, while the repository itself has been read as a Symfony bundle that wires Doctrine ORM to DataTables.net through a Twig extension and config/bundles.php registration. Both cannot be true, since bundle is Symfony vocabulary, Eloquent and Doctrine are different ORMs, and Blade and Twig are different template engines. Open composer.json and src/ first; if it is Symfony plus Doctrine, the evaluation ends there for a Laravel application.
- How do I install sigmasoft/datatable-bundle with Composer?
- The usual command is composer require sigmasoft/datatable-bundle, but treat a plain require with caution here. No release tags or cadence have been observed, so the safest route is to vendor or fork the code into a private repository and pin it to a specific commit SHA rather than a version range. Keep it off your main branch until a short spike confirms the framework target, the frontend contract, and the query behavior.
- Does sigmasoft/datatable-bundle support server-side sorting, filtering, and pagination?
- Yes, that is the stated purpose: it takes a query, applies sort, filter, and paginate operations, and returns the JSON envelope a frontend table component consumes. It also advertises search support and per-column callbacks for formatting. The open question is how those operations are applied and whether totals are computed with a count per request, which matters for large tables.
- Which Laravel and PHP versions does sigmasoft/datatable-bundle support?
- No supported version matrix is documented in the overview or the empty README excerpt, so do not assume Laravel 11 or PHP 8.1+ compatibility. The only reliable answer is in composer.json, which will declare either Laravel plus Eloquent or Symfony plus Doctrine along with PHP constraints. Inspect that file before planning an upgrade path, because with no tags you are also depending on a single commit.
- How do I define columns and row actions with the datatable bundle?
- The package exposes a fluent table definition API where you compose columns and row actions in PHP, then point it at a data source. Columns support per-column formatting callbacks and responsive layout options, so rendering is customizable without rewriting view logic. Because the API is small, read the source end to end during your spike to confirm the exact method names rather than relying on the marketing description.
- Does sigmasoft/datatable-bundle work with Eloquent or Doctrine as the data source?
- The description says Eloquent builders, while the repository reading indicates Doctrine ORM. This is the single most important thing to verify, because a Laravel codebase will not get value from a Doctrine-only data layer. If the package is Doctrine-based, it is out of scope for a Laravel shop regardless of how clean the table API looks.
- Is sigmasoft/datatable-bundle safe to expose to client-side sort and filter input?
- Datatable layers accept client-supplied column names, sort keys, filter operators, and sometimes relation paths, which makes server-side whitelisting the highest-severity concern. If those inputs are forwarded to the query builder instead of being validated against an explicit allowlist, the package becomes a SQL injection and cross-tenant data leakage vector. Confirm whether it respects Laravel policies, gates, and global scopes, or whether it bypasses them. This is not a question to delegate.
- Which frontend library does sigmasoft/datatable-bundle integrate with?
- The AJAX-ready endpoints are designed to sit behind a Blade view, and the repository has been described as targeting DataTables.net, which typically implies jQuery. It is not documented as a Livewire or Inertia component, so plan on a custom JavaScript table or a DataTables.net setup rather than a drop-in reactive component. Confirm the exact JSON envelope the endpoint returns before wiring your frontend.
- Does sigmasoft/datatable-bundle have tests, releases, and active maintenance?
- There is no visible adoption evidence: zero stars, zero dependents, no issue history, no Stack Overflow corpus, and no observed release cadence. It is MIT licensed and small enough to audit, which keeps the sandbox install cheap, but the base case should be single-maintainer abandonment and fork-and-own. Budget for an internal security review of the source as a prerequisite, not an optional extra.
- What are good alternatives for server-side data tables in Laravel?
- The mature options are Yajra Laravel DataTables for DataTables.net integration, Livewire-powered tables, or building a thin custom endpoint with your own query whitelist. If this package turns out to be Symfony plus Doctrine, one of those alternatives is your only path. Even if it is Laravel-native, wrap it behind your own DataTableProvider interface so controllers never depend on package classes and a swap stays cheap.