Twelve example layouts imported `ZenSans` from `@hanzo/font/sans`, a name
the package stopped exporting at 1.9.0 — the family is called Zen, so the
binding is `Zen`. Every one of those layouts would fail to resolve the
import against a current install, and the `^1.8.x` ranges they pinned kept
resolving to the old export instead of surfacing it.
Twelve example apps opened with next/font/google Inter, so every developer who
copied one started their project on a face that is not ours and a request to a
font host we do not control. They use @hanzo/font's ZenSans (and ZenMono where
the example wanted a second family), with the dependency declared so it
resolves. examples/proposals bound --font-sans to var(--font-inter), a variable
nothing sets any more; it reads --font-zen-sans.
- Renamed all package dependencies from fumadocs-* to @hanzo/docs-*
- Updated imports in source files across all packages
- Fixed @hanzo/docs facade package configuration
- Restored missing bun.ts and types.ts from upstream
- Fixed mdx-remote to mdx-runtime references
- Core packages (@hanzo/docs-core, @hanzo/docs-mdx, @hanzo/docs-ui) building successfully
- Rename all packages from fumadocs-* to @hanzo/docs-*
- Update all imports across apps, examples, and packages
- Update documentation and content references
- Sync lockfile with new package names
zeekay
Fuma Nama