Weave Code
Laravel Paginateroute Laravel Package
spatie/laravel-paginateroute
Adds a Laravel route macro to paginate via clean, translatable URLs like /news/page/2 instead of ?page=2. Includes a paginate route method and facade for generating pagination links. Note: this package is abandoned/unsupported—fork if needed.
Laravel router extension to easily use Laravel's paginator without the query string
Frequently asked questions about Laravel Paginateroute
- Does `spatie/laravel-paginateroute` work with Laravel 10.x?
- No, the package is abandoned and last updated in 2018, so it lacks Laravel 10.x compatibility. You’ll need to fork it and manually update dependencies like `illuminate/pagination` and adjust for route caching or PHP 8.1+ strict typing. Test thoroughly after forking.
- How do I replace `Route::get` with `Route::paginate` in my Laravel app?
- Replace `Route::get('/posts', [PostController::class, 'index'])` with `Route::paginate('/posts', [PostController::class, 'index'])`. Your controller logic stays the same—just return `Post::paginate(10)` as usual. The package handles the route-based pagination automatically.
- Will this break existing query-string pagination (e.g., `/posts?page=2`)?
- No, query-string pagination remains the default. You must explicitly opt into route-based pagination with `Route::paginate`. However, you’ll need to update frontend links (Blade, JavaScript) to use the new URL format, like `/posts/page/2`.
- Can I use this for API resources or cursor-based pagination?
- No, this package is designed for traditional web apps with page-number-based pagination (e.g., `/posts/page/2`). APIs typically use query-string pagination (`?page=2`), and cursor-based/infinite scroll pagination isn’t supported. Consider alternatives like `spatie/laravel-query-builder` for advanced use cases.
- How do I handle localization (e.g., `/posts/page/2` vs. `/nieuws/pagina/2`)?
- The package generates translatable routes like `/news/page/2` or `/nieuws/pagina/2` by default. For dynamic slugs, manually generate URLs using `route('posts.paginated', 2)` or tools like `Str::slug()`. Ensure your route names and middleware support localization.
- Are there performance differences between route-based and query-string pagination?
- Route-based pagination adds minimal overhead since it leverages Laravel’s existing Paginator. However, route caching in Laravel 9+ may conflict with dynamic pagination routes. Test in staging to confirm performance—query-string pagination is generally faster for APIs but less SEO-friendly.
- What if I have named routes or route parameters (e.g., `/posts/{id}/page/2`)?
- Route conflicts are possible. The package prioritizes pagination routes, so `/posts/{id}/page/2` may override intended parameter routes. Use explicit route names (e.g., `Route::paginate('/posts', ...)->name('posts.paginated')`) and test edge cases. Middleware may need adjustments for validation.
- Is there a modern alternative to this abandoned package?
- For Laravel 10+, consider building a custom solution using Laravel’s native Paginator + route macros or middleware. Alternatives like `spatie/laravel-query-builder` offer advanced pagination but aren’t drop-in replacements. Forking this package is an option, but weigh the maintenance effort.
- How do I migrate from query-string to route-based pagination in a large app?
- Start with non-critical routes (e.g., `/blog/page/2`) and pilot test. Update frontend links (Blade: `{{ $posts->links() }}`, JS: URL parsing) to use route-based URLs. Implement middleware to redirect legacy query-string URLs (e.g., `/posts?page=2` → `/posts/page/2`) during transition.
- Will this work with Laravel’s route caching (e.g., `php artisan route:cache`)?
- Potential conflicts exist, especially in Laravel 9+. Route caching may not handle dynamic pagination segments (e.g., `/page/{number}`) correctly. Test thoroughly in staging, or disable caching for pagination routes. Forking the package may require adjustments to support route caching.
Weaver
How can I help you explore Laravel packages today?