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

**URL:** https://discourse.roots.io/t/vite-still-wants-to-load-from-dev-url-after-building-and-deploying-my-sage-11-project/29833
**Category:** sage
**Created:** 2025-08-10T14:34:56Z
**Posts:** 5

## Post 1 by @tkohlmann21 — 2025-08-10T14:34:56Z

Hi

I have the Problem that after running yarn build and deploying to my Webserver, my css/js/vite still tries to load from my Dev url.  
How can i fix that.

Thx for helping me out

---

## Post 2 by @ben — 2025-08-10T15:01:27Z

> [@Deploying while Vite dev server is active causes broken URLs due to public/hot file existing](https://discourse.roots.io/t/deploying-while-vite-dev-server-is-active-causes-broken-urls-due-to-public-hot-file-existing/29601):
>
> 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…

---

## Post 5 by @ben — 2025-08-10T19:45:01Z