Weave Code
Paginator Bundle Laravel Package
ruwork/paginator-bundle
Symfony bundle that integrates the Ruwork paginator, providing service configuration and Twig helpers for splitting result sets into pages and rendering page navigation. It makes pagination easy to wire into Symfony applications while keeping the underlying paginator library reusable.
RuWork PaginatorBundle is a Symfony bundle that adds a lightweight, service-based paginator to your application. It wraps result sets in a PaginatorInterface, letting controllers and templates page through data without repetitive boilerplate, while page size and request parameter names remain configurable through the bundle's own configuration.
- Paginator service available via the Symfony container and autowiring
- Handles countable data sources and sliced result windows
- Configurable page size and page parameter naming
- Twig-friendly output for rendering navigation
- Simple defaults that require minimal setup
Frequently asked questions about Paginator Bundle
- Is ruwork/paginator-bundle a Laravel package?
- No. ruwork/paginator-bundle is a Symfony bundle that registers pagination services through Symfony's dependency injection container and kernel conventions. It has no service provider, facade, Blade directives, or Eloquent integration, so it does not fit the Laravel package model. Treat it as a Symfony component rather than something you would require in a Laravel application.
- How do I install ruwork/paginator-bundle in a Laravel application?
- You should not install it in a Laravel application. Wiring a Symfony bundle into Laravel would require a custom bridge for bundle registration, container configuration, and any Twig or HTTP-kernel assumptions, which is disproportionate effort for pagination. Laravel already ships LengthAwarePaginator, CursorPaginator, API resources, and query-builder integration that cover the same ground natively.
- Does ruwork/paginator-bundle support modern PHP and Laravel versions?
- Unlikely. The package was last released in 2018 and is archived, so its Composer constraints target the PHP and Symfony versions of that era and will probably conflict with modern PHP 8.x and current Laravel releases. Run a compatibility audit of its composer.json and transitive dependencies before assuming anything works. Expect blockers around PHP version, Symfony major version, and template engine assumptions.
- Is ruwork/paginator-bundle still maintained?
- No. The repository is archived, the last release was in 2018, and it has zero stars and zero dependents. Archived status means no upstream bug fixes, no security response, and no compatibility work for modern PHP or framework versions. The MIT license does allow a fork, but that shifts all maintenance and patching responsibility onto your team.
- What should I use instead of ruwork/paginator-bundle for pagination in Laravel?
- Use Laravel's built-in pagination: the query builder and Eloquent paginate methods, LengthAwarePaginator for offset pagination, CursorPaginator for keyset pagination, and API resources for shaping paginated responses. These are maintained with the framework, tested against each Laravel release, and require no additional dependency. Only consider a third-party library if it is framework-agnostic and actively supported.
- Does ruwork/paginator-bundle handle cursor or keyset pagination?
- Based on the available information the bundle is aimed at splitting collections or query results into pages with helpers for building page navigation, which points to offset-style pagination. Whether it offers a cursor or keyset mode is not documented in the material available, so verify before relying on it. In Laravel, CursorPaginator covers keyset pagination out of the box and avoids the offset stability problems that appear in large or frequently changing result sets.
- Can I fork ruwork/paginator-bundle and adapt it for Laravel?
- Technically yes, since it is MIT licensed, but it is rarely worth it. You would own the fork, its PHP and Laravel compatibility matrix, and any future security patches, and you would still be reimplementing behavior Laravel already provides. If the bundle contains domain-specific pagination logic worth keeping, port only that logic into a small Laravel service or provider with tests rather than forking the whole bundle.
- What are the production risks of depending on an archived Symfony pagination bundle?
- The main risks are no security response, no PHP 8.x or framework compatibility fixes, and untested edge cases given zero dependents. Pagination code also hides subtler problems around total-count queries, offset drift when sort order is not deterministic, and behavior on large result sets. Those issues surface under load, not in local testing, which makes an unmaintained dependency a poor bet for production.
- How does ruwork/paginator-bundle compare with Laravel's LengthAwarePaginator?
- LengthAwarePaginator is part of Laravel core, integrates directly with the query builder and Eloquent, produces total counts and page links, and is maintained alongside every framework release. ruwork/paginator-bundle is a Symfony bundle from 2018 with no Laravel integration surface and no ongoing maintenance. For a Laravel application the built-in paginator wins on fit, support, and testing coverage without a meaningful feature trade-off.
- How do I migrate from a Symfony paginator to Laravel pagination?
- Keep the existing Symfony pagination running at the edge while routes are migrated, then replace it with a Laravel paginator adapter route by route. Run a discovery spike first to document the bundle's public API and pagination algorithm, then compare outputs in parallel against current behavior before cutting over. Roll out behind a feature flag and verify against the oldest and newest PHP and Laravel versions you support.
Weaver
How can I help you explore Laravel packages today?