- Is mazarini/pagination-bundle a Laravel package?
- No. It is a Symfony bundle built against Doctrine ORM, registered through config/bundles.php and wired into Symfony's dependency injection container, almost certainly with Twig templates. Laravel has no bundle system, no Twig layer, and Eloquent rather than Doctrine by default. Only the pagination math is realistically portable.
- Can I install mazarini/pagination-bundle in Laravel with Composer?
- Composer may resolve the package, but it will not work: the bundle's service definitions expect Symfony's container and bundle registration, which Laravel does not provide. Even adding laravel-doctrine/orm leaves you with a Symfony bundle shim plus a Doctrine bridge, so you inherit two layers of integration risk for a problem Laravel already solves. Direct installation into Laravel is not viable.
- Which Laravel versions does mazarini/pagination-bundle support?
- None are targeted. The package ships no Laravel service provider, facade, config file, or Blade views, so Laravel compatibility is undefined rather than version-specific. Check composer.json for its PHP, Symfony, and Doctrine constraints instead, since those are the versions that actually matter here.
- How do I configure page sizes and navigation markup with this bundle?
- Configuration happens through the Symfony bundle's config files under config/packages, with navigation rendered via the bundle's services and template helpers. There is no Laravel config equivalent, so any port would mean mapping page size to perPage() and rewriting the markup as a Blade view. That mapping work is small, but it is work you would own forever.
- What should I use for pagination in Laravel instead?
- Use the framework primitives: LengthAwarePaginator for offset-based links and CursorPaginator for large offsets or infinite scroll. Eloquent and the Query Builder expose paginate() and cursorPaginate(), and links() renders the navigation in Blade. No third-party pagination package is required.
- Is the GPL-3.0 license a problem for a Laravel application?
- GPL-3.0 is copyleft. Internal or SaaS-only use is generally fine under most interpretations, but redistributing a derivative inside a shipped product or SDK can trigger source-disclosure obligations. Get legal sign-off before copying any code, including the page-window and ellipsis algorithm, not after.
- Does mazarini/pagination-bundle support Doctrine ORM 3, Symfony 6/7 and PHP 8?
- That is unverified from the package metadata. PHP 8.x support, Symfony 6/7 support, and Doctrine ORM 2 versus 3 compatibility all need checking in composer.json and the CI configuration. With roughly one star and zero dependents, there is very little production evidence either way.
- How does mazarini/pagination-bundle compare to Pagerfanta or KnpPaginatorBundle?
- Both Pagerfanta and KnpPaginatorBundle are far more widely adopted Symfony pagination libraries with larger communities and active maintenance. This bundle is only justified if it offers a specific feature the incumbents lack, and nothing in its metadata or adoption signals suggests that. For a Symfony stack, evaluate those two first.
- Is mazarini/pagination-bundle actively maintained and safe for production?
- Adoption signals are very low: about one star, zero dependents, a single maintainer, and no visible release cadence. That means high abandonment risk and unbounded security-patch latency. There is also no published test coverage, so adopting it means adopting unverified logic.
- Can I extract just the page-window and ellipsis logic into Laravel?
- The portable core is small: current page, per-page, offset and limit, total, and the page-window with ellipsis, realistically a few hundred lines. That is a few days of work to reimplement as a Laravel service or custom paginator. Do the GPL-3.0 review first, or simply write the algorithm yourself from scratch.