@jfrader/storybook-docs 0.0.0-stage → 0.4.4

package/docs/CONFIG.md

@@ -0,0 +1,287 @@
+# Configuration reference
+
+The consumer contract is `StorybookDocsConfig` in `src/config.ts`. Export a plain
+object from `docs.config.mjs` and pass it to `storybookDocs({ config })` in Vite.
+Only `site` and `stories` are required. Defaults below describe the current engine,
+not values copied from the reference consumer.
+
+## Site and stories
+
+| Key | Type | Default | Effect |
+| --- | --- | --- | --- |
+| `site` | object | Required | Branding and header content. |
+| `site.title` | `string` | Required | Header brand and overview heading. |
+| `site.mark` | `string` | First character of `site.title`, uppercased | Header mark. |
+| `site.tagline` | `string` | Built-in paragraph about generated documentation | Overview introduction. |
+| `site.links` | `Array<{ label: string; href: string }>` | `[]` | Header links. `label` is the visible text; `href` is the destination; both are required per item. |
+| `stories` | object | Required | Story discovery source. |
+| `stories.from` | `string` | Required | Installed package name, absolute directory, or relative directory holding story sources. |
+| `stories.pattern` | `string` | Required | Glob relative to the story root, for example `src/components/*/*.stories.tsx`. Matches determine navigation, examples and API tables. |
+
+Package roots are resolved by walking up from the consumer root for
+`node_modules/<package>`. Relative paths resolve against the Vite project root
+(normally the directory containing the config), not the engine's directory.
+The plugin option `root?: string` overrides that consumer root; it is not a
+`StorybookDocsConfig` key. Keep the config and Vite root together, or set `root`
+explicitly. Published packages must include their story sources, or
+`stories.from` must point at a checkout. The scanner supports `*` within one path
+segment and `**` across directories.
+
+### Authored documentation already in the stories
+
+The following authored documentation parameters are rendered without a second copy of the prose:
+
+| Storybook parameter | Where it appears |
+| --- | --- |
+| `parameters.docs.description.component` | Page introduction under the title. |
+| `parameters.docs.description.story` | Blurb on that story's example. |
+| `parameters.docs.usage` | Usage section, rendered as Markdown (headings, lists, tables, callouts) above the examples. |
+| `parameters.docs.source.code` | The example's Code panel, and the page-level snippet when authored, instead of the snippet derived from default arguments. |
+| `parameters.docs.source.language` | Language id handed to the consumer's code renderer; the derived snippet is `tsx`. |
+| `tags: ['!autodocs']` | Story is left off docs pages, as in Storybook. Meta and story tags both apply. |
+
+Meta parameters apply to every story; a story's own parameters win.
+
+### Rendering code with the design system's own block
+
+Code renders in the engine's plain block unless the consumer names a renderer:
+
+```js
+export default {
+  // …
+  code: { module: './src/code.tsx' },
+};
+```
+
+```tsx
+// src/code.tsx — the module's default export receives { code, language, label }.
+// `label` is optional and names the panel for assistive tech; forward it to your renderer
+// (a design system's code block usually takes a `label`) so a page with many examples does not
+// expose several landmarks with the same name.
+import { CodeBlock } from '@acme/ui';
+import { loadShikiHighlight } from '@acme/ui/code-block/shiki';
+
+export default function Code({ code, language }: { code: string; language?: string }) {
+  return <CodeBlock code={code} language={language} highlight={loadShikiHighlight} copyable />;
+}
+```
+
+The same renderer is used for the page snippet, every example's Code panel and every fenced block
+in authored Markdown. A design system that highlights code opt-in per component (a `highlight`
+loader, as Storybook does) wires it here once for the whole docs site. If the renderer throws, that
+block falls back to plain text rather than failing the page.
+
+## Groups
+
+| Key | Type | Default | Effect |
+| --- | --- | --- | --- |
+| `groups` | object | Omitted | Optional ordering and display-name changes. |
+| `groups.order` | `string[]` | See below | Places named groups first, in this order. Unlisted groups follow; components within a group sort by name. |
+| `groups.rename` | `Record<string, string>` | `{}` | Maps authored group names to display names before sorting. Use renamed names in `order`. |
+
+Default order: `Getting started`, `Foundations`, `Actions`, `Forms`, `Inputs`,
+`Data display`, `Feedback`, `Navigation`, `Surfaces`, `Pickers`, `Layout`,
+`Content`, `Components`. Passing `[]` disables this preferred order.
+Groups and component names come from story meta titles such as `Inputs/Button`;
+there is no separate component registry.
+
+## Theme
+
+| Key | Type | Default | Effect |
+| --- | --- | --- | --- |
+| `theme` | object | Omitted | Optional bridge from docs chrome to consumer theme. |
+| `theme.attribute` | `string` | `'data-theme'` | Attribute set on `document.documentElement` by the theme toggle. |
+| `theme.values` | `[string, string]` | `['dark', 'light']` | Initial and alternate theme attribute values, also used as toggle labels. |
+| `theme.vars` | `Partial<Record<ThemeRole, string>>` | `{}` | CSS values assigned to the engine's semantic roles. Unmapped roles keep the defaults in `src/styles.css`. |
+
+Each value is a complete CSS value, typically `var(--acme-bg)`, not a bare custom
+property name. These are all supported `ThemeRole` keys (each is an optional
+`string`, with the corresponding stylesheet role as its fallback):
+
+| Key | CSS property | Role |
+| --- | --- | --- |
+| `theme.vars.bg` | `--sd-bg` | Page background. |
+| `theme.vars.surface` | `--sd-surface` | Cards and panels. |
+| `theme.vars.surfaceRaised` | `--sd-surface-raised` | Raised surfaces. |
+| `theme.vars.surfaceHover` | `--sd-surface-hover` | Hovered surfaces. |
+| `theme.vars.border` | `--sd-border` | Standard boundaries. |
+| `theme.vars.borderSubtle` | `--sd-border-subtle` | Subtle separators. |
+| `theme.vars.text` | `--sd-text` | Primary text. |
+| `theme.vars.textMuted` | `--sd-text-muted` | Secondary text. |
+| `theme.vars.textSubtle` | `--sd-text-subtle` | Low-emphasis text. |
+| `theme.vars.accent` | `--sd-accent` | Accent surfaces and decoration. |
+| `theme.vars.accentText` | `--sd-accent-text` | Accent text. |
+| `theme.vars.accentSoft` | `--sd-accent-soft` | Subdued accent surfaces. |
+| `theme.vars.accentContrast` | `--sd-accent-contrast` | Text on accent surfaces. |
+| `theme.vars.danger` | `--sd-danger` | Error boundaries and tinted callouts. |
+| `theme.vars.dangerText` | `--sd-danger-text` | Danger **text**; use a tone that passes 4.5:1 on your surface (axe checks it). |
+| `theme.vars.focusRing` | `--sd-focus-ring` | Keyboard focus outlines. |
+
+## Tokens and guidance
+
+| Key | Type | Default | Effect |
+| --- | --- | --- | --- |
+| `tokens` | object | Omitted | Enables Foundations navigation. Without it the virtual token object is `{}`. |
+| `tokens.varsModule` | `string` | Required when `tokens` is supplied | Module specifier exporting the token object. |
+| `tokens.varsExport` | `string` | `'vars'` | Named export to read from that module. |
+| `tokens.css` | `string[]` | `[]` | CSS module specifiers imported globally, in order, after engine styles. |
+| `guidance` | object | Omitted | Optional Markdown prose; without it no authored content loads. Component pages can still show their built-in placeholder. |
+| `guidance.dir` | `string` | Required when `guidance` is supplied | Directory resolved against the consumer root. Files named `<component-slug>.md` render on that component's page; `index.md` renders on the overview. A missing directory or file loads no authored content. |
+
+Foundations read string-valued maps from the exported token object: `color`;
+`font`, `fontWeight`, `textSize`; `space`, `radius`, `size`; and `shadow`,
+`motion.duration`, `motion.ease` (or `motion.easing`). Values can be CSS variable
+references. Missing maps produce empty sections, not a crash. Guidance is authored
+Markdown rendered with `marked`; there is no built-in prose editor.
+
+## Page switches
+
+| Key | Type | Default | Effect |
+| --- | --- | --- | --- |
+| `pages` | object | Omitted | Optional switches. |
+| `pages.overview` | `boolean` | `true` | Exposed in page settings; currently the shell still shows the overview link and fallback route when `false`. |
+| `pages.color` | `boolean` | `true` with tokens, otherwise `false` | Shows Color in Foundations navigation. |
+| `pages.typography` | `boolean` | `true` with tokens, otherwise `false` | Shows Typography in Foundations navigation. |
+| `pages.spacing` | `boolean` | `true` with tokens, otherwise `false` | Shows Spacing & shape in Foundations navigation. |
+| `pages.effects` | `boolean` | `true` with tokens, otherwise `false` | Shows Elevation & motion in Foundations navigation. |
+| `pages.api` | `boolean` | `true` | Exposed in page settings; currently component pages still show API tables when `false`. |
+
+Setting a Foundations switch to `true` does not enable it without
+`tokens.varsModule`. These switches hide navigation entries, not direct routes.
+
+## Add your design system in five minutes
+
+Use a docs app with React, React DOM, Vite, `@vitejs/plugin-react`, this engine,
+and your design system installed. Add these four files, matching the README's
+consumer contract:
+
+1. **`docs.config.mjs`** — point at the story sources:
+
+   ```js
+   export default {
+     site: { title: 'acme/ui', mark: 'a' },
+     stories: { from: '@acme/ui', pattern: 'src/components/*/*.stories.tsx' },
+     // Optional: tokens: { varsModule: '@acme/tokens/vars', css: ['@acme/tokens/tokens.css'] },
+     // Optional: guidance: { dir: './guidance' },
+   };
+   ```
+
+2. **`vite.config.ts`** — register the engine and React plugins:
+
+   ```ts
+   import react from '@vitejs/plugin-react';
+   import { defineConfig } from 'vite';
+   import { storybookDocs } from '@jfrader/storybook-docs/vite';
+   import config from './docs.config.mjs';
+
+   export default defineConfig({ plugins: [storybookDocs({ config }), react()] });
+   ```
+
+3. **`index.html`** — mount the app:
+
+   ```html
+   <!doctype html>
+   <html lang="en">
+     <head><meta charset="UTF-8"><title>acme/ui docs</title></head>
+     <body><div id="root"></div><script type="module" src="/src/main.tsx"></script></body>
+   </html>
+   ```
+
+4. **`src/main.tsx`** — start the engine:
+
+   ```ts
+   import { start } from '@jfrader/storybook-docs';
+   start();
+   ```
+
+Run `pnpm exec vite` in the docs app. Match your stories' JSX runtime and install
+their imports in the consumer. The reference consumer is `examples/jfrader-ui`.
+
+### When the design system is linked rather than installed
+
+Stories are rendered from the design system's own files, so its imports resolve
+next to those files, not next to your app. Three things follow, and all three
+show up as stories that render wrong rather than as errors:
+
+- **Dedupe the styling runtime.** If the design system ships its own copy of
+  Emotion, styled-components or similar, a story that provides a cache or reads
+  a context sees a different instance than the components do. Add the runtime to
+  `resolve.dedupe` in the consumer so it resolves from your app.
+- **Provide optional peers.** A story may import a package the design system
+  treats as optional (its own Storybook installs it, your app does not). Install
+  it in the consumer and dedupe it too; an unresolved import fails the whole
+  story module, not just the story.
+- **Generate the design system's CSS.** Token CSS is usually generated and
+  gitignored, so a linked checkout can hold a build from before your tokens
+  changed. Regenerate it before `vite` (`pnpm --dir <design-system>/packages/tokens
+  generate` in the reference setup). A stale file loses variables silently:
+  every component that sizes itself from a token collapses to zero.
+
+## Known limits
+
+- Compound parts hidden from docgen (including `Object.assign` compounds and
+  `Dialog.Content = …`) rely on exported `*Props` types. Parts without exported
+  props types remain invisible.
+- Meta and story args, globals, argTypes and parameters are composed with story-level precedence.
+  Parameters and argTypes merge recursively; arrays replace rather than concatenate.
+  Explicit args win over deprecated argType defaults. Docgen defaults describe controls only;
+  they are not evaluated or passed into the component. Render functions receive the composed
+  context, and decorators can call `Story({ args })` to override arguments.
+- Controls support boolean, number, text/string, select, radio/inline-radio (as a select),
+  range and object (JSON, applied on blur). ArgType mappings apply to rendered arguments.
+  Custom renders accept controls too. Check/inline-check, multi-select, color, date and file
+  editors are not provided; their authored args still render unchanged.
+- Story `name` supplies the example heading; export names remain the stable identifiers.
+  `!dev` and `!test` affect Storybook's sidebar/test runner, not this docs front.
+  Custom tags have no filtering effect here. `!autodocs` hides docs examples.
+- Meta and story decorators are applied in Storybook's order. Project-level
+  decorators from `.storybook/preview` are not recreated: theme, global styles
+  and layout come from the docs config instead. A story that throws shows its
+  error in place rather than disappearing.
+- Play functions and accessibility checks do not run here. Loaders and beforeEach hooks
+  are not executed: test hooks can modify clocks, preferences and shared browser state,
+  which cannot safely be isolated across simultaneous examples. Affected frames show a notice.
+  Loader-dependent examples may not render correctly. Project globals/initialGlobals and
+  Storybook-specific context APIs (hooks, canvas, mount, step) are not recreated.
+  Addon parameters such as viewport and backgrounds are not applied; viewport frames show
+  a notice. Layout supports centered, padded and fullscreen (an unpadded docs frame,
+  not a separate viewport-sized canvas).
+- Search scans the in-memory catalog's component, group and story names. There is
+  no generated full-text search index for guidance, props or rendered content.
+
+### Checking a running site
+
+The engine ships a frame check for the thing unit tests cannot see: whether the examples a docs site
+renders are actually right. From a directory where `playwright` resolves:
+
+```bash
+node scripts/check-example-frames.mjs http://localhost:4320 [--json report.json]
+```
+
+It reports stories that fail to render (including modules that never loaded), content painted outside
+its frame, zero-size interactive controls, and component roots that collapsed to nothing. Invisible
+helpers — measure probes, closed dialogs, top-layer overlays, aria-hidden duplicates — are ignored, so
+findings are real. Exit code is 1 when a component has a finding.
+
+## Verification and CI
+
+From the engine root, run `pnpm test`, `pnpm typecheck` (engine and tests), and
+`pnpm build` (the reference consumer). The reference consumer's link dependencies
+expect a sibling `jfrader-ui` checkout, with UI dependencies installed and token
+CSS generated: run `pnpm --filter @jfrader/ui... install --frozen-lockfile --prefer-offline`
+then `pnpm --filter @jfrader/tokens generate` in that checkout, and
+`pnpm --dir examples/jfrader-ui install --frozen-lockfile --prefer-offline` in the
+engine checkout.
+
+CI runs on pushes and pull requests targeting `master`. It uses Node 22.23.3 (the
+`engines.node` minimum major), the root's pinned `pnpm@10.12.1`, cached package
+downloads and frozen, prefer-offline installs. It tests and typechecks before
+checking out the reference design system at
+`c990db09c143a183f5666d404c35cf2fe324cf9d`, installing its UI/token dependencies,
+generating tokens, installing the consumer and running the build.
+
+Set the repository secret `REFERENCE_UI_TOKEN` to a token with read-only contents
+access to `jfrader/jfrader-ui`. Checkout does not persist its credentials.
+Fork PRs do not receive this secret and fail the credential check; verify them on
+a trusted branch instead. CI never uses `pull_request_target` to run PR code with
+elevated permissions.

