Weave Code
Grid Bundle Laravel Package
prezent/grid-bundle
prezent/grid-bundle is a Symfony bundle for defining and rendering reusable data grids with configurable columns, filters, sorting, and pagination. It helps PHP applications present tabular data cleanly, integrating with Symfony services and templates for flexible, maintainable grid configurations.
Integrate prezent-grid in Symfony
Frequently asked questions about Grid Bundle
- Can I use prezent/grid-bundle in a Laravel application?
- Not directly. It is a Symfony bundle, so there is no Laravel service provider, no publishable config file, and no Kernel::registerBundles() equivalent to hook into. A Laravel team is better off requiring the underlying prezent-grid library and writing a thin adapter. Installing the bundle through a Symfony-to-Laravel bridge is technically possible but adds dependency surface for what is essentially a wrapper.
- How do I install prezent/grid-bundle?
- In a Symfony application it is a normal Composer require followed by registering the bundle in config/bundles.php. In Laravel there is nothing to register, because Laravel has no bundle concept or Resources/config auto-loading. The practical equivalent is requiring the framework-agnostic prezent-grid library and writing a small service provider yourself.
- Does prezent/grid-bundle support Laravel 10 or 11?
- There is no declared Laravel support and no Laravel-native test coverage, so no version is officially supported. The real constraint to check is the package's php and symfony/* requirements, since those resolve against Laravel's own pinned Symfony transitive dependencies and are the usual cause of Composer conflicts. Run composer why-not before assuming compatibility.
- What is the difference between prezent-grid and prezent/grid-bundle?
- prezent-grid is the framework-agnostic library that defines grids, columns, filters, sorting and pagination. prezent/grid-bundle is only the Symfony wiring around it: dependency-injection extension, service container configuration, and template integration. Nearly all of the reusable value lives in the library, which is the part a Laravel app can actually consume.
- How do I render a prezent grid in a Blade template?
- There is no Blade integration because the bundle targets Symfony's templating layer. The usual approach is to resolve the grid in a controller, render it to an HTML string or array, and pass that into a Blade view or an anonymous Blade component. You will need to build that component yourself, since no Blade directives or slots ship with the package.
- Does prezent-grid support server-side pagination, sorting and filtering?
- The bundle exposes configurable filters, sorting and pagination as grid options, but you must confirm whether the data source paginates at the query level or materializes the full collection first. In-memory dataset construction followed by view-level pagination is a common pattern in grid libraries and a scaling landmine under real data volume. Test with a large dataset before committing.
- Does prezent/grid-bundle work with Eloquent models?
- No. There is no Eloquent integration, no model-to-grid mapping and no query builder hooks. You would write that adapter layer yourself by mapping an Eloquent or query builder instance onto whatever data source contract the grid expects. Expect roughly 100 to 300 lines covering the service provider, config and data source binding.
- Is prezent/grid-bundle actively maintained and safe for production?
- The signals point to a pre-adoption, likely single-maintainer project: very few stars, zero dependents and a low opportunity score. Check the last commit date, the open-issue count and whether the maintainer actually responds before depending on it. The MIT license is the one unambiguous positive, since fork-and-own is legally and practically clean. Either way there is no production evidence base to lean on.
- What Laravel alternatives should I consider instead of prezent/grid-bundle?
- Filament tables, Livewire tables and Yajra Datatables are the usual Laravel-native choices, and all three ship Eloquent integration, Blade rendering and pagination out of the box. This bundle offers a grid definition API but none of the Laravel ergonomics. It only makes sense if the same grid definitions already exist elsewhere in your estate and consistency matters more than ecosystem fit.
- What is the best way to migrate a Symfony grid bundle to Laravel?
- Do not lift-and-shift the bundle. Extract column, formatter and data source definitions into framework-agnostic PHP config or DTOs, bind the underlying grid library through a Laravel service provider with a publishable config file, and expose rendering through a Blade component. Keep those grid definitions as the portable shared artifact and discard the Symfony scaffolding entirely. Add your own tests around the definitions, because no Laravel test coverage is provided.
Weaver
How can I help you explore Laravel packages today?