mirror of
https://github.com/hanzoai/gui.git
synced 2026-10-25 02:31:41 +00:00
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]>
51 lines
1.3 KiB
Plaintext
51 lines
1.3 KiB
Plaintext
---
|
|
title: Errors
|
|
description: Common error messages and how to resolve them
|
|
---
|
|
|
|
### Error 001
|
|
|
|
Haven't called createGui yet.
|
|
|
|
This often happens due to having duplicate Gui sub-dependencies.
|
|
|
|
Gui needs every `@hanzogui/*` dependency to be on the exact same version, we
|
|
include an upgrade script with the starter kits that you can call with "yarn
|
|
upgrade:hanzogui" to help with this.
|
|
|
|
You may want to clear your node_modules as well and run a fresh install after
|
|
upgrading.
|
|
|
|
### Error 002
|
|
|
|
Using global config fallback. This may indicate duplicate hanzogui instances
|
|
(e.g., from Vite SSR bundling). This is handled automatically, but may cause
|
|
issues due to duplicate hanzogui modules if ignored.
|
|
|
|
### Warning 001
|
|
|
|
#### Ignorable modules
|
|
|
|
This error means the compiler can't bundle some dependencies into what it reads
|
|
at compile-time in order to optimize. It's not necessarily an error and usually
|
|
won't de-opt.
|
|
|
|
To see a full stack trace set:
|
|
|
|
```bash
|
|
DEBUG=hanzogui
|
|
```
|
|
|
|
To disable the warning you can set:
|
|
|
|
```bash
|
|
GUI_IGNORE_BUNDLE_ERRORS=some_module_name,some_other_module_name
|
|
# Or to disable them all (not recommended):
|
|
GUI_IGNORE_BUNDLE_ERRORS=true
|
|
```
|
|
|
|
### Warning 002
|
|
|
|
You're rendering a Gui <Adapt /> component without nesting it inside a
|
|
parent that is able to adapt.
|