- Is mindy/pagination a Laravel pagination package?
- mindy/pagination is a component of the MindyPHP micro-framework, not a first-party Laravel package. It does not ship a Laravel ServiceProvider, facade, config file, or Blade directive, and it does not implement Laravel's LengthAwarePaginator contract. In a Laravel app it sits beside the native paginator as a separate abstraction.
- How do I install mindy/pagination with Composer?
- You can install it with composer require mindy/pagination if a Packagist release resolves. Adoption in Laravel is not recommended because the package appears to be a read-only subtree split of MindyPHP with limited release cadence. Check composer.json for php constraints and mindy/* sibling dependencies before installing.
- Does mindy/pagination work with Laravel 9, 10, or 11?
- There is no verified Laravel 9–11 integration path. The package targets MindyPHP and shows no ServiceProvider or Laravel paginator implementation, so Laravel's paginate, simplePaginate, cursorPaginate, and links directives remain the supported route. Treat Laravel compatibility as unverified unless you build and test an adapter.
- Does mindy/pagination provide a ServiceProvider or Blade pagination views?
- Based on the available repository profile, no Laravel ServiceProvider, facade, config, or Blade directive is included. It may provide its own rendering utilities for MindyPHP views, but those are not Laravel Blade pagination links. For Laravel, use the built-in links() directive and published pagination views.
- Can mindy/pagination replace Laravel's LengthAwarePaginator or CursorPaginator?
- No. It does not implement Illuminate\Contracts\Pagination\Paginator or LengthAwarePaginator, so Laravel features that type-hint those contracts will not accept it. Laravel's native paginators already handle offset pagination, cursor pagination, resource collections, and view rendering. Introducing mindy/pagination creates a second, incompatible pagination vocabulary.
- Is mindy/pagination maintained and safe for production?
- Maintenance risk is high because the repository has around 1 star, 0 dependents, and no visible release cadence or CI. It appears to be a subtree split published for MindyPHP internal use, so the Packagist artifact may lag the monorepo. Security exposure is low because pagination touches no auth, persistence, money, or PII, but unclamped per_page values can still be a resource-exhaustion vector.
- Does mindy/pagination support cursor or keyset pagination?
- The available context does not document cursor or keyset support, and pagination packages of this era are typically offset-only. Offset pagination becomes a scaling liability on large tables because deep offsets get slower. If you need cursor pagination in Laravel, use cursorPaginate() instead.
- What should I check before installing mindy/pagination in a Laravel app?
- Inspect composer.json for php and mindy/* sibling constraints, confirm whether installing it pulls the whole MindyPHP framework transitively, and check whether a real release tag exists or install is pinned to dev-master. Look for a test suite and any dependency on Request, Router, or View singletons. Also decide whether your product standardizes on Laravel's pagination ecosystem or tolerates mixed-paradigm components.
- What are the best alternatives to mindy/pagination for Laravel?
- Laravel's built-in paginate(), simplePaginate(), cursorPaginate(), API ResourceCollection, and links() Blade directive cover most needs. For custom views, publish Laravel's pagination views and style them with Tailwind or Bootstrap. These are first-party maintained and inherit Laravel's PHP-version and security guarantees.
- How do I migrate from mindy/pagination to Laravel's native paginator?
- Treat it as a spike rather than an adoption: map each mindy/pagination call to paginate(), simplePaginate(), or cursorPaginate() and replace custom link rendering with links() or published Blade views. Remove the Composer dependency once the native path is verified in tests. Because pagination is a thin offset-and-URL concern, the migration is usually cheap and removes a maintenance and compatibility burden.