- What does revolution/laravel-pagination-bulma do?
- It provides a Laravel pagination Blade view that outputs Bulma-compatible pagination markup instead of Laravel's default pagination links. It is a presentation-layer adapter, not a pagination engine, so it does not change how Laravel queries or paginates data. You use it when your Blade-rendered Laravel application already uses Bulma.
- How do I install laravel-pagination-bulma with Composer?
- Install it with Composer using the package name revolution/laravel-pagination-bulma, then follow the package's view registration or publishing steps. Because the last release dates to 2020, run a compatibility spike on a branch before adding it to production. Confirm service-provider auto-discovery and pagination view registration for your Laravel version.
- Does laravel-pagination-bulma support Laravel 10, 11, or 12?
- There is no guarantee; the package's last release was in 2020, so its Composer constraints may not allow modern Laravel and PHP versions. Test installation against your exact Laravel and PHP matrix in a non-production branch. If Composer conflicts occur, copy the Blade template into your application and remove the dependency.
- How do I customize the Bulma pagination markup?
- Publish the package's pagination views if publishing is supported, then edit the copied Blade file in your application's pagination view path. You can also copy the template directly into resources/views/vendor/pagination or another custom view directory. Register your customized view through Laravel's paginator configuration or a per-paginator view call.
- What are alternatives to laravel-pagination-bulma for Tailwind or Bootstrap?
- This package is specifically designed to emit Bulma-compatible markup, so it is a poor fit for Tailwind or Bootstrap design systems. Use Laravel's default pagination views or a design-system-specific pagination template instead. Only adopt this package if Bulma is the confirmed target CSS framework.
- Does laravel-pagination-bulma work with Inertia or API-only Laravel apps?
- It is a Blade view adapter for server-rendered pagination, so it is not useful for API-only services or SPA and Inertia front ends that render pagination client-side. Those applications should return paginator metadata and build pagination controls in their frontend framework. This package only matters when Laravel renders pagination links in Blade.
- How do I register a custom pagination view in Laravel?
- Laravel lets you set a default pagination view through the Paginator configuration or call a view method on a specific paginator instance. Place the Bulma Blade template in a path your application owns, such as resources/views/vendor/pagination, and reference that view. This keeps the integration explicit and makes future Laravel upgrades easier to manage.
- Is laravel-pagination-bulma maintained and safe for production?
- The package is effectively unmaintained, with a 2020 release, low community signal, and no dependent ecosystem. Runtime risk is low because it is static Blade markup, but dependency-hygiene risk is high on modern Laravel and PHP versions. For production, the safer path is usually to vendor the template and own it internally.
- Should I install laravel-pagination-bulma or copy the Blade template?
- For most teams, copying the Blade template into the application is the safer long-term choice because the package is small and unmaintained. The MIT license permits you to reuse and adapt the markup while avoiding Composer constraints and package lock-in. Install the package only if you have validated compatibility and prefer the Composer-managed route.
- How do I test Bulma pagination rendering in Laravel?
- Add functional or visual tests that render a paginator in Blade and assert the expected Bulma classes and accessible link structure. Test simple, length-aware, and cursor paginators if your application uses them, and compare the output with current Laravel defaults. Also verify behavior across the Laravel and Bulma versions you actually deploy.