Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message
Datagrid Bundle

Datagrid Bundle Laravel Package

palabs/datagrid-bundle

Palabs Datagrid Bundle provides configurable data grids for PHP applications, helping render sortable, filterable tables from existing data sources with less boilerplate. Suitable for admin panels and reporting views, though documentation and community adoption are currently limited.

View on GitHub
Deep Wiki
Context7

A Symfony bundle to work with datagrids. Any input data, any export format, any data types.

Frequently asked questions about Datagrid Bundle
Is palabs/datagrid-bundle compatible with Laravel?
No, not out of the box. It is a Symfony bundle built around Symfony's kernel, dependency injection extension, configuration tree, and Twig templates, none of which Laravel provides. Using it in a Laravel app would require either embedding Symfony's container or extracting the core classes, which is a significant architectural compromise.
Can I install a Symfony bundle in a Laravel application?
Not directly in any supported way. Laravel uses service providers, facades, config files, and Blade rather than Symfony bundles, so the bundle's wiring contracts have no equivalent. At minimum you would be writing and maintaining custom glue code.
What PHP and Symfony versions does palabs/datagrid-bundle require?
Check the composer.json constraints before anything else. Given the package's age and low adoption, it is likely pinned to older PHP and Symfony ranges that will not resolve against Laravel 10 or 11 on PHP 8.1+. If so, integration is blocked until the constraint files are rewritten.
Does palabs/datagrid-bundle work with Laravel Eloquent?
There is no indication of Eloquent support; the package is designed around Symfony conventions for data sources and rendering. Laravel developers would need adapters for request handling and the view layer. For Eloquent-native grids, Spatie Query Builder or yajra/laravel-datatables are better fits.
How do I render palabs/datagrid-bundle grids in Blade?
You cannot without a rewrite. The bundle ships Twig templates, so using it in Laravel means either adding the Twig bridge or rewriting the views as Blade components. Both approaches discard the package's main value, which is its pre-built view layer.
Is palabs/datagrid-bundle safe for production use?
The risk is high and asymmetric. Datagrids translate user-controlled filter, sort, and page parameters into SQL, so parameter binding and column allow-listing must be provably correct, and there is no evidence of an active maintainer or test suite to guarantee that. You should not assume those safeguards are present in an abandoned package.
Is palabs/datagrid-bundle actively maintained?
Adoption and documentation are limited, and there is no evidence of active maintenance, a community, or a test suite. That means no one to patch CVEs and no upstream path for PHP major-version upgrades. Treat it as unmaintained until proven otherwise.
What are the best Laravel alternatives to palabs/datagrid-bundle?
Spatie Query Builder for filter and sort allow-listing on Eloquent, yajra/laravel-datatables for server-side Ajax tables, and Livewire or Filament tables for interactive UI. A thin in-house abstraction over Eloquent scopes and Blade components also works well. All are maintained, documented, and PHP 8-ready.
Can I fork or extract palabs/datagrid-bundle for Laravel?
Possibly, but budget for the work. A full fork means rewriting composer.json constraints, replacing Twig with Blade, adding a service provider, adapting Symfony Request handling, and adding tests, and then you own it indefinitely. Check the license first to confirm a private fork with modification is permitted.
How much work is it to integrate palabs/datagrid-bundle into a Laravel app?
More than it is worth. You face three concrete blockers: Composer constraints likely pinned to older PHP and Symfony versions, a Twig rendering layer that needs a Blade rewrite, and request handling tied to Symfony's Request rather than Illuminate\Http\Request. A native Laravel datagrid of this scope is typically days of work, not weeks.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
dbravoan/dbcms-admin-theme-dbcms
dbravoan/dbcms-theme-db-cyber
dbravoan/dbcms-blocks-basic
dbravoan/dbcms-module-content-audit
dbravoan/dbcms-module-ai-assistant
paygate-to/paygate-php
padosoft/askmydocs-connector-base
defstudio/supercharged-carbon
bernskioldmedia/laravel-matomo
bernskioldmedia/laravel-harvest
bernskiold/laravel-data-scrubber
bernskiold/laravel-currency-converter
bernskiold/laravel-campaign-monitor
bernskioldmedia/laravel-autotranslate
siberfx/telegram-bot
roy-sandip/laravel-view-extended
gregsphotography/site-builder-core
roy-sandip/laravel-view
anodyne/blade-fluentui-icons
webx-ui/module-catalog-collections