Updating the Package

composer update medialight/textstem-laravel
php artisan view:clear
php artisan migrate
php artisan textstem:refresh-assets

view:clear matters even when nothing looks wrong: Laravel's compiled Blade cache is keyed by file path, not content hash, so an updated package template can silently keep serving the pre-update compiled version until the cache is cleared -- this has caused Alpine/Livewire components to reference stores or handlers that exist in the new source but not in the stale compiled output.

php artisan migrate matters too: updates can add columns the admin relies on (for example wrangler_pages.updated_by, which records who last saved each page for the Pages list and cards).

If you use live page screenshots (Step 13), run php artisan textstem:page-screenshots --check and php artisan queue:restart after updating.

textstem:refresh-assets is also required for any update that touches package CSS/JS (e.g. new Tailwind utility classes) -- public/vendor/medialight/textstem/style.css and textstem.js are prebuilt and committed to the package, not regenerated by the host app's own asset build.

If you completed Step 12, an update can also touch the published React source. Re-publish it and rebuild:

php artisan vendor:publish --tag=textstem-react --force
npm run build

Review any files you've since customized (components/index.ts, page-templates/index.ts, public-layout.tsx) against the freshly-published versions before overwriting -- --force does not merge.

Review config/textstem.php in the package against your published config/textstemapp.php after each update and merge in any new keys.