bojuvue 0.3.2 → 0.4.0

package/README.md

@@ -1,280 +1,106 @@
-# BojuVue 보주뷰 [![starline](https://raw.githubusercontent.com/ScottKirvan/BojuVue/refs/heads/starlines/ScottKirvan/BojuVue/starline.svg)](https://github.com/qoomon/starlines)
-<div align="center">
+# BojuVue 보주뷰 <a href="https://github.com/qoomon/starlines"><img src="https://raw.githubusercontent.com/ScottKirvan/BojuVue/refs/heads/starlines/ScottKirvan/BojuVue/starline.svg" alt="starline" /></a>
 
-  <img src="assets/media/logo.jpg" alt="logo" width="200" height="auto" />
-    <h1><a href="https://github.com/ScottKirvan/BojuVue">ScottKirvan/BojuVue</a></h1>
-  <h3>Shared Vue 3 components, with VitePress-aware builds</h3>
-  
-  
-<!-- Badges -->
-<p>
-  <a href="https://github.com/ScottKirvan/BojuVue/graphs/contributors">
-    <img src="https://img.shields.io/github/contributors/ScottKirvan/BojuVue" alt="contributors" />
-  </a>
-  <a href="https://github.com/ScottKirvan/BojuVue/commits/main">
-    <img src="https://img.shields.io/github/last-commit/ScottKirvan/BojuVue" alt="last update" />
-  </a>
-  <a href="https://github.com/ScottKirvan/BojuVue/network/members">
-    <img src="https://img.shields.io/github/forks/ScottKirvan/BojuVue" alt="forks" />
-  </a>
-  <a href="https://github.com/ScottKirvan/BojuVue/stargazers">
-    <img src="https://img.shields.io/github/stars/ScottKirvan/BojuVue" alt="stars" />
-  </a>
-  <a href="https://github.com/ScottKirvan/BojuVue/issues/">
-    <img src="https://img.shields.io/github/issues/ScottKirvan/BojuVue" alt="open issues" />
-  </a>
-  <a href="https://github.com/ScottKirvan/BojuVue/blob/main/LICENSE.md">
-    <img src="https://img.shields.io/github/license/ScottKirvan/BojuVue.svg" alt="license" />
-  </a>
-  <a href="https://discord.gg/TN6XJSNK5Y">
-    <!--<img src="https://img.shields.io/discord/704680098577514527?style=flat-square&label=%F0%9F%92%AC%20discord&color=00ACD7">-->
-    <img src="https://img.shields.io/discord/1052011377415438346?style=flat-square&label=discord&color=00ACD7">
-  </a>
-</p>
-   
-<h4>
-    <a href="https://scottkirvan.github.io/BojuVue/">Documentation</a>
-  <span> · </span>
-    <a href="https://github.com/ScottKirvan/BojuVue/issues/new?template=bug_report.md">Report Bug</a>
-  <span> · </span>
-    <a href="https://github.com/ScottKirvan/BojuVue/issues/new?template=feature_request.md">Request Feature</a>
-  </h4>
-</div>
+BojuVue is a Vue 3 component library including a download button that serves each visitor the right build for their OS. Works in any Vue 3 app; VitePress-aware variants at a second import path, zero VitePress overhead in the generic build.
 
