Vite still wants to load from dev url after building and deploying my Sage 11 Project

[ben]

Deploying while Vite dev server is active causes broken URLs due to public/hot file existing

I’m using the full Roots stack (Trellis, Bedrock, Sage 11 with Vite). Everything works fine locally, but I’ve run into a problem when deploying. If I have the dev server running (npm run dev) at the time of deployment, the file web/app/themes/sage/public/hot is present in my local project and gets synced to the production server via Trellis (synchronize task). This file causes Sage to load assets from http://[::1]:5173, which completely breaks the site in production: I get CORS errors, fonts f…