Missing Vite assets after Laravel deployment

[nickbasham]

I'm pulling my hair out about this, and just hoping someone has run into a similar issue or has some ideas to point me in the right direction.

I have a Laravel app using Vite and the Laravel Vite plugin to build and package my javascript and scss/css assets. My initial deployments worked fine, but the past few times I've attempted to deploy, the assets linked in the final HTML don't match the filenames of the built assets, so they 404 and it effectively breaks the site. I'm able to perform a rollback, which corrects the issue, but when I attempt to deploy again, I run into the same issue and have to rollback again. I tried php artisan cache:clear and php artisan view:clear, to see if something from a previous release was getting carried over, but it had no effect.

I thought it might be a configuration issue with my server (a VPS at Dreamhost), so I created a new dev environment on it and was able to deploy to it without any issues. I did a bunch of deploys to it, too – editing views and css/js assets, testing rollbacks, etc., and all was working flawlessly.

So at this point, I just can't figure out why deployments to my prod environment are ending up with broken links to Vite assets, but deployments to my dev environment are working fine. Both environments are on the same server with a nearly identical .env, and running against the same commit. If it's a cache issue, I'm not sure why I'm not running into the same issue in both environments.

Any pointers/guidance would be greatly appreciated, thanks in advance!

[antonmedv]

Well, figure out which assets is served and why. Use -v during deployment.

Seems easy)

[nickbasham]

Appreciate your quick reply @antonmedv, and especially for all your work on this great tool. I was unaware of the -v flag (pretty obvious thing I should have tried, but just didn't think of it), so I did run that. One detail I forgot to include above is that I was running the vite build step on the server – I think I had the task order wrong, and then the rendered blade views were referencing an old asset.

After sleeping on it, I realized I should just run the build step locally and upload, avoiding npm install && npm run build on the server completely. After tweaking my deployer config with the new task, all seems to be working now.

Thanks again!