- Is kgilden/pager-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle, not a Laravel package. It ships no Laravel service provider, no extra.laravel metadata, and no package auto-discovery, so Composer will install it but Laravel will not wire anything up automatically. The only Laravel-transferable part is the pager object itself (current page, offset, limit, total), while the DI extension, Twig extension and templates are Symfony-specific.
- Does kgilden/pager-bundle work with Laravel 10 or 11?
- No, not idiomatically. The bundle targets the Symfony 2.x/3.x line, and its last release (2.0.1) exists only to add Symfony 3.0 compatibility. Laravel pins its own Symfony component versions internally, so installing a bundle built against an EOL Symfony branch is likely to produce Composer conflicts on modern Laravel. If you need pagination in Laravel, use the framework's built-in LengthAwarePaginator instead.
- How do I install kgilden/pager-bundle?
- Install it with Composer using a constraint of ^2.0.1, which is the compatibility patch that adds Symfony 3.0 support. In a Symfony application you then register the bundle in your kernel and configure page size and template options through the bundle's DI extension. In Laravel there is no registration path, so installation alone gives you nothing functional.
- What is the Laravel equivalent of kgilden/pager-bundle?
- Laravel already ships a full pagination subsystem: LengthAwarePaginator for page-number pagination, the paginate() method on query builder and Eloquent results, and Blade pagination views you can publish and customise. That covers the same requirement as this bundle with zero extra dependencies, no translation layer, and first-party maintenance. For most teams the honest answer is to skip this package entirely.
- Can I reuse the pager class from pager-bundle in a Laravel app?
- Possibly, but only as an isolated app-owned utility. The defensible pattern is to lift the small page/offset/limit/total calculation into app/Support/ after a license review, then let Laravel own routing, container binding and rendering via a Blade partial. Do not try to make the bundle itself behave like a Laravel package, because that creates a permanent custom-wiring layer.
- What PHP versions does kgilden/pager-bundle support, and will it run on PHP 8?
- The published releases date from the Symfony 2.x/3.x era, with the last release in 2015, so PHP 8 readiness is unverified. Before committing, check the composer.json platform constraints and run the code against the PHP version you actually deploy. Expect to need compatibility work if your stack is PHP 8.x.
- Is kgilden/pager-bundle still maintained?
- There is effectively no maintenance signal: the package has no stars, no dependents, and its final release is a one-line compatibility patch from 2015. That does not make the pagination logic dangerous, but it does mean you own any bugs, security review and future PHP compatibility yourself. Treat it as abandoned upstream and plan accordingly.
- How do I configure page sizes and templates in pager-bundle?
- The bundle exposes pager services plus a Twig helper, with page size and rendering template configured through the bundle's Symfony DI extension. Documentation is thin, so you will mostly be reading the bundle source to confirm the available options. In a Laravel context there is no config publishing path, so these settings would have to be reimplemented by hand.
- How would I test pagination if I adopt kgilden/pager-bundle?
- Test the pager calculation directly as a unit: given a total and a page size, assert the current page, offset and item slice for the first page, a middle page, the last page and an out-of-range page. If you port the class into app/Support/, those tests live in your own suite and survive dropping the dependency. If you keep the Composer package, add an integration test that pins the resolved Symfony component versions so upgrades fail loudly.
- What are the production risks of depending on kgilden/pager-bundle?
- The main risks are strategic and operational rather than algorithmic. You inherit a permanent translation layer between Symfony bundle conventions and Laravel, plus compatibility debt from an EOL Symfony 3.0 line that will surface as Composer conflicts during framework upgrades. With no maintainer activity since 2015, you also own the security and license review. The lowest-cost route is Laravel's LengthAwarePaginator with a shared Blade partial, or a lift-and-own port of the pager class with no external dependency.