- What is mrshanebarron/drawer and what does it do in Laravel?
- mrshanebarron/drawer is a Laravel/PHP package for adding drawer-style UI panels, such as slide-out navigation, filters, or contextual actions, to Laravel applications. It follows a conventional Laravel package shape with a service provider, publishable config, and Blade integration. It is intended to be lightweight and dropped into a Laravel app with minimal setup.
- How do I install mrshanebarron/drawer in a Laravel app?
- Install it with composer require mrshanebarron/drawer. Laravel package auto-discovery should register the service provider; if it does not, add the provider manually in config/app.php. Then publish config or assets with php artisan vendor:publish and follow the README for Blade usage. Check composer.json version constraints before installing in production.
- Which Laravel and PHP versions does mrshanebarron/drawer support?
- The package is assessed as feasible for Laravel 9, 10, or 11 on PHP 8.1+, but the supplied context does not include a verified support matrix. Check composer.json and CI results before committing to a version. Treat the Laravel 9/10/11 and PHP 8.1+ guidance as an assessment assumption rather than a confirmed guarantee.
- How do I publish and configure the drawer config file?
- Publish the package config with php artisan vendor:publish using the package's config tag, then adjust values in the published config file and any matching .env keys. In v1.0.1 the config stub uses an sb- prefix, so the published filename will be sb-<name>.php rather than the older name. Confirm the exact tag and filename in the README or the provider publishes() call.
- Why did my config file name change in v1.0.1 and what should I do?
- v1.0.1 corrects the config file naming convention to use an sb- prefix. If you upgrade, re-publish or manually rename the config file, move your existing values across, and remove the orphaned old file. Then run php artisan config:clear and php artisan config:cache so Laravel does not keep reading stale cached paths.
- Is the config rename in v1.0.1 a breaking change for existing installs?
- Functionally it may be, because consumers who published the v1.0.0 config could silently fall back to defaults when the package starts reading the renamed file. Whether it is officially breaking depends on the maintainer's changelog and semver policy, which the one-line release note does not clarify. For existing installs, treat it as a migration and verify the effective config after upgrading.
- How do I use the drawer component in Blade templates?
- The package is described as offering straightforward Blade integration for slide-out panels, but the exact component or directive syntax is not included in the supplied README excerpt. Use the package's documented Blade tags and pass your drawer content, trigger, and options as described there. If you need exact API details, check the repository README and source views before building against it.
- Does mrshanebarron/drawer work with Livewire or Tailwind CSS?
- The provided context does not confirm Livewire or Tailwind support; it only describes a Laravel Blade-oriented drawer component. You can usually style the drawer markup with Tailwind classes, and Livewire can render Blade components, but verify compatibility in the source before relying on it. Test interactions such as opening, closing, and state persistence in your own stack.
- How should I test drawer components in a Laravel application?
- Test drawer rendering and interactions in your Laravel test suite using the framework's HTTP and view assertions, and add browser-level tests for open and close behavior if the component relies on JavaScript. Also test config publishing and the sb-prefixed config filename in a clean app to catch upgrade issues. The supplied assessment does not include test-coverage evidence for the package itself.
- Is mrshanebarron/drawer actively maintained and what are the alternatives?
- Maintenance signal is unclear from the available context: there is a v1.0.1 patch but no detailed changelog, test results, or issue-response data. Alternatives include building the drawer with plain Blade plus Alpine.js or Tailwind, or using a broader UI component package. Evaluate release cadence and open issues on the repository before adopting it for long-lived production use.