mirror of
https://github.com/hanzoai/gui.git
synced 2026-10-25 02:31:41 +00:00
zeekayandHanzo Dev
69c6e860d7
This repo could never sync. There was NO merge-base with tamagui — 372 commits
here against 15,791 there, unrelated histories — because it began as a
copy-paste rebrand with a flattened layout. Every "sync" since was a hand
re-application that drifted, which is why the tree sat on 7.3.1 while upstream
shipped fixes we then rediscovered by hand.
This commit's PARENT IS TAMAGUI. A future sync is `git merge tama/main` then
`node scripts/rebrand.mjs` — a real merge, because the history is now shared.
174 packages: 166 upstream, our 8 restored (chrome, shell, telemetry, recipes,
get, font-geist-{sans,mono}, @hanzo/booker), bento-get gained. 170/170 build.
Our patches to files UPSTREAM ALSO OWNS are carried, which the package-level
delta missed and which was where the value actually was:
- useMedia's server snapshot (`initState ?? getMedia()`). Upstream still
returns undefined there, so every Tamagui Dialog kills a prerender — the
exact crash hanzo.app spent a day on.
- data-slot on web host nodes, absent upstream entirely.
Both applied ONTO upstream's newer files (it rewrote useMedia +150/-63 and
createComponent +160/-55), marked `PATCH (ours, carried across the transplant)`.
Seven traps are encoded in scripts/rebrand.mjs, each found by a gate:
skip itself and lockfiles; special-case the double-branded names in BOTH scoped
and bare form; map path strings, not just paths; drop a level for the flattened
group; check disk rather than a stale index.
Rust build artifacts are NOT committed. An earlier draft of this commit swept
apps/desktop/src-tauri/target/debug in via `git add -A` — 3,859 files including
a 272MB .a, over GitHub's 100MB cap, so the push could never have landed. They
are gitignored now.
Co-Authored-By: Hanzo Dev <[email protected]>
28 lines
987 B
TypeScript
28 lines
987 B
TypeScript
// runs once on server boot — see vite.config.ts `setupFile.server`
|
|
|
|
// RAILWAY_DEPLOYMENT_ID is only present on Railway — guards against purging
|
|
// from local prod builds
|
|
if (process.env.NODE_ENV === 'production' && process.env.RAILWAY_DEPLOYMENT_ID) {
|
|
const { CF_API_KEY, CF_EMAIL, CF_ZONE_ID } = process.env
|
|
if (CF_API_KEY && CF_EMAIL && CF_ZONE_ID) {
|
|
fetch(`https://api.cloudflare.com/client/v4/zones/${CF_ZONE_ID}/purge_cache`, {
|
|
method: 'POST',
|
|
headers: {
|
|
'X-Auth-Email': CF_EMAIL,
|
|
'X-Auth-Key': CF_API_KEY,
|
|
'Content-Type': 'application/json',
|
|
},
|
|
body: JSON.stringify({ purge_everything: true }),
|
|
})
|
|
.then(async (res) => {
|
|
const body = await res.text()
|
|
if (!res.ok) {
|
|
console.warn(`[cf-purge] failed ${res.status}: ${body}`)
|
|
return
|
|
}
|
|
console.info('[cf-purge] cache purged on boot')
|
|
})
|
|
.catch((err) => console.warn('[cf-purge] error:', err))
|
|
}
|
|
}
|