- How do I install mrshanebarron/tabs in a Laravel application?
- Install it with composer require mrshanebarron/tabs. The package follows the standard Laravel shape: Composer install, service provider auto-discovery, and a config file merged from the package and optionally published. Check the composer.json constraints in the repository before installing to confirm your Laravel version is supported.
- Which Laravel versions does mrshanebarron/tabs support?
- Laravel major version support is not confirmed in the material available; the only published release note is a config filename fix in v1.0.1. Check the package's composer.json require constraints on Packagist or GitHub before committing. If your app runs a recent Laravel release, do a smoke render in a staging branch first.
- How do I publish the mrshanebarron/tabs config file?
- Use the standard Laravel vendor publish command, php artisan vendor:publish, and select the mrshanebarron/tabs provider tag. As of v1.0.1 the published file uses an sb- prefix to avoid collisions in the application config directory. Confirm the exact tag in the package's service provider, since tags are not documented in the release notes.
- Why is my mrshanebarron/tabs config ignored after upgrading to v1.0.1?
- v1.0.1 corrected the config file naming to use an sb- prefix, so a config published under the old name may now be orphaned or ignored. Rename or merge the existing file into the new prefixed filename, then run php artisan config:clear and rebuild the cache. Whether the legacy filename is still read as a fallback is unconfirmed, so treat this as a migration rather than a hotfix.
- How do I define tabs and panels with mrshanebarron/tabs in Blade?
- The package exposes a simple API for defining tabs and panels and rendering the tab navigation inside Blade views. The general pattern is to register each tab with a label and content, then render the nav and the matching panel in your layout. Check the repository examples for the exact method names, since the README excerpt available is thin.
- Can I customize tab labels, ordering, and the active tab?
- Yes. Labels, ordering, and active states are described as customizable in the package overview. Typical usage is to pass a label and sort position per tab and mark one as active so it renders selected on page load. Verify the exact option keys against the source, because the release notes do not document them.
- Do I need to clear the config cache after upgrading mrshanebarron/tabs?
- Yes. Run php artisan config:clear after any upgrade that touches config file naming, then re-run php artisan config:cache if you cache config in production. Laravel can otherwise keep resolving the old filename from the cached config. The symptom is subtle: package defaults apply where you believe overrides exist.
- Is mrshanebarron/tabs safe to use in production?
- It is a leaf UI dependency with a small blast radius, so runtime risk is low. The real risk is upgrade hygiene around the v1.0.1 config rename and the lack of a published changelog or diff. Pin the version, review release notes, and verify config resolution in staging before deploying.
- Does mrshanebarron/tabs have tests and CI coverage?
- Test coverage is unverified from the available material; no changelog, diff, or CI status was provided. Ask whether there is coverage for config resolution and the publish-then-boot sequence. If your team requires tested dependencies, run the suite locally or vendor the component instead.
- What are alternatives to mrshanebarron/tabs for Laravel tabs?
- Common alternatives are hand-rolled Blade partials with Alpine.js, Laravel Blade components, Livewire components for dynamic tabs, or admin-panel stacks like Filament and Nova that ship tab layouts. Choose this package if you want a small, reusable API that drops into existing Blade layouts without a JavaScript framework.