- How do I install aymanalhattami/filament-slim-scrollbar in a Laravel Filament app?
- You can install it with composer require aymanalhattami/filament-slim-scrollbar. Laravel package auto-discovery registers the service provider, and the README says no further usage steps are required. Confirm the correct package version for your Filament major before installing, because the README version note links to a sibling repository and should be verified against the changelog.
- Does this package support Filament 3, 4, and 5?
- Yes for the main line: version 2.x is documented for Filament 3.x, 4.x, and 5.x, while version 1.x covers Filament 2.x. The changelog is the more reliable compatibility signal, showing 2.0.0 for Filament 3 and 2.1.1 adding Filament 4 and 5 support. Pin the version that matches your panel and test after Filament upgrades.
- Do I need to publish assets or register the service provider manually?
- The README presents Composer installation and usage as sufficient, relying on Laravel auto-discovery, and it does not document a required vendor:publish step. However, separate engineering notes mention a publish tag and manual config/app.php registration that the README does not cover. Treat those steps as unverified and read the small source before assuming zero configuration.
- How does the package slim scrollbars without JavaScript or CSS libraries?
- It ships a stylesheet that targets browser scrollbar pseudo-elements and related scrollbar properties, so no JavaScript or third-party CSS library is involved. The browser paints the native scroll container differently, and the package does not add models, migrations, routes, or Livewire components. That keeps the footprint small but also means browser support and CSS specificity determine the result.
- Will it style scrollbars in custom Blade and Livewire views, or only Filament components?
- The package is described as styling scrollbars broadly across the application, including the Filament sidebar and tables, but its practical reach depends on the selectors in its stylesheet. Custom Blade or Livewire views may be styled if they match those global selectors, but the package is not a component-aware API for arbitrary views. Audit your scrollable surfaces and test custom layouts before relying on it everywhere.
- Can I scope the slim scrollbar CSS to one Filament panel or avoid global overrides?
- The README does not document panel-level scoping options, and global scrollbar CSS can collide with intentional per-component styling. Inspect the stylesheet for broad selectors or !important declarations, then consider overriding or narrowing it in your own theme CSS if needed. If scoping is essential, inlining about 20 lines of CSS in your theme may be simpler than adapting the package.
- Does it support dark mode and Firefox scrollbars?
- The package is pure CSS and advertises both dark and light mode support, inheriting Filament's theming. It targets WebKit scrollbar pseudo-elements and also uses standard scrollbar-width and scrollbar-color properties, which Firefox supports. Forced-colors or high-contrast modes may ignore custom scrollbar styling, so verify those environments rather than assuming perfect degradation.
- Is there an accessibility risk with slim scrollbars?
- Yes, reduced scrollbar thickness can shrink the draggable target and is a genuine accessibility concern, especially for users with motor or low-vision impairments. Review WCAG 2.2 target-size guidance and consider whether users need a native-scrollbar toggle. The package's large-screen-only behavior in 2.1.0 mitigates mobile touch issues but does not eliminate desktop pointer-target concerns.
- How do I uninstall or revert the slim scrollbar styles?
- Because the package adds only a stylesheet through a service provider and stores no data or config state, removal is straightforward. Run composer remove aymanalhattami/filament-slim-scrollbar and clear cached assets or views if your deployment caches them. There is no schema, migration, or persisted user preference to clean up.
- Is this package actively maintained, and what are the alternatives?
- The project is MIT licensed but small, with roughly 51 stars, no dependents, and a single maintainer, so treat it as a low-risk cosmetic dependency rather than a platform capability. Recent dependency-bot activity is not strong evidence of feature maintenance, although the MIT license lets you fork or inline the CSS if needed. The main alternative is adding equivalent scrollbar CSS to your own Filament theme, which you already control.