mirror of
https://github.com/hanzo-docs/docs.git
synced 2026-10-25 04:20:02 +00:00
zooqueenandHanzo Dev
ed3285d93d
Three things the workspace disagreed with itself about. Versions. apps/docs ran ahead on next 16.2.6 / react 19.2.6 / TS 6, the other 21 apps trailed on next 16.1.6 / react 19.2.3 / TS 5.9.3, and the packages sat somewhere between with five different @types/react pins. Everything is now on the newest patch of the line it was already on — react 19.2.8, next 16.2.12, @types/react 19.2.18, @types/react-dom 19.2.4 — and the TS-5 stragglers join the TS 6.0.3 the root and every package already used. No majors were invented: 6.0.3 IS the top of the 6.x line, and TS 7 is blocked because [email protected] declares `typescript: ^5.5.0 || ^6.0.0`. The duplicate key. next.config.mts declared `transpilePackages` twice in one object literal, so the later list won and @hanzogui/shell and @hanzo/brand had never been transpiled — the comment explaining why they must be outlived the setting it described. tsc had been reporting this the whole time as next.config.mts(193,3) TS1117; the app's `types:check` never reaches tsc (its script starts with a bare `@hanzo/docs-mdx`, which is not the bin's name and fails immediately), so nobody saw it. One list now, both groups in it. Dead weight. Twelve packages apps/docs declared and no file, config, script or browserslist field referenced: @radix-ui/react-dialog, @floating-ui/react-dom, @mixedbread/sdk, @orama/orama, openapi-sampler, react-remove-scroll, algoliasearch, gray-matter, tinyexec, tinyglobby, @types/three (types for a package that isn't installed) and shadcn (no components.json exists anywhere in the repo, so the CLI was never initialized). The ones that are real dependencies of packages/openapi, packages/core and packages/cli keep their own copies — pnpm's node_modules is isolated, so nothing lost a resolution. @orama/core stays: apps/docs/app/static.json/route.ts pulls OramaDocument through @hanzo/docs-core/search/orama-cloud, which types against it. Verified against a clean worktree at HEAD, since the working tree carries gigabytes of untracked synced project docs that CI never checks out: turbo build, apps + packages 43/52 before, 43/52 after, same 9 failures docs export 1764 html pages, byte-identical page count deploy.yml gate index/docs/services present, /docs has nav tsc --noEmit in apps/docs 325 errors before, 324 after (the TS1117) vitest 169 passed / 13 failed, both sides The 9 build failures and 13 test failures are unchanged from HEAD and none are version-related: 7 sibling apps cannot resolve @hanzo/mdx:collections/server under `next build --webpack`, zen-docs has a committed docs/server.ts importing a deleted zen5-coder-flash.mdx, and packages/preview cannot resolve its own @/lib/source alias under waku/vite. Co-authored-by: Hanzo Dev <[email protected]>