Skip to content

docs(data-objectstack): describe the real dependency contract, not a peer one - #4127

Merged
yinlianghui merged 1 commit into
mainfrom
claude/issue-3781-data-objectstack-docs-deps
Aug 10, 2026
Merged

docs(data-objectstack): describe the real dependency contract, not a peer one#4127
yinlianghui merged 1 commit into
mainfrom
claude/issue-3781-data-objectstack-docs-deps

Conversation

@yinlianghui

Copy link
Copy Markdown
Collaborator

Fixes#3781

Docs-only. Aligns content/docs/utilities/data-objectstack.mdx with the manifest as it is — the manifest is deliberately untouched, per the split ruling on the card.

Premise re-verified on origin/main = cfeb378b5

packages/data-objectstack/package.json:

  • no peerDependencies key at all — stronger than the card's "peerDependencies": {}, same conclusion: the package declares no peers;
  • @objectstack/client and @objectstack/spec are regular dependencies (alongside @object-ui/core and @object-ui/types);
  • react appears in no dependency field — only in keywords. grep -rn react packages/data-objectstack/src/ returns two prose comments naming the separate @object-ui/react package and nothing else, so the package imports React nowhere. Its dependency closure is React-free too: @object-ui/core and @object-ui/types both declare peerDependencies: {}.

Premise holds: the docs were wrong, the manifest was not.

The three sites

SiteBeforeAfter
:13 installnpm install @object-ui/data-objectstack @objectstack/clientnpm install @object-ui/data-objectstack
:16 note"is a peer dependency and must be installed separately""is a regular dependency ... nothing to install separately"
:456 bulletsclient and react both labelled (peer dependency)react bullet deleted outright; client relabelled

One addition beyond the card's three sites, from its own instruction to cross-check the whole page for dependency-contract prose: the Dependencies section listed only 2 of the package's 4 regular dependencies. Since the react bullet was being deleted from that exact list, the two omitted ones (@objectstack/spec, @object-ui/core) were added, so the section now matches the manifest line for line.

Page-wide cross-check

grep -i "peer" / "installed separately" over the file: the only surviving match is the new truthful sentence. Repo-wide, the only other peer-dependency prose in content/docs/ is guide/troubleshooting.md:70 ("ObjectUI packages declare React 18+ as a peer dependency") — left alone because it is true: 20+ packages do declare a react peer. data-objectstack is the headless adapter that correctly does not, which is exactly how the false bullet got copied onto this page.

Verification

GateResult
pnpm turbo run build --filter=@object-ui/site (Build Docs equivalent)29 successful, 29 total in 3m11s
node scripts/check-doc-links.mjsLinks are valid across 7 scan roots.
node scripts/check-control-bytes.mjsOK (scanned 3827 tracked text file(s); skipped 85 binary)
node scripts/check-changeset-presence.mjsNo source of a released package changed in this range, so no changeset is owed.

Rendered-output check on the built page (apps/site/.next/server/app/docs/utilities/data-objectstack.html): none of the three false claims render any more, and the four corrected bullets do. Changeset: none owed, per the presence script's own arbitration (docs-only, no released package src/ touched).

Out-of-scope findings (filed, not fixed here)

Not done, deliberately

The manifest-side half of #3781 — whether @objectstack/clientshould become a peer so hosts share one client instance — stays with the maintainer and was declined without measured pain. Today's change makes the docs true under the contract that ships now; if that ruling ever flips, the docs flip back as part of that change.


Generated by Claude Code

…peer one (#3781)
The page claimed `@objectstack/client` is a peer dependency that must be
installed separately, and listed a `react` peer dependency. Neither is true:
`packages/data-objectstack/package.json` declares no `peerDependencies` key at
all, carries `client` and `spec` as regular dependencies, and mentions `react`
only in `keywords` — the package is headless and imports React nowhere.
Three sites corrected:
- install line drops `@objectstack/client` (it resolves with the package);
- the "peer dependency ... must be installed separately" note becomes a
truthful one-liner;
- the Dependencies list drops the `react` bullet outright, relabels the
`client` bullet, and gains the two regular dependencies it had been
omitting (`@objectstack/spec`, `@object-ui/core`), so the section now
matches the manifest exactly.
Docs-only; the manifest is deliberately untouched per the maintainer's split
ruling on #3781 (whether `client` *should* be a peer was declined without
measured pain).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017Qqyix2QcnpUC9XeYVDzx3
@vercel

vercelBot commented Aug 10, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
ProjectDeploymentActionsUpdated (UTC)
objectuiIgnoredIgnoredAug 10, 2026 11:17am

Request Review

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

2 participants

@yinlianghui@claude