Filament Audiofeedback Laravel Package

Getting Started

This release is a rename-only release: the code-level API (namespace, plugin class, config key, translation namespace, routes, audiofeedback_settings table) is unchanged. Only the Composer package name and the published asset paths changed. Treat your first task as a dependency swap, not a feature upgrade.

1. Swap the package (do not have both installed at once — they share a namespace):

   composer remove blemli/filament-audiofeedback
   composer require blemli/audiofeedback-for-filament
   

2. Re-publish frontend assets and clear stale ones:

   php artisan filament:assets
   rm -rf public/js/blemli/filament-audiofeedback public/css/blemli/filament-audiofeedback
   

3. Register the plugin in your panel provider as before (same class, same namespace):

   ->plugin(\Blemli\...\AudioFeedbackPlugin::make())
   

4. Clear caches (php artisan optimize:clear) and confirm the settings page/routes still resolve — they are unchanged, so a 404 here means the plugin isn't registered, not a migration issue.

Where to look first: your composer.json/composer.lock, then public/{js,css}/blemli/, then your panel provider. There is nothing to read in the changelog beyond those two paths.

First use case: existing installs just need the Composer + assets swap; new installs run the install command (which no longer prompts you to star the repo) and then migrate the audiofeedback_settings table.

Implementation Patterns

• Deploy pipeline: add php artisan filament:assets to your deploy script after composer install. This release changes the asset destination directory, so any deploy that only runs composer install will 404 the JS/CSS until assets are republished. Purge the old blemli/filament-audiofeedback directories in the same step (or the deploy will ship dead weight indefinitely — the uninstall command now cleans the CSS dir, but nothing cleans it on upgrade).
• Multi-panel apps: registration stays per-provider; since routes/config are unchanged, a panel that worked before the rename keeps working. Verify each panel still loads assets if you publish per-environment.
• Settings storage: the audiofeedback_settings table and its migrations are untouched, so existing rows carry over. Do not re-run migrate:fresh to "fix" the rename.
• Custom sounds / theming: if you published views or translations, they still resolve under the same translation namespace. Only asset URLs changed — anything hardcoding public/js/blemli/filament-audiofeedback/... in a custom theme, Blade view, or CDN manifest must be updated to public/{js,css}/blemli/audiofeedback-for-filament/.
• Automated upgrades: Renovate/Dependabot will treat blemli/audiofeedback-for-filament as a new package, not an update of the old one. Add it explicitly to your dependency config (and remove the old entry), or you'll sit on the abandoned name indefinitely while security and compatibility fixes land in the new package.
• Forked/vendored installs: if you reference the package via a path or vcs repository in composer.json, update that entry to the new name — the old name will no longer resolve to this repository.

Gotchas and Tips

• Both packages installed simultaneously is the main failure mode. They declare the same namespace and plugin class, so Composer won't necessarily stop you, and you'll get confusing "class not found" or duplicate-registration errors. Always composer remove first.
• Stale assets are invisible failures. The plugin will appear to load but sounds won't play, or styles will be missing, because Filament's asset URLs now point at the new directory. Check the browser network tab for 404s under public/js/blemli/.
• Browser autoplay policy is the most common "it's broken" report that has nothing to do with the package: audio requires a user gesture. Sounds triggered on page load silently no-op; those triggered by a click work. Don't chase this during the upgrade.
• Config key is unchanged (audiofeedback). Your existing published config file remains valid — do not delete and republish blindly; diff it first if you've customised sound mappings or defaults.
• Translation namespace is unchanged. Community translations and any __('audiofeedback::...') calls keep working; only the vendor path in lang/vendor/ would differ if you published translations under the old name — republish to the new vendor directory if so.
• Config/view caching will mask the rename. Run php artisan optimize:clear (or config:clear + view:clear) before concluding something is broken.
• Uninstall now removes the published stylesheet directory too. If you have a custom stylesheet in that path, back it up before running the uninstall command.
• Silent minor bumps: no deprecations, no API removals — this is a safe upgrade, but it is not semver-neutral at the Composer level (package identity changed), so pin ^1.4 on the new name rather than assuming your existing constraint will float across.