mirror of
https://github.com/projectsend/projectsend.git
synced 2026-09-17 09:05:08 +00:00
Ignacio Nelson
0e3f7d5c68
The tab title suffix came from `import.meta.env.VITE_APP_NAME`, with the starter kit's own `|| 'Laravel'` behind it. Vite resolves that at build time, and a release ships public/build/ already compiled — precisely so nobody downstream needs npm — so whatever the build machine had is frozen for every install that artifact produces. The 2.0.0 zip has `const s2="Laravel"` in app-BoPagLMd.js, and no APP_KEY, APP_NAME or VITE_APP_NAME an operator sets afterwards can reach it (#1619). Swapping the fallback to 'ProjectSend' would fix the reported symptom and leave the mechanism: a name baked at build time, wrong for anyone who renamed their site. The name is already on every page — the shared props carry the site_name setting — so read it from there and drop the build-time variable entirely, .env.example's dead VITE_APP_NAME line included. The root view's own <title> now reads the same shared prop, so the tab does not show one name before hydration and another after on any installation whose administrator renamed the site. Verified in a real browser, which is the only place this is visible — the server-rendered title was always right, and curl never saw the bug. Titles read "Log in - ProjectSend" and, after renaming the site with no rebuild of any kind, "Log in - Acme Files". Co-authored-by: Claude Opus 5 <noreply@anthropic.com>