- How do I install mrshanebarron/accordion in a Laravel application?
- Install it with Composer using composer require mrshanebarron/accordion. Laravel package discovery registers the service provider automatically, so no manual provider entry is normally needed. If you want to override the package defaults, publish the configuration file with php artisan vendor:publish --tag=sb-config.
- Which Laravel and PHP versions does this accordion package support?
- The integration assessment assumes Laravel 9 or newer, PHP 8.1 or newer, and Composer 2 with package discovery enabled. The 1.0.1 patch release does not provide a clear signal about the supported framework matrix, so check the package's composer.json constraints before scheduling an upgrade. If your application runs an older Laravel version, verify compatibility first because a newest-LTS-only package can change your upgrade plans.
- How do I publish the accordion package config file?
- Run php artisan vendor:publish --tag=sb-config to publish the package configuration into your application's config directory. The sb- prefix is the vendor namespace short name used to avoid config filename collisions. Publishing is optional and only necessary when you need to override the package defaults.
- What changed in version 1.0.1 of mrshanebarron/accordion?
- Version 1.0.1 renames the package config file to include the sb- vendor prefix, which is the standard Laravel convention. It is shipped as a patch release, but it can be functionally breaking for existing installs that published the pre-fix filename and customized values in it. Verify both the package source merge path and the publish target path when reviewing the change.
- Why is my custom accordion configuration ignored after upgrading to 1.0.1?
- If your application still has the old published config filename, the package reads config('sb-accordion...') and falls back to its merged defaults. The application keeps booting and tests may keep passing, so the behavior change is easy to miss. Check that only the new prefixed config file exists and that it contains your expected custom values.
- How do I safely migrate an existing install from 1.0.0 to 1.0.1?
- Record the currently published config filename and a checksum of its contents in each environment, then upgrade in a scratch branch and diff the newly published file against the old one. If the keys are identical and only the filename changed, rename the published file and delete the old one rather than leaving both. Run php artisan config:clear and config:cache per environment, confirm the cached values are correct, and grep CI configs, Dockerfiles, and deploy scripts for the literal old filename. Promote from dev to staging to production with the config diff as the gate between each step.
- Does the accordion package require database migrations or queue workers?
- No database migrations, queue workers, schema changes, or service dependencies are implied by the package. It is a conventional Laravel package with a service provider that merges defaults and exposes a publishable config file. Integration is limited to Composer installation, optional config publishing, and package discovery registration.
- Does mrshanebarron/accordion work with php artisan config:cache?
- Yes, the configuration file works with Laravel's config cache, but you must clear and rebuild the cache after upgrading. A stale config cache can preserve old values and mask or delay the filename-rename issue differently in each environment. After running config:cache, confirm the cached output contains the values you expect before promoting the release.
- Can I use the package without publishing its config file?
- Yes, the service provider uses mergeConfigFrom to provide package defaults, so publishing is optional. If you never published the config file, the 1.0.1 filename rename has less impact because there is no old file to conflict with the new path. You only need to publish the config when you want to customize the package's default values.
- Should I pin to 1.0.0 or upgrade to 1.0.1, and what are the alternatives?
- If the package is load-bearing, pin 1.0.0 until the config audit is complete because the fix is cosmetic and there is no security driver to rush it. Alternatives include building the accordion as a native Blade component, using Alpine.js or Livewire for the toggle behavior, or adopting a larger Laravel UI kit, and you should compare markup, JavaScript dependencies, and maintenance expectations before switching. Ask the maintainer about the supported Laravel and PHP matrix and why the config rename shipped as a patch rather than a minor or major release.