Getting Started

Start with the new package name. v1.0.1 changed the Composer package name, so composer require old-vendor/old-name will fail. Find the new name in the package’s composer.json (or Packagist) and update your require line. Run composer remove old-vendor/old-name if needed, then composer require new-vendor/new-name:^1.0.
Look first at vendor/<new-vendor>/<new-name>/dist/. The dist/ folder is now committed and shipped with the package, so prebuilt assets should be available without running a Node build. Confirm what is inside—JS, CSS, or both—and check whether the README references a publish tag for those assets.
Clear Laravel’s caches after the rename. Run composer dump-autoload and php artisan optimize:clear. The old package name may still be referenced in config, view namespaces, publish tags, or facade aliases.
First use case: publish the shipped assets into public/vendor/<package> using php artisan vendor:publish --tag=<package>-assets (the tag may have changed with the package name). Then reference them from Blade with asset('vendor/<package>/...'). If the package registers a service provider, confirm auto-discovery picked up the new namespace.

Implementation Patterns

Treat the name change as a migration, not an upgrade. Search your codebase for the old vendor/package string in composer.json, config files, Blade templates, asset paths, cache keys, translation namespaces, and publish tags before deploying.
Publish config and assets separately. Use vendor:publish --provider="New\\Namespace\\ServiceProvider" for config and a tagged publish for dist/ assets. Keep the two steps explicit so upgrades don’t silently overwrite either.
Remove redundant frontend builds. Since dist/ is committed upstream, you no longer need to build this package’s assets yourself. If you use Vite or Mix, alias the package’s dist/ path rather than copying or rebuilding it.
In CI, rely on composer install --prefer-dist. The committed dist/ should be included in the Composer archive. Verify that your .gitattributes export-ignore rules do not accidentally exclude dist/ when installing from a tagged release.
Pin tagged releases. Because dist/ is checked in, it can drift from src/. Prefer ^1.0 tagged releases over dev-main so the shipped assets match the tagged source.

The package rename is a breaking change. It breaks lock files, composer require, auto-discovery, and any hard-coded strings. Grep for the old name across config, views, translations, and asset references.
dist/ may be stale. Committed build output can lag behind source changes. After upgrading, compare the release tag with the contents of dist/; if something looks wrong, check the package’s release notes or open an issue rather than editing dist/ by hand.
vendor:publish without --force will not update existing published assets. After upgrading, run the tagged publish with --force deliberately, or version your published asset paths to avoid stale CSS/JS in the browser.
Clear more than Composer. After the rename, run php artisan config:clear, view:clear, and route:clear. If OPcache is enabled, restart PHP-FPM so old class names are not cached.
Check extension points before customizing. If the package exposes config for asset paths or publish tags, use those rather than overriding files in dist/. Hand-editing dist/ will be overwritten on the next publish and is not upgrade-safe.