Weave Code
Paginator Laravel Package
ruwork/paginator
A pagination package for Laravel and PHP applications that helps split large data sets into manageable pages. Suitable for list cards, search results, and other paginated views, with a simple API for adding page navigation to your project.
[READ-ONLY] Subtree split of the Ruwork Paginator library
Frequently asked questions about Paginator
- What is ruwork/paginator used for in Laravel?
- It is a Composer pagination package intended for Laravel and PHP applications that need to split large data sets into manageable pages. Typical uses include list cards, search results, and other paginated views that need page navigation. The available context describes it as likely a Laravel-oriented pagination abstraction or presenter, so confirm its exact behavior before adopting it.
- How do I install ruwork/paginator with Composer?
- Install it with Composer using the package name ruwork/paginator, ideally with a pinned version rather than a broad range. Confirm the package is available from Packagist and review its composer.json constraints before running composer require. Start in a branch or spike environment, not directly in production.
- Which Laravel and PHP versions does ruwork/paginator support?
- The provided context does not include a compatibility matrix, so the supported Laravel and PHP versions are unproven. Inspect the package composer.json, tagged releases, and CI configuration, then test against your target Laravel major version. Do not assume compatibility with current Laravel releases without a time-boxed spike.
- Does ruwork/paginator replace Laravel's built-in paginator?
- It is not proven to be a drop-in replacement for Laravel's LengthAwarePaginator, CursorPaginator, or API resource pagination. The package may fit only a narrow pagination gap, so compare its contracts, response shape, and page metadata against native pagination. Prefer an internal adapter over replacing Laravel native pagination directly.
- Does ruwork/paginator support Blade views and JSON API responses?
- Blade view compatibility and JSON serialization behavior are not confirmed in the available context and must be verified. If the package implements Laravel paginator contracts or wraps native paginators, existing Blade and API serialization may work, but that is an assumption. Test one Blade list view and one JSON endpoint during evaluation.
- How does ruwork/paginator handle count queries and large offsets?
- The context does not document how the package handles count queries, large offsets, or page metadata under concurrent writes. Pagination libraries do not solve scaling by themselves; count-query cost, large offsets, and missing indexes remain database concerns. Validate query counts and response consistency on realistic data volumes before production use.
- Is ruwork/paginator actively maintained and safe for production?
- Adoption and maintenance signals are weak: the metadata shows 0 stars, 0 dependents, and a read-only subtree split. Release cadence, test coverage, CI, and long-term ownership are not established in the provided context. Treat it as high risk, pin the dependency, assign an internal owner, and define an exit plan to revert to native pagination or fork.
- Can I use ruwork/paginator with Laravel API resources?
- Possibly, but only if the package implements or wraps Laravel's paginator contracts in a way that API resources can serialize. The context does not confirm compatibility with API resource responses or JSON metadata. If your application already uses native paginator responses, build an adapter layer instead of coupling API resources directly to this package.
- How should I test ruwork/paginator before using it in production?
- Run a time-boxed, non-production spike in a branch with a pinned version of the package. Reproduce one representative list endpoint and compare response shape, page metadata, query count, Blade rendering, and JSON output against Laravel native pagination. Add regression tests and roll out behind a feature flag to one low-risk endpoint first.
- What are the best alternatives to ruwork/paginator for Laravel?
- Laravel's native LengthAwarePaginator, CursorPaginator, and API resource pagination are the default alternatives and should be used unless a specific gap exists. You can also build a thin internal pagination adapter or choose a mature, actively maintained Composer package. Prefer native or well-adopted options when the requirement can be met without adding a low-adoption dependency.
Weaver
How can I help you explore Laravel packages today?