Weave Code
Grid Bundle Laravel Package
sylius/grid-bundle
SyliusGridBundle brings advanced, configurable grids to Symfony applications, with filtering, sorting, pagination, and flexible data sources. Part of the Sylius eCommerce stack, it lets you build powerful admin listings and reusable grid definitions with clean, maintainable configuration.
Amazing grids with support of filters and custom fields integrated into Symfony.
Frequently asked questions about Grid Bundle
- Does SyliusGridBundle work with Laravel?
- No. SyliusGridBundle is a Symfony bundle built on Symfony's bundle, dependency injection and compiler pass model, with Twig rendering and Doctrine drivers. There is no Laravel service provider, no Blade views, and no Eloquent driver, so architecture fit in a Laravel application is effectively zero. If your target is Laravel, treat this package as out of scope and look at Laravel-native listing or admin packages instead.
- How do I install SyliusGridBundle in a Symfony application?
- Install it with composer require sylius/grid-bundle, then register the bundle in your bundles configuration. After that you define a grid and render it from a Twig template. A competent Symfony developer can get a first grid on screen in under a day; the real effort is in template overrides and driver choices rather than in installation.
- Which Symfony and PHP versions does SyliusGridBundle support?
- The bundle tracks recent Symfony releases, with Symfony 8.x support landing in version 1.15. Because the supported Symfony and PHP combinations change between minors, check the composer constraints for the exact version you plan to adopt. Confirm that your Symfony and PHP pair is inside the support window before committing, since the project follows Sylius' release needs first.
- What data sources and drivers can SyliusGridBundle use?
- Doctrine ORM and Doctrine DBAL are the paved road and the best-supported options. The bundle also supports custom drivers, which means grids are not implicitly bound to Doctrine entities. That matters if your data lives behind an API, in an Elasticsearch index, or in a read model, because you can implement a driver instead of reshaping your persistence to suit the grid.
- How do you define a grid in SyliusGridBundle?
- In the 1.16 line, grids are invokable, attribute-driven PHP classes marked with #[AsGrid], and #[AsGridMutator] handles cross-cutting customization. This is a cleaner primitive for a large codebase than the legacy YAML and AbstractGrid approach, and it is where new work should target. Pick one strategy up front, because mixing invokable grids and legacy grids across a codebase creates two mental models and doubles the eventual migration.
- Can SyliusGridBundle display data from an API or Elasticsearch instead of a database table?
- Yes, through a custom driver. Doctrine ORM and DBAL are the supported defaults, but any other source is custom code that you own and maintain forever. Budget for that ownership when deciding whether a remote data plane is worth it for a given listing.
- How do I customize the look and templates of a Sylius grid?
- The bundle ships its own Twig templates and a default appearance, so any product with a design system will override them. Template overrides are the most common source of friction during Symfony minor upgrades, due to Twig deprecations and block name changes. Plan a maintained override layer rather than ad-hoc template edits in application code.
- Is SyliusGridBundle production ready and actively maintained?
- It is the grid engine behind Sylius' own admin, so it is battle-tested at production scale for admin-style CRUD listings. The caveat is vendor concentration: roadmap, release timing and bug triage follow Sylius' needs first, and the community is largely the Sylius contributor pool. Also verify actual release cadence and the support window for the minor you adopt, since the recorded latest release metadata looks future-dated relative to normal release history.
- Will upgrading to SyliusGridBundle 1.16 break my existing grids?
- Version 1.16 introduced invokable grids, grid mutators and fluent action builders, while deprecating legacy grids and grid events and moving builder interfaces between packages. Deprecations are non-breaking today, but the removal window is a scheduled future cost. All of that surface movement in a single minor is a reason to plan the migration deliberately rather than drifting between both APIs.
- What are the alternatives to SyliusGridBundle?
- Inside Symfony, the main alternative is writing your own Doctrine-backed listings or using a generic admin generator, which gives you full control but no configurable field, filter and action layer out of the box. SyliusGridBundle's differentiator is its framework-agnostic Grid component plus custom drivers, which let grids compose into existing admin surfaces instead of owning routing. For Laravel applications the alternatives come from the Laravel ecosystem, since this bundle cannot run there at all.
Weaver
How can I help you explore Laravel packages today?