Weave Code
Paginator Bundle Laravel Package
silpo-tech/paginator-bundle
Paginator Bundle from Silpo Tech provides flexible pagination for PHP and Laravel applications, splitting large result sets into manageable pages for list views and search results. It offers straightforward Composer installation, simple configuration, and integration-ready APIs for cleaner listing c...
Paginator bundle for Symfony
Frequently asked questions about Paginator Bundle
- Is silpo-tech/paginator-bundle a Laravel package?
- No. Despite appearing in Laravel and PHP package scans, silpo-tech/paginator-bundle is explicitly a Symfony bundle. It ships a Symfony Bundle subclass, a dependency-injection extension, and a configuration tree, none of which Laravel's container discovers or boots. Treat it as a Symfony component, not a drop-in Laravel paginator.
- How do I install silpo-tech/paginator-bundle in a Laravel application?
- You can run composer require silpo-tech/paginator-bundle, but installation alone does not make it work in Laravel. Laravel has no bundle registration or DI extension loading, so the bundle will not be discovered or booted. A real integration requires a compatibility shim you write and maintain, or extraction of the framework-agnostic pagination core.
- What PHP and Symfony versions does silpo-tech/paginator-bundle support, and does that include Laravel?
- The provided evaluation does not list the declared php and symfony/* constraints, so you must read composer.json in the repository. There is no declared Laravel version support because the package targets Symfony. Check that any Symfony constraints intersect with the Symfony component versions pinned by your Laravel release before attempting adoption.
- Can silpo-tech/paginator-bundle return a Laravel LengthAwarePaginator?
- The evaluation flags this as an open question: it is not confirmed whether the bundle can emit a LengthAwarePaginator-shaped result or whether you must adapt its pager object. If you adopt the bundle, expect to write an adapter that maps its pagination contract to Illuminate\Pagination\LengthAwarePaginator. That adapter is your code to own and test.
- Which pagination contract does this bundle use: Pagerfanta, Symfony PaginatorInterface, or a custom pager?
- The available context does not confirm the contract; the evaluation explicitly lists this as a key question for the maintainer or source review. It could be a custom pager object, Pagerfanta, or Symfony's PaginatorInterface, and each choice changes the adapter you would need. Read the source before assuming compatibility with any existing pagination layer.
- Does silpo-tech/paginator-bundle require Doctrine ORM or DBAL?
- It is not confirmed whether pagination is bound to Doctrine for the query layer or whether the data source is pluggable through arrays, callbacks, or a query builder. If it assumes Doctrine ORM or DBAL, integrating it with Laravel's Eloquent query builder becomes significantly more work. The evaluation recommends verifying this before adoption because it determines whether you reuse the logic or reimplement it.
- Does this bundle support cursor or keyset pagination, or only offset pagination?
- The provided evaluation does not specify whether cursor and keyset pagination are supported or whether the bundle is offset-only. This matters for high-volume tables where deep offset pagination degrades. Confirm the supported modes from the source before relying on it for large result sets.
- Will installing this Symfony paginator bundle conflict with Laravel's Symfony component versions?
- There is a real risk. A Symfony bundle typically pulls in symfony/dependency-injection, symfony/config, and often symfony/framework-bundle, while Laravel already pins its own versions of Symfony components such as http-foundation, http-kernel, console, and routing. Adding constraints on components Laravel already constrains is a classic source of Composer resolver deadlocks on minor upgrades.
- Is silpo-tech/paginator-bundle safe to use in production?
- The adoption signals are close to the bottom: 0 stars, 0 dependents, and an overall score of 0.03. That is a maintenance verdict rather than a quality verdict, but with no downstream users nobody is filing issues or catching breaking changes. The recent 2025-10-03 release is a positive sign that someone is still tagging versions, yet a single-vendor cadence is not a stable public contract. Test coverage, CI status, and bus factor beyond the publishing organization are unconfirmed.
- What are the alternatives to using this bundle for pagination in Laravel?
- For most Laravel applications the built-in Illuminate paginator, backed by Eloquent or the query builder, is the lowest-risk option. If you want a standalone pagination library, Pagerfanta with a Laravel adapter is a more established choice, though it also needs integration work. The evaluation's preferred path for this specific package is to extract dependency-free pagination classes under your own namespace and wrap them in a thin Laravel adapter, not to depend on the bundle directly.
Weaver
How can I help you explore Laravel packages today?