Files
gui/apps/gui.hanzo.ai/features/studio/api/generateThemeBuilderCode.ts
zeekayandHanzo Dev 69c6e860d7 transplant onto tamagui v2.6.0, brand as a re-runnable transform
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]>
2026-07-30 18:25:06 -07:00

98 lines
3.0 KiB
TypeScript

import { createPalettes, PALETTE_BACKGROUND_OFFSET } from '@hanzogui/theme-builder'
import type { BuildThemeSuiteProps } from '@hanzogui/themes'
type GenerateThemeBuilderCodeProps = BuildThemeSuiteProps & {
includeComponentThemes: boolean
includeSizeTokens: boolean
}
export async function generateThemeBuilderCode({
palettes,
includeComponentThemes,
}: GenerateThemeBuilderCodeProps) {
// side effect to getLastBuilder
const palettesOut = createPalettes(palettes)
function paletteToCreateThemes(pIn: string[]) {
return pIn.slice(PALETTE_BACKGROUND_OFFSET, -PALETTE_BACKGROUND_OFFSET)
}
// Convert accent palette array to named color object
function paletteToNamedColors(name: string, palette: string[]) {
return palette.reduce(
(acc, color, i) => {
acc[`${name}${i + 1}`] = color
return acc
},
{} as Record<string, string>
)
}
const darkPalette = paletteToCreateThemes(palettesOut.dark)
const lightPalette = paletteToCreateThemes(palettesOut.light)
const darkAccent = paletteToCreateThemes(palettesOut.dark_accent)
const lightAccent = paletteToCreateThemes(palettesOut.light_accent)
const componentThemesProp = includeComponentThemes
? `\n componentThemes: v5ComponentThemes,`
: `\n componentThemes: false,`
return `import { createV5Theme, defaultChildrenThemes } from '@hanzogui/config/v5'${includeComponentThemes ? `\nimport { v5ComponentThemes } from '@hanzogui/themes/v5'` : ``}
import { yellow, yellowDark, red, redDark, green, greenDark } from '@hanzogui/colors'
const darkPalette = ${arrayToJS(darkPalette)}
const lightPalette = ${arrayToJS(lightPalette)}
// Your custom accent color theme
const accentLight = ${JSON.stringify(paletteToNamedColors('accent', lightAccent), null, 2)}
const accentDark = ${JSON.stringify(paletteToNamedColors('accent', darkAccent), null, 2)}
const builtThemes = createV5Theme({
darkPalette,
lightPalette,${componentThemesProp}
accent: {
light: accentLight,
dark: accentDark,
},
childrenThemes: {
// Include default color themes (blue, red, green, yellow, etc.)
...defaultChildrenThemes,
// Semantic color themes for warnings, errors, and success states
warning: {
light: yellow,
dark: yellowDark,
},
error: {
light: red,
dark: redDark,
},
success: {
light: green,
dark: greenDark,
},
},
})
export type Themes = typeof builtThemes
// the process.env conditional here is optional but saves web client-side bundle
// size by leaving out themes JS. hanzogui automatically hydrates themes from CSS
// back into JS for you, and the bundler plugins set GUI_ENVIRONMENT. so
// long as you are using the Vite, Next, Webpack plugins this should just work,
// but if not you can just export builtThemes directly as themes:
export const themes: Themes =
process.env.GUI_ENVIRONMENT === 'client' &&
process.env.NODE_ENV === 'production'
? ({} as any)
: (builtThemes as any)
`
}
function arrayToJS(palette: string[]) {
return `[${palette.map((val) => {
return `'${val}'`
})}]`
}