mirror of
https://github.com/projectsend/projectsend.git
synced 2026-09-18 01:25:09 +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>
84 lines
3.3 KiB
TypeScript
84 lines
3.3 KiB
TypeScript
import '../css/app.css';
|
|
|
|
import { createInertiaApp, router } from '@inertiajs/react';
|
|
import axios from 'axios';
|
|
import { resolvePageComponent } from 'laravel-vite-plugin/inertia-helpers';
|
|
import { createRoot } from 'react-dom/client';
|
|
import { route as routeFn } from 'ziggy-js';
|
|
import { initializeTheme } from './hooks/use-appearance';
|
|
import { xsrfCookieName } from './lib/xsrf';
|
|
|
|
declare global {
|
|
const route: typeof routeFn;
|
|
}
|
|
|
|
// Inertia sends every write through axios, which reads the CSRF token
|
|
// from a cookie it expects to be called `XSRF-TOKEN`. This installation
|
|
// names that cookie after itself so a neighbouring Laravel app on the same
|
|
// hostname cannot overwrite it — so axios has to be told. Without this,
|
|
// every write 419s the moment a neighbour answers a request.
|
|
axios.defaults.xsrfCookieName = xsrfCookieName();
|
|
|
|
/**
|
|
* The suffix on every browser tab title.
|
|
*
|
|
* Read from the shared props — the site name an administrator set — and
|
|
* never from `import.meta.env`. Vite resolves those at build time, and the
|
|
* published release ships `public/build/` already compiled, so whatever a
|
|
* build machine happened to have is frozen for every install downstream and
|
|
* no setting can move it afterwards. That is how 2.0.0 came to tell every
|
|
* visitor its tabs were "Laravel".
|
|
*/
|
|
let appName = 'ProjectSend';
|
|
|
|
const siteName = (page: { props: Record<string, unknown> }): string | null => {
|
|
const name = page.props.name;
|
|
|
|
return typeof name === 'string' && name !== '' ? name : null;
|
|
};
|
|
|
|
// Pages shipped by packages, re-keyed to look exactly like a host page
|
|
// (`./pages/<name>.tsx`) so resolvePageComponent finds them the same
|
|
// way — a one-time, generic extension point so a new package's pages
|
|
// just work without touching this file again.
|
|
//
|
|
// vendor/ is the only location globbed, and it covers both ways a
|
|
// package arrives: `composer require` puts a published package there,
|
|
// and a path repository (how a dev checkout consumes a local clone)
|
|
// symlinks the clone
|
|
// there too. Globbing packages/* as well, which this did at first,
|
|
// matched the dev checkouts' pages through both paths and emitted every
|
|
// package page into the bundle twice.
|
|
const packagePages: Record<string, () => Promise<unknown>> = {};
|
|
for (const [path, loader] of Object.entries(import.meta.glob('../../vendor/*/*/resources/js/pages/**/*.tsx'))) {
|
|
const match = path.match(/resources\/js\/pages\/(.+)$/);
|
|
if (match) packagePages[`./pages/${match[1]}`] = loader;
|
|
}
|
|
|
|
createInertiaApp({
|
|
title: (title) => `${title} - ${appName}`,
|
|
resolve: (name) => resolvePageComponent(`./pages/${name}.tsx`, { ...packagePages, ...import.meta.glob('./pages/**/*.tsx') }),
|
|
setup({ el, App, props }) {
|
|
// Before the first render, so the title callback below already has
|
|
// it when the initial page produces its <Head>.
|
|
appName = siteName(props.initialPage) ?? appName;
|
|
|
|
const root = createRoot(el);
|
|
|
|
root.render(<App {...props} />);
|
|
},
|
|
progress: {
|
|
color: '#4B5563',
|
|
},
|
|
});
|
|
|
|
// Renaming the site is a settings save like any other, so the new name
|
|
// arrives on the very next visit — without this the tabs would keep the
|
|
// old one until someone reloaded the page.
|
|
router.on('navigate', (event) => {
|
|
appName = siteName(event.detail.page) ?? appName;
|
|
});
|
|
|
|
// This will set light / dark mode on load...
|
|
initializeTheme();
|