Files
gui/pkgs/compiler/static-tests/tests/ssrThemeRepro.web.test.tsx
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

70 lines
1.7 KiB
TypeScript

import * as React from 'react'
import { expect, test } from 'vitest'
import { extractForWeb } from './lib/extract'
window['React'] = React
// regression for sandbox ssr-theme failure: tokens inside extracted
// $theme-* / $group-* blocks must resolve to var(--x) references — a raw
// "$color5" in the emitted CSS is an invalid declaration browsers drop,
// so the theme style silently never applies.
test('tokens inside $theme-* blocks resolve to CSS variables', async () => {
const output = await extractForWeb(
`
import { View } from '@hanzogui/core'
export function Test() {
return (
<View
width={100}
height={100}
boxShadow="0 2px 4px $shadowColor"
$theme-light={{
boxShadow: '0 4px 8px $color5',
}}
/>
)
}
`,
{
options: {
platform: 'web',
components: ['@hanzogui/core'],
},
}
)
const styles = output?.styles ?? ''
expect(styles).toContain('.t_light')
expect(styles).toContain('var(--color5)')
expect(styles).not.toContain('$color5')
})
// nested media-like keys inside a theme block can't extract in one pass —
// the whole prop must stay on the runtime path (kept as an inline JSX attr)
test('nested media inside $theme-* deopts to runtime', async () => {
const output = await extractForWeb(
`
import { View } from '@hanzogui/core'
export function Test() {
return (
<View
width={100}
$theme-dark={{
$sm: { backgroundColor: 'red' },
}}
/>
)
}
`,
{
options: {
platform: 'web',
components: ['@hanzogui/core'],
},
}
)
expect(output?.js ?? '').toContain('$theme-dark')
})