package/docs/RELEASING.md

@@ -0,0 +1,153 @@
+# Publishing @jfrader/storybook-docs
+
+## Check a release
+
+Use Node 22.18+ for the maintainer's TypeScript tests and the pinned `pnpm@10.12.1`.
+Use Node 24 and npm 11.18.0 for publishing, matching `publish.yml`.
+
+```bash
+pnpm install --frozen-lockfile
+pnpm test
+pnpm typecheck
+pnpm build:package
+pnpm smoke:package
+```
+
+The smoke command runs `pnpm pack` (including `prepack`), prints and checks the
+tarball contents, installs that tarball with npm into a temporary directory under
+`node_modules`, and typechecks/builds a synthetic consumer. It checks both public
+entries, all virtual declarations without `skipLibCheck`, and emitted engine CSS.
+It needs registry access and `tar`; it removes the temporary directory on success
+or failure. It uses the installed development versions of React, Vite and TypeScript,
+not a peer-version matrix. It does not run a browser.
+
+Both checkout and tarball exports currently point at `dist`, not `src`. Linked
+consumers must rebuild the engine after edits. The browser entry imports its CSS
+automatically and its declaration references `virtual.d.ts`; consumers importing
+the root entry need no extra CSS import or triple-slash reference. A consumer
+importing virtual modules alone must also import a type from the root entry to load
+those ambient declarations. The Node-only plugin remains at `@jfrader/storybook-docs/vite`.
+
+## First publish: the owner's interactive login
+
+Trusted publishing is configured in an existing npm package's settings. If the
+package does not exist yet, the owner must create it by publishing locally first.
+
+1. Confirm the checkout is the reviewed release commit on `master` and clean.
+   Check `npm view @jfrader/storybook-docs versions --json --registry=https://registry.npmjs.org`.
+   An `E404` can mean the public package does not exist yet. If `0.2.1` already
+   exists, do not retry that version: npm versions are immutable.
+2. Run the checks above. Pack the release outside the checkout:
+
+   ```bash
+   release_dir=$(mktemp -d /tmp/opencode/storybook-docs-release-XXXXXX)
+   pnpm pack --pack-destination "$release_dir"
+   tar -tzf "$release_dir"/*.tgz
+   npm login --registry=https://registry.npmjs.org
+   npm whoami --registry=https://registry.npmjs.org
+   npm publish "$release_dir"/*.tgz --access public --registry=https://registry.npmjs.org
+   ```
+
+   `whoami` must be the owner (`jfrader`) or an authorized package maintainer.
+   Complete npm's interactive 2FA challenge. `EOTP` means authorization requires
+   a fresh second factor; it is not a build failure. Retry interactively with a
+   fresh code/challenge, never disable 2FA or commit an OTP/token. If needed, npm's
+   `--otp` option accepts a fresh code, but keep it out of shared shell history.
+   Do not request `--provenance` from a local shell: local publishing has no
+   supported CI OIDC identity. This initial version will lack CI provenance.
+3. Verify `npm view @jfrader/storybook-docs@0.2.1 version dist.integrity --registry=https://registry.npmjs.org`.
+   Delete the temporary release directory when finished.
+4. Do not push a `v0.2.1` tag after publishing it manually: the tag workflow would
+   try to publish the same immutable version again. Configure trust before the next
+   release; its new version/tag is the first automated publish.
+
+## Later publishes: trusted publishing (recommended)
+
+On npmjs.com, open the package's **Settings → Trusted publishing** and add GitHub
+Actions with these exact, case-sensitive values:
+
+| Field | Value |
+| --- | --- |
+| Organization or user | `jfrader` |
+| Repository | `storybook-docs` |
+| Workflow filename | `publish.yml` (not `.github/workflows/publish.yml`) |
+| Environment name | Leave empty; this workflow has no environment |
+| Allowed actions, if shown | Allow direct `npm publish` |
+
+The workflow uses GitHub-hosted Ubuntu, Node 24, npm 11.18.0, `id-token: write`,
+and `npm publish --provenance`. It needs no `NPM_TOKEN` or `NODE_AUTH_TOKEN`.
+If npm shows a validation deadline for a new trust configuration, complete an
+unpublished release within that deadline (currently two days), or recreate the
+configuration. After validating trust, select **Require two-factor authentication
+and disallow tokens** in the package's Publishing access settings. OIDC still works.
+
+For each release:
+
+1. Choose a new, unpublished version. Update `package.json` without creating a
+   tag (`npm version <version> --no-git-tag-version`), reconcile the pnpm lockfile
+   if needed, and run the checks above. Review and merge the version commit to
+   `master` through the repository's normal review process.
+2. From the merged, clean `master` commit, create and push its matching tag:
+   `git tag v<version>` then `git push origin v<version>`.
+3. Watch **Publish package** in GitHub Actions. The workflow rejects a tag/version
+   mismatch or a release commit not contained in `origin/master`, then checks,
+   packs and publishes. Confirm the registry version, integrity and provenance.
+
+`workflow_dispatch` also publishes; it is not a dry run. Dispatch only an
+unpublished version from a reviewed commit contained in `master`. Rerunning a
+successful publish fails because that version already exists.
+
+## Token publishing: explicit fallback, not the current configuration
+
+The committed workflow uses OIDC only. A token secret alone will not make it use
+token authentication. If trusted publishing cannot be used, a maintainer must
+explicitly change the publish step to supply `NODE_AUTH_TOKEN` from a repository
+secret. Use a short-lived granular token restricted to this package with publish
+permission and **Bypass 2FA** enabled; ordinary tokens trigger `EOTP` in CI. The
+package's publishing access must permit such tokens. Account/organization policy
+may forbid this fallback. Never put an interactive OTP into CI, never use a
+read-only token for publishing, and remove/revoke the write token after moving
+to OIDC. Keep `--provenance` and GitHub-hosted runners for the fallback too.
+
+## Version hygiene
+
+The current version is `0.2.1`. Packed dependencies installed by filename or URL
+remain on that exact tarball until consumers update their manifest and lockfile;
+a version bump does not update them automatically. Do not replace an existing
+version, reuse a tag, or remove `.`/`./vite`. Treat configuration, virtual module,
+CSS delivery, Node/peer minimum and declaration changes as compatibility changes.
+Before `1.0`, document any breaking changes and use a minor version bump rather
+than hiding them in a patch. Consumers must retain React 19, React DOM 19 and a
+compatible Vite, and supply their own story sources and story dependencies: a
+design system tarball containing only built components cannot supply source stories.
+
+Official npm references (check them when changing authentication):
+[trusted publishers](https://docs.npmjs.com/trusted-publishers/),
+[provenance](https://docs.npmjs.com/generating-provenance-statements/),
+[granular tokens](https://docs.npmjs.com/creating-and-viewing-access-tokens/).
+
+## First publish of a new package name
+
+Established procedure, after a morning spent rediscovering it:
+
+1. **`npm trust` works before the package exists.** `npm trust github <pkg> --repo <owner>/<repo> --file publish.yml --allow-publish`
+   returns **201** even for a name that has never been published, as long as you are authenticated. Do this first; it is
+   what lets every later `v*` tag publish itself through OIDC with provenance, no tokens.
+2. **Workflows that set `NODE_AUTH_TOKEN` cannot use trusted publishing.** An empty secret sends an
+   unauthenticated request and npm answers `404` on the `PUT`, which reads like a missing package. This workflow
+   therefore sets no token.
+3. **The first publish has to happen once from a machine** — the registry has no artifact yet:
+
+   ```bash
+   cd <the package checkout>
+   npm login --registry https://registry.npmjs.org     # prints a browser URL; no OTP code needed
+   NPM_CONFIG_USERCONFIG=<config> npm publish          # browser URL again, then "+ <pkg>@<version>"
+   ```
+
+   A `~/.npmrc` that maps the scope to another registry (e.g. `@scope:registry=https://npm.pkg.github.com/`) makes a
+   plain `npm publish` target that registry instead and fail with `403`. Point the scope at npmjs in the config used
+   for the publish.
+4. **Verify from the registry, not from the local output:** `curl -s https://registry.npmjs.org/<scope>%2f<pkg>`
+   must list the version. Until it does, nothing is published.
+5. After that, releases are tags: `git tag -a vX.Y.Z && git push origin vX.Y.Z`, and the publish workflow does the
+   rest. Do **not** push a tag for a version you already published by hand — npm rejects the duplicate.

package/package.json

@@ -1,6 +1,78 @@
 {
   "name": "@jfrader/storybook-docs",
-  "version": "0.0.0-stage",
-  "stub": true,
-  "description": "Temporary package placeholder for staged publishing"
+  "version": "0.4.4",
+  "type": "module",
+  "description": "A documentation front for any design system that has Storybook: navigation, live examples and API tables are generated from the story files themselves.",
+  "exports": {
+    ".": {
+      "types": "./dist/index.d.ts",
+      "import": "./dist/index.js"
+    },
+    "./vite": {
+      "types": "./dist/vite-plugin.d.ts",
+      "import": "./dist/vite-plugin.js"
+    }
+  },
+  "peerDependencies": {
+    "react": "^19.0.0",
+    "react-dom": "^19.0.0",
+    "vite": "^6.0.0 || ^7.0.0 || ^8.0.0"
+  },
+  "devDependencies": {
+    "@types/node": "^22.20.5",
+    "@types/react": "^19.3.0",
+    "@types/react-dom": "^19.3.0",
+    "esbuild": "^0.28.2",
+    "react": "^19.3.0",
+    "react-dom": "^19.3.0",
+    "vite": "^8.3.4"
+  },
+  "dependencies": {
+    "marked": "^18.1.1",
+    "react-docgen-typescript": "^2.4.0",
+    "typescript": "^5.9.3"
+  },
+  "license": "MIT",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/jfrader/storybook-docs.git"
+  },
+  "homepage": "https://github.com/jfrader/storybook-docs",
+  "bugs": {
+    "url": "https://github.com/jfrader/storybook-docs/issues"
+  },
+  "publishConfig": {
+    "access": "public",
+    "registry": "https://registry.npmjs.org"
+  },
+  "keywords": [
+    "storybook",
+    "react",
+    "vite",
+    "design-system",
+    "documentation",
+    "props",
+    "docs"
+  ],
+  "engines": {
+    "node": ">=22.12.0"
+  },
+  "files": [
+    "dist",
+    "docs/CONFIG.md",
+    "docs/RELEASING.md",
+    "LICENSE",
+    "README.md"
+  ],
+  "sideEffects": [
+    "**/*.css"
+  ],
+  "scripts": {
+    "test": "node --test test/*.test.ts",
+    "typecheck": "tsc --noEmit",
+    "build": "pnpm build:package && pnpm --dir examples/jfrader-ui build",
+    "build:package": "node scripts/build.mjs",
+    "smoke:package": "node scripts/smoke-package.mjs",
+    "check:frames": "node scripts/check-example-frames.mjs"
+  }
 }