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

Pagerfanta Bundle Laravel Package

nitra/pagerfanta-bundle

Symfony bundle integrating Pagerfanta pagination, offering flexible pagers, adapters, and Twig helpers for paginated lists. Easily paginate Doctrine queries, arrays, and custom data sources with configurable templates and straightforward Symfony integration.

View on GitHub
Deep Wiki
Context7

Product Decisions This Supports

  • Framework fit check (critical): Despite being catalogued under "Laravel/PHP," this is a Symfony2 bundle, not a Laravel package. It contributes zero Laravel service providers, facades, config, or Blade/Eloquent integration. Any roadmap item assuming Laravel compatibility should be corrected before it reaches a sprint.
  • Build vs. buy for pagination: Pagination is a commodity. Laravel ships LengthAwarePaginator, CursorPaginator, and simplePaginate out of the box; the framework-agnostic core (pagerfanta/pagerfanta) is a separate, better-maintained dependency. Buying/integrating this bundle means adopting glue code for a framework we don't run.
  • Vendor risk / dependency hygiene: Score 0, zero stars, zero dependents, hosted on Bitbucket, and pinned to Symfony2 (EOL since November 2018). This is a do-not-adopt signal. Use it as a worked example in our dependency review checklist rather than as a candidate.
  • Legacy archaeology, not new features: The only realistic use case is auditing or maintaining an inherited Symfony2 application that already depends on it — a cost-of-ownership question, not a feature enabler.
  • Roadmap impact: None for greenfield work. If a team proposes it, the correct PM response is "use Laravel's native paginator or BabDev Pagerfanta," and reallocate the integration time to the actual feature.
  • API contract decisions: Pagination shape (offset vs. cursor vs. page-number) is a product decision affecting UX and mobile/API performance. That decision is made in our own paginator layer; this package adds no influence over it.

When to Consider This Package

Consider it only when all of the following hold:

  • You are maintaining an existing Symfony2 (not Laravel, not Symfony 4+) application.
  • That application already depends on this bundle, and removal is costlier than retention.
  • You have verified the bundle is vendored/pinned and the security posture of the transitive Pagerfanta version is acceptable.
  • There is no active product roadmap beyond maintenance for that application.

Look elsewhere — immediately — when:

  • You are building or extending a Laravel application. Use Laravel's native paginator; it is maintained, documented, and free.
  • You need a modern, maintained Symfony integration. Use BabDev Pagerfanta (the actively maintained successor) instead of this bundle.
  • You need the pagination logic only. Depend on pagerfanta/pagerfanta directly and write ~20 lines of adapter code rather than inheriting an unmaintained bundle.
  • You require community support, security advisories, or a contributor path. Zero stars and zero dependents means no ecosystem to lean on.
  • You are mid-migration off Symfony2. Adding this now increases the migration surface.

How to Pitch It (Stakeholders)

For executives: This package is a small integration shim for Symfony2, a PHP framework we do not use, and it has no community traction (no stars, no dependents) on a framework version that reached end of life in 2018. Adopting it would create a maintenance and security liability with no offsetting product value. Recommendation: do not adopt; no roadmap or budget impact. Pagination, the capability it nominally provides, is already included in Laravel at no cost.

For engineering: Treat this as out of scope. It is a Symfony2 bundle — no service provider, no Laravel config, no relevance to our stack. If you need Pagerfanta-style pagination semantics, depend on pagerfanta/pagerfanta directly behind our own interface, or use Laravel's CursorPaginator for high-volume endpoints and LengthAwarePaginator for admin tables. If you encounter this in an inherited Symfony2 codebase, flag it in the dependency audit and pair its removal with the framework upgrade rather than investing in it. For new pagination work, the maintained successor is BabDev Pagerfanta.

Bottom line: Correct the catalogue classification (Symfony2, not Laravel), close the evaluation, and spend the saved effort on the pagination UX decision — cursor vs. offset — which is where the real product value sits.

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.
novasa/laravel-language-center
opencage/geocode
adolfoholzer/parameters
livenetworks/ln-starter
shitoudev/permissionmanager
johannesclimacus/laravel-tui
hocvt/seotools
vitalybaev/sypexgeo
amphibee/themosis-ignition
gito-me/fast-excel
frankyso/laravel-ipaymu
geolize-studio/laravel-chile
boomerangui/chat
cgv/localized-resource
noith/settings
kda/laravel-package
kda/filament-dynamic-navigation
bypersoft/signbox
pairus/product-data
fayne/laravel-filament-cms-core