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
Pager Bundle

Pager Bundle Laravel Package

symfony-twig/pager-bundle

symfony-twig/pager-bundle is a Symfony bundle for adding Twig-powered pagination to your projects. It provides reusable pager rendering and page navigation controls, helping you display paginated lists with configurable ranges and simple template integration.

View on GitHub
Deep Wiki
Context7

Paginator Bundle for Symfony >=3 and twig >=2.0.0.

Frequently asked questions about Pager Bundle
Can I use symfony-twig/pager-bundle in a Laravel application?
No. It is a Symfony bundle (type symfony-bundle) that depends on Symfony's HTTP kernel, bundle registration, and service container, none of which exist in Laravel. Laravel has no bundle system and uses Blade by default, so there is no supported integration path. Use Laravel's built-in LengthAwarePaginator instead.
How do I install symfony-twig/pager-bundle?
Install it with Composer as symfony-twig/pager-bundle and register the bundle in your Symfony bundles.php or AppKernel. That registration step is Symfony-specific and has no Laravel equivalent. Check composer.json for PHP and Twig constraints first, since the package targets Symfony 3 and older Twig versions.
Does symfony-twig/pager-bundle work with Doctrine queries and plain arrays?
Yes, the bundle is designed to paginate Doctrine ORM/DBAL queries as well as plain array data. It renders pager controls and page links from Twig templates with configurable page size and window ranges. That Doctrine-centric design does not map cleanly onto Eloquent or Laravel's query builder.
What is the Laravel equivalent of this Twig pager bundle?
Laravel's LengthAwarePaginator and the paginate methods on Eloquent and the query builder already handle ?page= parsing, query-string preservation, and links() rendering. Blade's $paginator->links() gives you Bootstrap-friendly markup without an extra dependency. For Symfony projects, Pagerfanta and KnpPaginatorBundle are the maintained alternatives.
Is symfony-twig/pager-bundle maintained and safe for production?
Adoption is effectively zero: no stars, no dependents, and a single maintainer with no visible CI or changelog. The composer constraints target Symfony 3, which reached end of life in 2021, so expect friction with PHP 8.x and Twig 3. Without downstream users or a test suite, there is little evidence of production hardening.
Which Symfony and PHP versions does symfony-twig/pager-bundle support?
The package targets Symfony 3 and older Twig versions, and that branch is end-of-life. It will likely hit issues on PHP 8.1+ (implicit nullable parameters, dynamic properties) and Twig 3 (escaping defaults, removed spaceless). Verify the exact constraints in composer.json against your supported PHP and Twig matrix before writing any code.
How do I override the pager templates and markup in symfony-twig/pager-bundle?
The bundle ships Bootstrap-friendly markup with overridable Twig templates, so you can customise the pager controls by overriding the bundle's template paths in your Symfony app config. This is standard Symfony bundle template overriding and does not translate to Blade. In Laravel you would publish and edit pagination views instead.
Does symfony-twig/pager-bundle handle GROUP BY, HAVING, DISTINCT, or joins when counting results?
The documentation does not confirm correct handling of complex SQL counting, and pagination packages commonly assume single-table counts. This matters most with joins that multiply rows, GROUP BY, HAVING, and DISTINCT, where a naive COUNT returns wrong totals. Test those queries explicitly if you evaluate it in a Symfony app, and prefer Pagerfanta if you need known behaviour.
Should I fork symfony-twig/pager-bundle or build pagination myself?
Do not fork it for a Laravel app: pagination is presentation-layer commodity logic that LengthAwarePaginator already solves. Even in Symfony, wrapping a thin PaginatorInterface around Pagerfanta is cheaper than owning a fork indefinitely. If a legacy service already uses it, contain the call site behind one adapter class so an eventual swap is a single-file change.
How do I test or migrate away from symfony-twig/pager-bundle?
There is no visible test suite or CI to inspect, so treat the code as unverified and add characterization tests around any existing call sites. Migrate by returning a neutral page-result DTO (items, total, perPage, currentPage) from your adapter and letting each stack render its own links. Exit targets are Pagerfanta for Symfony and native LengthAwarePaginator for Laravel.
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.
robertmarney/lara-hierarchial-collections
simonschaufi/rule-doc-generator
emissaoja/emissaoja
blackbricksoftware/gravityforms-civicrm-form-processor
al-rahabi/fancy-crud
jinas/dhivatar-component
mltstephane/laravel-quality
bernskiold/laravel-talentlms
bernskioldmedia/laravel-form-architect
youbar/easy-crud
c-point-labs/laravel-hostyourai
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