docs: Share provider-with-managers setup across API pages

[ntucker]

Requested by Nathaniel · project thread

Includes #4145.

Motivation

Six API pages each carried their own copy of the "pass managers to the provider" setup: a 100+ line Web / React Native / NextJS / Expo tab block for React (LogoutManager, Manager) or a single web snippet (Controller, DevToolsManager ×2, PollingSubscription, getDefaultManagers), plus a Vue main.ts beside each. The installation page hand-wrote the same root files again. The copies had drifted (ReactDOM.render, unused imports, NextJS layout titled _layout.tsx).

Solution

website/src/components/providerSetup.mjs generates one platform's setup file (web, native, nextjs, expo, vue). ProviderSetupCode.tsx renders it on the site, and the skill-reference / llms.txt generator (docsToMarkdown.mjs) uses it too, so agents see the same code. Two partials use it:

• docs/core/shared/_provider_managers.mdx: React platform tabs + Vue main.ts for a page's managers block. Used by LogoutManager, Manager, DevToolsManager, PollingSubscription, getDefaultManagers and Controller.
• docs/core/shared/_installation.mdx (docs: Generate installation provider setup tabs from ProviderSetupCode #4145): the same tabs without managers. Installation-only extras (Anansi tab, redux links, NextJS guide button) stay as MDX around it.

Before (LogoutManager.md, ~170 lines):

:::react

<Tabs groupId="platform" ...>
<TabItem value="web">

```tsx title="/index.tsx"
import { DataProvider, LogoutManager, getDefaultManagers } from '@data-client/react';
import ReactDOM from 'react-dom';

const managers = [new LogoutManager(), ...getDefaultManagers()];

ReactDOM.createRoot(document.body).render(...);
```

</TabItem>
<!-- React Native, NextJS, Expo tabs... -->
</Tabs>

:::

:::vue

```ts title="main.ts"
...
```

:::

After:

import ProviderManagers from '../shared/_provider_managers.mdx';

<ProviderManagers imports={['LogoutManager', 'getDefaultManagers']}>

```ts
// highlight-next-line
const managers = [new LogoutManager(), ...getDefaultManagers()];
```

</ProviderManagers>

• The managers block is read with the playground's existing parseCodeDocuments. Highlight comments carry through, and an import at the top of the block (Controller's unAuth) continues the generated import list.
• Every page that used only a web snippet now gets all four React platform tabs.
• docsToMarkdown.mjs now passes a partial its page's code block and evaluates JSX spreads ({...props}); skill references are regenerated.

Verified with a full website production build, the rendered /docs/... and /vue/... pages and their generated markdown, and yarn build:skills --check. Website typecheck and lint pass. Docs only, so no changeset.

🤖 Generated with Claude Code

https://claude.ai/code/session_01DE1vvoaeNDUbYnk4ewofap

---

Note

Low Risk
Documentation and doc-build tooling only; no library runtime or auth behavior changes.

Overview
Deduplicates DataProvider / DataClientPlugin setup examples across API and installation docs by generating platform-specific snippets from one shared module.

Adds providerSetup.mjs and ProviderSetupCode, plus _provider_managers.mdx, so pages only supply a short managers code block (and optional imports) instead of repeating Web / React Native / Next.js / Expo / Vue tab content. LogoutManager, Manager, Controller, DevToolsManager, PollingSubscription, and getDefaultManagers are refactored to use this partial; installation uses the same generator without managers.

Updates docsToMarkdown.mjs to render ProviderSetupCode, forward partial children, and evaluate JSX spreads so regenerated agent skill references match the live site. Vue installation copy is tightened (default app.use(DataClientPlugin) with options described in prose).

^{Reviewed by Cursor Bugbot for commit fa82596. Bugbot is set up for automated code reviews on this repo. Configure here.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: fa82596

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

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

Project	Deployment	Actions	Updated
docs-site	Ready	Preview	Oct 5, 2026 11:37pm UTC

[ntucker]

One actionable issue in the validation triggers for the new shared snippet generator.