-**BojuVue** is a Vue 3 component library published to npm as [`bojuvue`](https://www.npmjs.com/package/bojuvue). It exists so that VitePress sites — this author's homepage blog and several local documentation sites — can share one set of landing-page and UX components instead of duplicating them per repo. Update this repo, bump the version, publish, and every consuming site can pull in the update with `npm update`.
+<!-- TODO: demo GIF — record label changing across macOS, Windows, Linux → save to assets/media/demo.gif -->
 
-Branches
---------
-`main` is the [deployed](https://ScottKirvan.github.io/BojuVue/) branch.  The repo doesn't currently contain any other historic or dev branches.
+<div align="center"><a href="https://github.com/ScottKirvan/BojuVue/stargazers"><img src="https://img.shields.io/github/stars/ScottKirvan/BojuVue" alt="stars" /></a> <a href="https://github.com/ScottKirvan/BojuVue/commits/main"><img src="https://img.shields.io/github/last-commit/ScottKirvan/BojuVue" alt="last update" /></a> <a href="https://github.com/ScottKirvan/BojuVue/blob/main/LICENSE.md"><img src="https://img.shields.io/github/license/ScottKirvan/BojuVue.svg" alt="license" /></a> <a href="https://discord.gg/TN6XJSNK5Y"><img src="https://img.shields.io/discord/1052011377415438346?style=flat-square&label=discord&color=00ACD7" alt="discord" /></a></div>
 
-Repo Layout
------------
-```
-BojuVue
-├───.github
-│   ├───gitignore-templates      # .gitignore templates for other stacks (not used by this repo's own Node build)
-│   ├───release-please           # Release-Please config — automated version bumps + CHANGELOG from Conventional Commits
-│   └───workflows                # CI (test + build), docs deploy, release, pre-release staging
-├───assets
-│   └───media                    # Logo
-├───docs                         # VitePress site — consumer-facing docs, deployed to GitHub Pages
-├───notes
-│   ├───dev                      # Design specs and working notes for this repo's own contributors
-│   ├───CHANGELOG.md             # Auto-generated by Release-Please
-│   ├───TODO.md
-│   └───VERSION.md
-├───src                          # Library source — see Architecture below
-├───CLAUDE.md                    # AI agent context
-├───CODE_OF_CONDUCT.md           # Community guidelines
-├───CONTRIBUTING.md              # Contribution guidelines
-├───LICENSE.md                   # MIT License
-└───README.md                    # This file
-```
-
-Issue and PR templates aren't in this repo's own `.github/` — they're inherited from
-the `ScottKirvan/.github` org repo via GitHub's community health file fallback.
-
-Table of Contents
------------------
-- [Branches](#branches)
-- [Repo Layout](#repo-layout)
-- [Features](#features)
-- [Architecture](#architecture)
-- [Installation](#installation)
-- [Usage](#usage)
-- [Adding a new component](#adding-a-new-component)
-- [Contributions / Contact](#contributions--contact)
-- [Credits](#credits)
+**[See it live](https://www.scottkirvan.com/BojuVue/appendix/examples.html)** — every component rendered, not just described.
 
-Features
---------
-- Vue 3 + TypeScript components, built as an ES module via Vite library mode
-- `vue` is a peer dependency, so consuming sites use their own Vue instance — no duplicate copies, no broken reactivity
-- Every component is exported from one entry point (`src/index.ts`), so consuming a new component is a one-line import change
-- The `docs/` VitePress site imports directly from `src/index.ts`/`src/vitepress.ts` and registers every exported component globally, so new components can be previewed live in a real VitePress site without publishing or `npm link`
-- Some components (currently `BVPlatformButton`) ship as **two fully independent builds behind two import paths**: a generic implementation at `bojuvue`, with zero dependency on `vitepress`, and a VitePress-specific implementation at `bojuvue/vitepress`, same component name, resolving anything VitePress-specific for you. Neither component imports or renders the other — the import path is what disambiguates them. `vitepress` is an *optional* peer dependency — installing the package alone never requires it; only importing from the `/vitepress` path does.
+## Install
 
-Architecture
-------------
-The bit that shapes everything else in this repo: **the generic build must have zero
-dependency on `vitepress`, anywhere in its module graph.** Everything below exists to
-make that hold under a real bundler, not just in theory.
-
-**Two entry points, two physical files.** `vite.config.ts` builds library mode with two
-separate entries — `src/index.ts` → `dist/bojuvue.js` (published as `.`) and
-`src/vitepress.ts` → `dist/vitepress.js` (published as `./vitepress`). `src/vitepress.ts`
-re-exports everything `src/index.ts` has, plus its own VitePress-specific component
-implementations, under the same names. This has to be two genuinely separate output
-files, not two exports of one bundle — if both compiled into a single file, importing
-only the generic path would still execute a top-level `import 'vitepress'` somewhere in
-it. Verify this invariant after touching anything under `src/` by building and grepping
-the output:
 ```sh
-npm run build
-grep -r vitepress dist/bojuvue.js   # should print nothing
-```
-
-**Two independent implementations per VitePress-aware component.** A component that
-needs anything VitePress-specific (site data, the router, VitePress's own `VPButton`)
-doesn't take a runtime "VitePress mode" flag — it gets two fully independent
-implementations sharing one exported name, disambiguated by import path:
-`src/ComponentName.vue` (plain props, no `vitepress` import, exported from
-`src/index.ts`) and `src/vitepress/ComponentName.vue` (calls whatever VitePress
-composables it needs itself, exported from `src/vitepress.ts`). Neither imports or
-renders the other. `BVPlatformButton` is the worked example — see
-`src/BVPlatformButton.vue` and `src/vitepress/BVPlatformButton.vue`. Logic genuinely
-shared between the two (e.g. manifest-fetch orchestration) lives in a plain utility
-module both call independently — see `src/useManifestFetch.ts` — not in one component
-owning the other's rendering.
-
-**Prop types stay inline in `defineProps<T>()`.** `@vue/compiler-sfc` resolving a
-`defineProps<T>()` type imported from another module needs the `typescript` package
-loadable from wherever the `.vue` file is compiled — which breaks under `docs/`'s
-cross-directory source build (next point) whenever the repo root's `node_modules` isn't
-present. Keep the type written out inline in the macro itself. A type used only for a
-public, non-macro export (`BVPlatformButtonProps` in `src/BVPlatformButton.types.ts`,
-for instance) is fine to keep in its own file — the constraint is specifically about the
-`defineProps<T>()` type position.
-
-**Real logic lives outside the `.vue` file.** Components with real logic — detection,
-data-shaping, anything beyond pure rendering — extract that logic into a plain `.ts`
-module (`src/platform.ts` next to `BVPlatformButton.vue`) rather than keeping it inline
-in `<script setup>`. Much easier to unit test a plain function than to mount a component
-or mock Vue-specific APIs to exercise the same branch.
-
-**`docs/` previews live source, not the published package.** `docs/` is a separate,
-independently-installed VitePress project. `docs/.vitepress/theme/index.ts` imports
-directly from `../../../src/vitepress` — this repo's own VitePress-entry *source* — and
-registers every export globally, so a new component shows up in a real VitePress site
-the moment you write it (`npm run docs:dev`), no publish or `npm link` needed. That
-import crosses a directory boundary `docs/`'s own dependency resolution doesn't know
-about: files under repo-root `src/` still `import 'vue'`/`import 'vitepress'`
-themselves, which would otherwise resolve relative to `src/`'s own location. A scoped
-Vite plugin in `docs/.vitepress/config.mts` fixes this by redirecting any such import,
-when the importing file is physically under repo-root `src/`, through Vite's normal
-resolver as if it came from inside `docs/` instead. Verify a change here by temporarily
-renaming the repo root's `node_modules` out of the way and confirming `npm run
-docs:build` (from `docs/`) still succeeds — `docs/`'s deploy job never installs the repo
-root's dependencies, so this has to work without them.
-
-**Typechecking and build.** `npm run build` runs `vue-tsc -b` (typecheck, via composite
-TypeScript project references) then `vite build` (emits `dist/`). There's no separate
-typecheck-only script — `vue-tsc -b --noEmit` isn't valid with composite project
-references, so `build` is the only way to typecheck the library.
-
-Installation
-------------
-```
 npm install bojuvue
 ```
 
-Usage
------
-Register components however you already register components in your app:
+## Usage
 
-```ts
-// main.ts (or wherever you create your Vue app)
-import { createApp } from 'vue'
-import { BVPlatformButton, SomeComponent } from 'bojuvue'
-import App from './App.vue'
+```vue
+<script setup>
+import { BVPlatformButton } from 'bojuvue'
+</script>
 
-const app = createApp(App)
-app.component('BVPlatformButton', BVPlatformButton)
-app.component('SomeComponent', SomeComponent)
-app.mount('#app')
+<template>
+  <BVPlatformButton
+    manifest-url="/platformButton.json"
+    fallback-href="https://github.com/you/app/releases"
+  />
+</template>
 ```
 
-Building a VitePress site? Register the same way from `enhanceApp` in
-`.vitepress/theme/index.ts` instead of `main.ts`, and prefer importing from
-`bojuvue/vitepress` for any component with a VitePress-aware build (see
-Features above):
+Works as-is in any Vue 3 app. Building a VitePress site instead? Swap the import for
+`bojuvue/vitepress` to get real `VPButton` theme styling, and register it once so every
+`.md` page can use it with no per-page import:
 
 ```ts
+// .vitepress/theme/index.ts
 import DefaultTheme from 'vitepress/theme'
-import { BVPlatformButton } from 'bojuvue/vitepress'
-import { SomeComponent } from 'bojuvue'
+import * as BojuVue from 'bojuvue/vitepress'
 
 export default {
   extends: DefaultTheme,
   enhanceApp({ app }) {
-    app.component('BVPlatformButton', BVPlatformButton)
-    app.component('SomeComponent', SomeComponent)
+    for (const [name, component] of Object.entries(BojuVue)) {
+      app.component(name, component)
+    }
   },
 }
 ```
 
-Then use it in any `.md` page. Update later with `npm update`.
+Then in any .md page, no import needed:
 
-See the **[component reference](https://scottkirvan.github.io/BojuVue/components/)**
-for every available component's props and a usage example — including, per component,
-which import path(s) it's available from.
+```md
+<BVPlatformButton manifest-url="platformButton.json" />
+```
 
-Adding a new component
------------------------
-Read [Architecture](#architecture) first if you haven't — the steps below assume you
-know why some components have two implementations and why prop types stay inline.
+Your manifest (`public/platformButton.json`) — put one entry under `platforms` for each
+platform you ship for:
+
+```json
+{
+  "platforms": {
+    "windows": { "href": "https://example.com/app.msi" },
+    "macos": { "href": "https://example.com/app.dmg" },
+    "linux": { "href": "https://example.com/app.tar.gz" }
+  }
+}
+```
 
-**A component with no VitePress-specific needs:**
+**[Documentation](https://scottkirvan.github.io/BojuVue/)** -- props reference, live demos, full setup guide, every component.
 
-1. Write the `.vue` file under `src/` (e.g. `src/YourComponent.vue`) — standard SFC:
-   `<script setup lang="ts">` for props/logic, `<template>` for markup, `<style
-   scoped>` for CSS scoped to that component alone.
-2. Make configurable text/behavior actual props, not hardcoded strings —
-   `defineProps<{...}>()` with `withDefaults(...)` for sensible fallbacks. Keep the prop
-   type written inline in the macro.
-3. Extract any real logic (detection, data-shaping) into a plain `.ts` module next to
-   the component, and write unit tests for it (see `src/platform.ts` /
-   `src/platform.test.ts`).
-4. Add one line to `src/index.ts`: `export { default as YourComponent } from
-   './YourComponent.vue'`.
-5. Preview it: `npm run docs:dev` (from `docs/`), then use `<YourComponent />` anywhere
-   in a `.md` file — it's registered globally in this repo's own `docs/` theme, so no
-   import is needed there.
-6. Add a reference page at `docs/components/your-component.md` (props table + usage
-   example — copy the structure of an existing page) and link it from
-   `docs/components/index.md` and the sidebar in `docs/.vitepress/config.mts`.
-7. `npm run build` at the repo root to confirm the library itself still builds clean,
-   and `npm test` to run the unit suite.
+What's in the package
+---------------------
 
-**A component that needs something VitePress-specific** (worked example:
-`BVPlatformButton`) gets two fully independent implementations instead of one file:
+Published to npm as [`bojuvue`](https://www.npmjs.com/package/bojuvue). It exists so that VitePress sites can share one set of landing-page components instead of duplicating them per repo. This repo gets updated, the package gets published, and every consuming site picks it up with `npm update`.
 
-1. The framework-agnostic logic and markup goes in `src/YourComponent.vue` — plain
-   props in (including anything the VitePress-specific implementation would otherwise
-   read from a VitePress composable — e.g. a `base` prop standing in for
-   `useData().site.value.base`, resolved by that other implementation itself, not read
-   directly here). No `vitepress` import anywhere in this file.
-2. `src/vitepress/YourComponent.vue` calls whatever VitePress composables it needs
-   itself and implements its own rendering. It does not import or render
-   `src/YourComponent.vue`. Any logic genuinely shared between the two (like fetch
-   orchestration — see `useManifestFetch`) lives in a plain utility module both call
-   independently, not in one component owning the other's rendering.
-3. `src/index.ts` exports the generic implementation; `src/vitepress.ts` re-exports
-   everything `src/index.ts` has, plus exports the VitePress-specific implementation —
-   both under the same name, `YourComponent`. The import path is what disambiguates
-   them.
-4. Preview via `docs/.vitepress/theme/index.ts`, which registers from `src/vitepress.ts`
-   (the superset) — this exercises both the VitePress-specific implementation and
-   everything re-exported from the generic one.
-5. `npm run build` must still produce two separate physical files (check
-   `vite.config.ts`'s `build.lib.entry`), and the generic build's output file must
-   contain zero reference to `vitepress` — grep for it directly after any build that
-   touches this component (see [Architecture](#architecture)).
-6. Add the reference page and sidebar entry as in step 6 above, and document both import
-   paths on that page — see `docs/components/platform-button.md` for the pattern.
+- **BVPlatformButton** — reads the visitor's OS from the browser, fetches a manifest you host, and links to the right download. No manifest entry for a platform? The button hides itself, or shows a fallback link if you provide one. VitePress sites get real `VPButton` styling from `bojuvue/vitepress`; plain Vue 3 apps use the same prop surface without any VitePress dependency.
+- **BVMoreButton** — an overflow dropdown for the secondary links every project needs (repo, report a bug, request a feature) without letting them outweigh your primary call-to-action.  Visible-text mode ("More...") or a compact icon-only "⋯" button; VitePress sites get real `VPButton` styling for free via `bojuvue/vitepress`, same as `BVPlatformButton`.
+  <!-- TODO: demo GIF/screenshot — the dropdown open, showing the GitHub/bug/feature links → save to assets/media/more-button-demo.gif -->
+- **BVButton** — VitePress's own `VPButton` prop shape, usable in any Vue 3 app. The primitive the others build on.
+- **BVIconButton** — `BVButton` with an optional inline SVG icon in addition to, or in place of, the button text.
 
-**Before opening a pull request:** `npm test` and `npm run build` both pass; tests exist
-for anything with real logic; every failure and edge path has a deliberate, documented
-user-visible behavior; the reference page documents every prop's default and whether
-it's required, and calls out anything deliberately not supported, with why. See
-`CLAUDE.md` for the full set of engineering conventions this project holds
-contributions to.
+Every component exports from `bojuvue`. Components with VitePress-specific builds are located at `bojuvue/vitepress` — same exported name, resolves VitePress-specific values and renders through real VitePress components. `vitepress` is an optional peer dependency: installing the package alone never requires it.
+
+Why not a monorepo workspace?
+-----------------------------
+
+npm/yarn/pnpm workspaces already solve "share a component across projects" for free, and if every consuming site lived in this repo, that would be the right answer — skip this package entirely.
+
+It only holds while that's true. The moment a consuming site is a separate repo — a different site, a client's project, a repo you don't control — a workspace can't reach across that boundary. There's no shared `package.json` to add an entry to, no symlinked `node_modules` to rely on. Publishing is what still works: a versioned package on the registry that any repo, anywhere, can `npm install` and `npm update`.
+
+That's the actual reason this exists — not "components in a folder," but components that survive the boundary between repos.
+
+Contributing
+------------
+See [CONTRIBUTING.md](CONTRIBUTING.md) for development setup, the branch and commit
+conventions, and step-by-step instructions for adding a new component.
 
 Contributions / Contact
 -----------------------
 - Please [file an issue](https://github.com/ScottKirvan/BojuVue/issues/new), or [grab a fork](https://github.com/ScottKirvan/BojuVue/fork), hack away, and submit a [pull request](https://github.com/ScottKirvan/BojuVue/pulls).
 - Contact me at [linkedin.com/in/scottkirvan/](https://www.linkedin.com/in/scottkirvan/)
-- You can also contact me at my [discord](https://discord.gg/TN6XJSNK5Y) server, I'm cptvideo.
+- You can also find me on [Discord](https://discord.gg/TN6XJSNK5Y) — I'm cptvideo.
 
 Credits
 -------
@@ -282,6 +108,6 @@ Credits
 
 Scaffolded from [ScooterGitTemplate](https://github.com/ScottKirvan/ScooterGitTemplate).
 
-Project Link:  [BojuVue](https://github.com/ScottKirvan/BojuVue)  
-[CHANGELOG](notes/CHANGELOG.md)  
+Project Link: [BojuVue](https://github.com/ScottKirvan/BojuVue)
+[CHANGELOG](notes/CHANGELOG.md)
 [TODO](notes/TODO.md)

package/dist/bojuvue.js

@@ -1,4 +1,4 @@
-import { a as e, c as t, i as n, l as r, n as i, o as a, r as o, s, t as c } from "./useMoreButtonMenu-BYpzDpLJ.js";
+import { a as e, c as t, i as n, l as r, n as i, o as a, r as o, s, t as c } from "./useMoreButtonMenu-CewNc9xN.js";
 import { Fragment as l, computed as u, createBlock as d, createCommentVNode as f, createElementBlock as p, createTextVNode as m, createVNode as h, defineComponent as g, mergeProps as _, normalizeClass as v, normalizeStyle as y, onMounted as b, openBlock as x, ref as S, renderList as C, toDisplayString as w, unref as T } from "vue";
 //#region src/BVIconButton.vue?vue&type=script&setup=true&lang.ts
 var E = ["innerHTML"], D = /*#__PURE__*/ t(/* @__PURE__ */ g({

package/dist/index.d.ts

@@ -4,7 +4,7 @@ export { default as BVIconButton } from './BVIconButton.vue';
 export type { BVIconButtonProps } from './BVIconButton.types';
 export { default as BVPlatformButton } from './BVPlatformButton.vue';
 export { detectPlatform, resolveDownload, resolveManifestUrl, defaultLabels } from './platform';
-export type { BVPlatformManifest, BVPlatformEntry, BVPlatformId } from './platform';
+export type { BVPlatformData, BVPlatformEntry, BVPlatformId, BVPlatformManifest } from './platform';
 export type { BVPlatformButtonProps } from './BVPlatformButton.types';
 export { default as BVMoreButton } from './BVMoreButton.vue';
 export type { BVMoreButtonItem, BVMoreButtonProps } from './BVMoreButton.types';

package/dist/platform.d.ts

@@ -3,7 +3,10 @@ export interface BVPlatformEntry {
     href: string;
     label?: string;
 }
-export type BVPlatformManifest = Partial<Record<BVPlatformId, BVPlatformEntry>>;
+export type BVPlatformData = Partial<Record<BVPlatformId, BVPlatformEntry>>;
+export interface BVPlatformManifest {
+    platforms: BVPlatformData;
+}
 export interface NavigatorLike {
     userAgent: string;
     platform: string;

package/dist/useManifestFetch.d.ts

@@ -1,53 +1,58 @@
+import { BVPlatformManifest } from './platform';
 export declare function useManifestFetch(getUrl: () => string): {
     manifest: import('vue').Ref<{
-        windows?: {
-            href: string;
-            label?: string | undefined;
-        } | undefined;
-        macos?: {
-            href: string;
-            label?: string | undefined;
-        } | undefined;
-        linux?: {
-            href: string;
-            label?: string | undefined;
-        } | undefined;
-        android?: {
-            href: string;
-            label?: string | undefined;
-        } | undefined;
-        ios?: {
-            href: string;
-            label?: string | undefined;
-        } | undefined;
-        chromeos?: {
-            href: string;
-            label?: string | undefined;
-        } | undefined;
-    } | null, Partial<Record<import('./platform').BVPlatformId, import('./platform').BVPlatformEntry>> | {
-        windows?: {
-            href: string;
-            label?: string | undefined;
-        } | undefined;
-        macos?: {
-            href: string;
-            label?: string | undefined;
-        } | undefined;
-        linux?: {
-            href: string;
-            label?: string | undefined;
-        } | undefined;
-        android?: {
-            href: string;
-            label?: string | undefined;
-        } | undefined;
-        ios?: {
-            href: string;
-            label?: string | undefined;
-        } | undefined;
-        chromeos?: {
-            href: string;
-            label?: string | undefined;
-        } | undefined;
+        platforms: {
+            windows?: {
+                href: string;
+                label?: string | undefined;
+            } | undefined;
+            macos?: {
+                href: string;
+                label?: string | undefined;
+            } | undefined;
+            linux?: {
+                href: string;
+                label?: string | undefined;
+            } | undefined;
+            android?: {
+                href: string;
+                label?: string | undefined;
+            } | undefined;
+            ios?: {
+                href: string;
+                label?: string | undefined;
+            } | undefined;
+            chromeos?: {
+                href: string;
+                label?: string | undefined;
+            } | undefined;
+        };
+    } | null, BVPlatformManifest | {
+        platforms: {
+            windows?: {
+                href: string;
+                label?: string | undefined;
+            } | undefined;
+            macos?: {
+                href: string;
+                label?: string | undefined;
+            } | undefined;
+            linux?: {
+                href: string;
+                label?: string | undefined;
+            } | undefined;
+            android?: {
+                href: string;
+                label?: string | undefined;
+            } | undefined;
+            ios?: {
+                href: string;
+                label?: string | undefined;
+            } | undefined;
+            chromeos?: {
+                href: string;
+                label?: string | undefined;
+            } | undefined;
+        };
     } | null>;
 };

package/dist/{useMoreButtonMenu-BYpzDpLJ.js → useMoreButtonMenu-CewNc9xN.js}

@@ -57,12 +57,15 @@ var S = {
 function w(e, t) {
 	return C.test(t) ? t : `${e}${t}`;
 }
-function T(e, t, n = {}) {
+function T(e) {
+	return typeof e == "object" && !!e;
+}
+function E(e, t, n = {}) {
 	if (e && t) {
-		let n = e === "chromeos" ? t.chromeos ?? t.android : t[e];
-		if (n) return {
-			href: n.href,
-			label: n.label ?? S[e]
+		let n = T(t.platforms) ? t.platforms : void 0, r = n && (e === "chromeos" ? n.chromeos ?? n.android : n[e]);
+		if (r) return {
+			href: r.href,
+			label: r.label ?? S[e]
 		};
 	}
 	return n.fallbackHref ? {
@@ -72,7 +75,7 @@ function T(e, t, n = {}) {
 }
 //#endregion
 //#region src/useManifestFetch.ts
-function E(e) {
+function D(e) {
 	let t = d(null), n = null;
 	async function r() {
 		n?.abort();
@@ -90,13 +93,13 @@ function E(e) {
 }
 //#endregion
 //#region src/moreButtonMenu.ts
-function D({ triggerLeft: e, triggerRight: t, panelWidth: n, viewportWidth: r }) {
+function O({ triggerLeft: e, triggerRight: t, panelWidth: n, viewportWidth: r }) {
 	let i = e;
 	if (i + n <= r) return i;
 	let a = t - n;
 	return a >= 0 ? a : Math.max(0, r - n);
 }
-function O(e, t, n) {
+function k(e, t, n) {
 	if (n <= 0) return -1;
 	switch (e) {
 		case "Home": return 0;
@@ -107,7 +110,7 @@ function O(e, t, n) {
 }
 //#endregion
 //#region src/useMoreButtonMenu.ts
-function k({ itemCount: e, rootEl: t, iconButtonEl: n, panelEl: r }) {
+function A({ itemCount: e, rootEl: t, iconButtonEl: n, panelEl: r }) {
 	let a = d(!1), c = d(0), l = d(0);
 	function u() {
 		return (n.value?.$el)?.querySelector("a, button") ?? null;
@@ -134,7 +137,7 @@ function k({ itemCount: e, rootEl: t, iconButtonEl: n, panelEl: r }) {
 		let e = u(), t = r.value;
 		if (!e || !t || typeof window > "u") return;
 		let n = _(), i = e.getBoundingClientRect(), a = t.getBoundingClientRect().width / n;
-		c.value = D({
+		c.value = O({
 			triggerLeft: i.left / n,
 			triggerRight: i.right / n,
 			panelWidth: a,
@@ -151,7 +154,7 @@ function k({ itemCount: e, rootEl: t, iconButtonEl: n, panelEl: r }) {
 		a.value ? b() : y();
 	}
 	function S(t) {
-		a.value || (t.key === "ArrowDown" ? (t.preventDefault(), y(O("ArrowDown", -1, e()))) : t.key === "ArrowUp" && (t.preventDefault(), y(O("ArrowUp", -1, e()))));
+		a.value || (t.key === "ArrowDown" ? (t.preventDefault(), y(k("ArrowDown", -1, e()))) : t.key === "ArrowUp" && (t.preventDefault(), y(k("ArrowUp", -1, e()))));
 	}
 	let C = [
 		"ArrowDown",
@@ -166,7 +169,7 @@ function k({ itemCount: e, rootEl: t, iconButtonEl: n, panelEl: r }) {
 		}
 		if (C.includes(t.key)) {
 			t.preventDefault();
-			let n = O(t.key, h(), e());
+			let n = k(t.key, h(), e());
 			n >= 0 && g(n);
 		}
 	}
@@ -191,4 +194,4 @@ function k({ itemCount: e, rootEl: t, iconButtonEl: n, panelEl: r }) {
 	};
 }
 //#endregion
-export { T as a, y as c, x as i, _ as l, E as n, w as o, S as r, b as s, k as t };
+export { E as a, y as c, x as i, _ as l, D as n, w as o, S as r, b as s, A as t };

package/dist/vitepress.d.ts

@@ -1,5 +1,5 @@
 export { detectPlatform, resolveDownload, resolveManifestUrl, defaultLabels } from './platform';
-export type { BVPlatformManifest, BVPlatformEntry, BVPlatformId } from './platform';
+export type { BVPlatformData, BVPlatformEntry, BVPlatformId, BVPlatformManifest } from './platform';
 export type { BVPlatformButtonProps } from './BVPlatformButton.types';
 export { default as BVPlatformButton } from './vitepress/BVPlatformButton.vue';
 export type { BVButtonProps } from './BVButton.types';

package/dist/vitepress.js

@@ -1,4 +1,4 @@
-import { a as e, c as t, i as n, l as r, n as i, o as a, r as o, s, t as c } from "./useMoreButtonMenu-BYpzDpLJ.js";
+import { a as e, c as t, i as n, l as r, n as i, o as a, r as o, s, t as c } from "./useMoreButtonMenu-CewNc9xN.js";
 import { Fragment as l, computed as u, createBlock as d, createCommentVNode as f, createElementBlock as p, createTextVNode as m, createVNode as h, defineComponent as g, mergeProps as _, normalizeClass as v, normalizeStyle as y, onMounted as b, openBlock as x, ref as S, renderList as C, toDisplayString as w, unref as T } from "vue";
 import { useData as E, withBase as D } from "vitepress";
 import { VPButton as O } from "vitepress/theme";

package/package.json

@@ -1,13 +1,17 @@
 {
   "name": "bojuvue",
-  "version": "0.3.2",
+  "version": "0.4.0",
   "type": "module",
   "license": "MIT",
-  "description": "Vue 3 components for VitePress — platform-aware download buttons and shared UI, built so publishing them doesn't duplicate Vue.",
+  "description": "Vue 3 components including a download button that serves each visitor the right build for their OS. Works in any Vue 3 app; VitePress-aware variants included.",
+  "homepage": "https://www.scottkirvan.com/BojuVue/",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/ScottKirvan/BojuVue.git"
   },
+  "bugs": {
+    "url": "https://github.com/ScottKirvan/BojuVue/issues"
+  },
   "files": [
     "dist"
   ],
@@ -49,6 +53,16 @@
       "optional": true
     }
   },
+  "funding": [
+    {
+      "type": "github",
+      "url": "https://github.com/sponsors/ScottKirvan"
+    },
+    {
+      "type": "ko-fi",
+      "url": "https://ko-fi.com/ScottKirvan"
+    }
+  ],
   "keywords": [
     "vue",
     "vue3",
@@ -60,6 +74,5 @@
     "platform-detection",
     "typescript",
     "vite"
-  ],
-  "homepage": "https://github.com/ScottKirvan/BojuVue#readme"
-}
+  ]
+}