Files
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

61 lines
2.0 KiB
TypeScript

import { expect, test } from '@playwright/test'
test.describe('SSR Theme Styles', () => {
test('$theme-light generates proper CSS classes', async ({ page }) => {
await page.goto('/ssr-test')
// wait for render
const box = page.getByTestId('theme-light-box')
await expect(box).toBeVisible({ timeout: 15000 })
// the theme rule is compile-time extracted; in dev vite injects the CSS
// client-side after hydration, so wait on the stylesheet instead of racing
// it by reading page.content() at first paint
const themeRule = await page.waitForFunction(
() => {
for (const sheet of document.styleSheets) {
try {
for (const rule of sheet.cssRules) {
const text = rule.cssText || ''
// the extracted theme-scoped boxShadow rule specifically (not the
// theme variable definitions, which also mention .t_light)
if (text.includes('.t_light') && text.includes('_bxsh-_light_')) {
return text
}
}
} catch {}
}
return null
},
undefined,
{ timeout: 15000 }
)
// the declaration must survive browser CSS parsing — an unresolved token
// like "$color5" makes the browser drop it, leaving an empty rule
const ruleText = (await themeRule.jsonValue()) as string
expect(ruleText).toContain('.t_light')
expect(ruleText).toContain('box-shadow')
const boxClasses = await box.getAttribute('class')
console.log('Box classes:', boxClasses)
// should have a _light_ prefixed class for the theme-specific style
expect(boxClasses).toMatch(/_light_/)
})
test('no hydration mismatch with JS enabled', async ({ page }) => {
const errors: string[] = []
page.on('console', (msg) => {
if (msg.type() === 'error' && msg.text().includes('Hydration')) {
errors.push(msg.text())
}
})
await page.goto('/ssr-test')
await page.waitForTimeout(1000)
expect(errors).toHaveLength(0)
})
})