Weave Code
Datatable Bundle Laravel Package
netteam/datatable-bundle
Netteam Datatable Bundle is a PHP package for building sortable, paginated, filterable data tables. Configure columns, actions, and server-side data sources to render reusable grids with minimal setup in your application.
At a glance
Frequently asked questions about Datatable Bundle
- Is netteam/datatable-bundle compatible with Laravel?
- No. Despite being described as a general PHP package, netteam/datatable-bundle is a Symfony bundle built around Symfony's dependency injection container, EventDispatcher, Twig rendering, and likely Doctrine persistence. Laravel uses service providers, Blade, Eloquent, and its own paginator contracts, and none of those are equivalent to the Symfony wiring this package depends on. Treat it as Symfony-only unless you fork it and re-wrap the core logic yourself.
- How do I install netteam/datatable-bundle in a Laravel project?
- A plain composer require is unlikely to install cleanly, and even if it does, the bundle expects registration in a Symfony kernel rather than a Laravel service provider, so nothing will boot. Its composer.json almost certainly pins legacy PHP and Symfony component ranges that clash with the Symfony 6/7 components shipped by Laravel 10 and 11. Forcing the install with --ignore-platform-reqs is not acceptable for a production application. Run a short compatibility spike in a throwaway branch before committing any time to it.
- Is netteam/datatable-bundle a Symfony bundle or a Laravel package?
- It is a Symfony bundle. The Bundle naming suffix, the service container registration, and the Twig templating conventions all point to Symfony, not Laravel. This distinction is the single most important thing to understand before evaluating it, because it changes the question from how do I install this to how much of it would I have to rewrite.
- Does netteam/datatable-bundle work with Blade and Eloquent?
- No. Rendering is Twig-based and data access is likely Doctrine-backed, while Laravel expects Blade views and Eloquent query builders or repositories. Bridging means replacing both the view layer and the persistence layer, which is where most of the bundle's actual wiring lives. What might be reusable is the abstract column, filter, sort, and paginate pipeline, and only if that code is container-agnostic.
- What PHP and Symfony versions does netteam/datatable-bundle require?
- You have to check composer.json directly, because the README does not document supported version ranges. Given the zero-star, zero-dependent status and the legacy bundle structure, expect constraints from older PHP and Symfony 2.x/3.x eras. Those ranges are the first thing to verify, since they determine whether the package can even coexist with a modern Laravel install on PHP 8.1 or newer.
- Is netteam/datatable-bundle safe to use in production?
- The signals are poor: zero stars, zero dependents, a composite score around 0.1, and no visible issue triage or release activity. That means no community support and no upstream security patches, so every bug and CVE becomes your team's responsibility. If you adopt it, budget for maintaining a fork indefinitely and document it heavily, because onboarding will otherwise require code archaeology with a bus factor of one.
- Does netteam/datatable-bundle support server-side data sources, sorting, and pagination?
- Yes, that is its stated purpose: defining columns and actions over a server-side data source with sorting, filtering, and paging. However, the paging and request handling are tied to Symfony's request and pager primitives rather than Laravel's LengthAwarePaginator, and the filter and sort layer is unlikely to be decoupled from the container. The pipeline concept is what is worth porting, not the implementation.
- What license does netteam/datatable-bundle use and are there dependency CVE risks?
- The license is not stated in the README excerpt, so confirm it in composer.json before any code reuse, especially if you plan to vendor classes into a closed-source internal package. Then review transitive dependencies for known CVEs, since unmaintained bundles often pull in old Symfony components with published advisories. This review should happen before the decision gate on port versus replace, not after.
- What are the best Laravel alternatives to netteam/datatable-bundle?
- For server-side sortable and paginated tables in Laravel, the common choices are Yajra DataTables, Filament tables, and Livewire-based datatable components. If you only need a thin column, filter, sort, and paginate pipeline, a small Eloquent and Blade implementation is often less work than adapting a foreign abstraction. All of these avoid the container, templating, persistence, and pagination mismatches this bundle creates.
- Can I fork or vendor netteam/datatable-bundle into a Laravel service provider?
- Only if a time-boxed spike shows the core datatable classes are genuinely container-agnostic and not tied to HttpFoundation or Symfony's pager. If they are decoupled, vendor those classes into an internal package with tests, wrap them in a Laravel service provider, and accept full ownership of the fork. If they are coupled, which is more likely, abandon adoption and port the concepts to a Laravel-native implementation instead.
Weaver
How can I help you explore Laravel packages today?