- Does this package work with Filament v5?
- The package overview describes a Filament v5 plugin, but earlier notes referenced v3 and v4, so version alignment must be reconciled before adoption. Check the Composer constraints against the Filament major and minor you actually run. If the constraints are permissive rather than tight, test on a low-traffic panel first because sidebar markup changes can break the integration silently.
- How do I install martin6363/filament-sidebar-resize in a Laravel app?
- Install it with Composer, register the plugin on the target Filament panel in that panel's provider, then publish its config and assets. Finish with visual QA on the panel where it is enabled. The integration is small and time-boxable, typically half a day to a day for a Laravel/Filament developer.
- How does the plugin remember each user's preferred sidebar width?
- Persistence is handled client-side with localStorage rather than a database column or server-side profile setting. That means the width is remembered per browser and per device, not per user identity across machines. Users on another browser or in a private window will not inherit their saved width.
- Can I configure the default, minimum, and maximum sidebar widths?
- Yes. The package provides a published config stub with configurable default, minimum, and maximum widths. Set those values to match your panel's navigation density and screen-size assumptions, then clear any cached config in non-local environments. The limits also constrain how far users can drag the sidebar edge.
- Does this plugin add database migrations, models, routes, or middleware?
- No. It is a presentation-layer Filament panel plugin with no migration, model, route, middleware, or server-side persistence. Its footprint is a plugin registration, published assets, and a config stub. That makes it cheap to remove if it does not suit your panel.
- Is the sidebar resize handle keyboard accessible and screen-reader labelled?
- The provided overview does not confirm keyboard operability or screen-reader labelling, and the technical assessment flags this as unresolved. The interaction is described as drag-to-resize, which suggests pointer-first behaviour. Verify keyboard focus, resize controls, and ARIA labelling before adopting it in an accessibility or compliance-sensitive organisation.
- Will this sidebar resize plugin break when I upgrade Filament?
- It may. The plugin couples to Filament's sidebar markup and CSS classes, which are internal and non-contractual, so an upgrade can make the grip vanish or stop dragging without throwing an error. Version 1.0.1 exists specifically because 1.0.0 broke scrollbar access in the sidebar. Pin the package, retest navigation scrolling and pointer events after every Filament upgrade, and keep a visual QA checklist.
- Does it support multiple panels, RTL layouts, mobile drawers, and dark mode?
- These scenarios are unverified in the package's public signals because it has zero dependents and little community testing. The localStorage key may be global rather than namespaced per panel or tenant, so width can plausibly leak between panels. Test multi-panel scoping, RTL, the mobile collapsed drawer, dark mode, and tenant switching on a non-critical panel before wider rollout.
- Does the package have tests or a CI matrix across Filament versions?
- No test suite or CI matrix across Filament versions is indicated in the assessment; QA appears to be manual. That shifts regression detection onto your own visual checks, especially for pointer-event interception and sidebar scrolling. Treat the package as forkable source you happen to consume through Composer rather than as tested infrastructure.
- Should I use this on a customer-facing production panel?
- The technical assessment recommends a time-boxed spike on one internal, low-traffic panel, not adoption into a customer-critical path. The package has a single primary maintainer, seven stars, zero dependents, and a history of one CSS regression. If you adopt it, pin the exact version, review the service provider, confirm asset registration goes through Filament's pipeline, and be ready to fork or remove it.