@box-kite/react 2.2.14 → 2.2.16

package/mcp/src/data.d.ts

@@ -1,90 +0,0 @@
-import { RegistryItem } from '../../pages/site/registry';
-/**
- * The corpora, all of them generated somewhere else in this repository: the prop reference F3
- * measures off the engine, the component reference G4 extracts from the sources, the rules file AI3
- * installs as a skill, and F4's registry items. Nothing here is written down a second time — a
- * transcribed fact is the one an agent trusts over its priors and the one that goes stale.
- */
-export interface PropExample {
-    value: unknown;
-    css: string;
-}
-export interface PropRecord {
-    name: string;
-    description: string;
-    /** The CSS properties it writes. More than one when the prop composes (`shadow`, the filters). */
-    properties: string[];
-    example: PropExample;
-    /** Whether a number is accepted, and whether values outside the listed set are. */
-    numeric: boolean;
-    open: boolean;
-    /** The listed values, or a count alone where the reference cut a long list short. Numeric scales list numbers. */
-    values?: (string | number)[];
-    valueCount?: number;
-}
-export interface ComponentProp {
-    name: string;
-    type: string;
-    required: boolean;
-    default: string | null;
-    description: string;
-}
-export interface ComponentPart {
-    name: string;
-    description: string;
-    props: ComponentProp[];
-}
-export interface ComponentKey {
-    mode: string | null;
-    keys: string;
-    action: string;
-}
-export interface ComponentRecord {
-    name: string;
-    route: string;
-    import: string;
-    description: string;
-    pattern?: string;
-    props: ComponentProp[];
-    parts?: ComponentPart[];
-    keyboard?: ComponentKey[];
-    a11y?: string[];
-    styleTree?: string[];
-}
-export interface RuleRecord {
-    number: number;
-    /** The bolded lead sentence — what the rule is about, without its 300 words of detail. */
-    heading: string;
-    body: string;
-}
-export declare const packageName: string;
-export declare const packageVersion: string;
-export declare const siteUrl = "https://www.box-kite.dev";
-export declare const props: readonly PropRecord[];
-export declare const prop: (name: string) => PropRecord | undefined;
-export declare const components: readonly ComponentRecord[];
-/** Case-insensitive, because a model asks for `datagrid` as readily as `DataGrid`. */
-export declare const component: (name: string) => ComponentRecord | undefined;
-export declare const rules: readonly RuleRecord[];
-/**
- * Those bullets, verbatim — the server's `instructions`, which a client puts in front of the model
- * before it calls anything. `scripts/agentSources.mjs` reads the same block for `llms.txt` and the
- * skill; `data.test.ts` pins this reader to that one, because two parsers of one file is how a fact
- * comes to be stated two ways.
- */
-export declare const priorFacts: readonly string[];
-export declare const blocks: readonly RegistryItem[];
-export declare const blockInstall: (name: string) => string;
-/** The page a registry item is shown on — running in light and dark, with every file — if it has one. */
-export declare const blockPage: (name: string) => string | undefined;
-/**
- * A fresh engine with readable class names, no DOM and no console: what `check_styles` judges a value with. One
- * per call rather than one for the process, so a caller's `vars` or `css` cannot leak into the next
- * answer through the rule registry.
- */
-export declare const styleEngine: () => import('../../src/core').StyleEngine;
-/**
- * Every style prop's accepted values, live off the registry rather than out of `props.json`, which
- * cuts a list over 40 short — and a colour prop's 295 tokens are exactly the list worth having.
- */
-export declare function acceptedValues(name: string): string[];

package/mcp/src/data.test.d.ts

@@ -1 +0,0 @@
-export {};

package/mcp/src/engine.d.ts

@@ -1,23 +0,0 @@
-/**
- * What one prop writes, measured. Every answer this server gives about a value — the example, the
- * scale, the verdict — comes through here rather than out of a table, so a changed divider changes
- * the documentation in the same commit and a rejected value is reported as what it is: nothing.
- */
-/**
- * The sheet as a list of top-level rules. A brace counter rather than a split on `}`, because a
- * `@media`, `@container` or `@scope` block carries rules of its own and a nested one must stay with
- * its wrapper — and because the sink writes several rules to a line, so a line is not a rule.
- */
-export declare function splitRules(css: string): string[];
-export interface Measured {
-    /** The rules this prop added, at-rules included — empty when the value was not accepted. */
-    css: string;
-    /** The class names it produced, without the base class every Box carries. */
-    classNames: string[];
-}
-/** One prop resolved on an engine of its own, so nothing it writes can hide behind another prop's class. */
-export declare function measure(name: string, value: unknown): Measured;
-/** Just the declarations, for a table where the selector is noise: `padding:1rem`. */
-export declare function declarations(name: string, value: unknown): string;
-/** How a value is written in JSX — a string in quotes, everything else in braces. */
-export declare const written: (name: string, value: unknown) => string;

package/mcp/src/index.d.ts

@@ -1 +0,0 @@
-export {};

package/mcp/src/search.d.ts

@@ -1,26 +0,0 @@
-/**
- * One entry point over the four corpora, because an agent mid-task knows what it wants the UI to do
- * and not which of them holds the answer. Ranked rather than filtered: a query with no exact hit
- * should still come back with the three things most worth reading, since an empty result sends the
- * model back to its priors — which is the failure this whole package exists to prevent.
- */
-export type HitKind = 'prop' | 'component' | 'nesting' | 'rule';
-export interface Hit {
-    kind: HitKind;
-    /** What to pass to `get_props`, `get_component` or `get_rules` for the whole record. */
-    name: string;
-    summary: string;
-    score: number;
-}
-/** The four corpora, ranked together. `kind` narrows it when the caller already knows which it wants. */
-export declare function search(query: string, options?: {
-    kind?: HitKind;
-    limit?: number;
-}): Hit[];
-/**
- * The components whose own props a name belongs to — what a search for `onValueChange` should answer
- * with, since the same prop name lives on six widgets and none of them is in the prop registry.
- */
-export declare function componentsWithProp(name: string): string[];
-/** Case-insensitive component lookup that also answers for a part (`Tabs.Tab` → `Tabs`). */
-export declare function resolveComponent(name: string): import('./data').ComponentRecord | undefined;

package/mcp/src/search.test.d.ts

@@ -1 +0,0 @@
-export {};

package/mcp/src/server.d.ts

@@ -1,18 +0,0 @@
-import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
-/**
- * `@box-kite/mcp` — the retrieval channel for an agent mid-task.
- *
- * Deliberately six tools at *capability* level rather than one per document: what may I write, what
- * does this component take, and — the one no docs mirror can answer — does this value actually work.
- * The package is built from this repository, so every answer is the reference the same commit
- * generated: `api/props.json` measured off the engine, `api/components/*.json` extracted from the
- * sources, the rules file the skill installs, and the engine itself for `check_styles`.
- */
-/**
- * What a client puts in front of the model before it calls anything. The facts are `AGENTS.md`'s own
- * lead block — the four a model's memory of a library with these prop names gets wrong — because an
- * agent that never calls a tool should still be told the dividers differ.
- */
-export declare const instructions: string;
-/** The server, transport-free so a test can drive it over an in-memory pair. */
-export declare function createServer(): McpServer;

package/mcp/src/server.test.d.ts

@@ -1 +0,0 @@
-export {};

package/mcp/src/styles.d.ts

@@ -1,27 +0,0 @@
-/**
- * `check_styles`: the answer an agent cannot get from prose. A value this library does not accept
- * produces **no rule and no class name** — silently, by design — so the only honest way to say
- * whether `bgColor="blue-550"` works is to hand it to the engine and look at what came back.
- *
- * Each prop is measured on its own, because one bag would let a rejected value hide behind an
- * accepted one in the same class list.
- */
-export type Verdict = 'ok' | 'misread' | 'rejected-value' | 'unknown-prop' | 'html-attribute' | 'reserved';
-export interface PropCheck {
-    name: string;
-    verdict: Verdict;
-    /** The rules this prop wrote, at-rules included. Empty unless `ok` or `misread`. */
-    css: string;
-    /** What to do about it, when the verdict is not `ok`. */
-    note?: string;
-    /** Prop names worth trying instead, closest first. */
-    suggestions?: string[];
-}
-export interface StyleCheck {
-    checks: PropCheck[];
-    /** The class attribute the whole bag resolves to — what `<Box {...props}>` would render. */
-    className: string;
-    ok: boolean;
-}
-/** Judge a whole prop bag: one verdict per prop, plus the class attribute the bag as a whole resolves to. */
-export declare function checkStyles(bag: Record<string, unknown>): StyleCheck;

package/mcp/src/styles.test.d.ts

@@ -1 +0,0 @@
-export {};

package/mcp/src/tools.d.ts

@@ -1,18 +0,0 @@
-import { ComponentRecord } from './data';
-import { Hit } from './search';
-/** `search_docs` — the entry point when the caller knows the goal and not the name. */
-export declare function searchDocs(query: string, kind?: Hit['kind'], limit?: number): string;
-/** `get_props` — the record for named style props, with the scale measured rather than stated. */
-export declare function getProps(names: string[]): string;
-export type ComponentSection = 'props' | 'parts' | 'keyboard' | 'a11y' | 'styles';
-/** `get_component` — one component's whole contract: props, parts, the keyboard map and the ARIA. */
-export declare function getComponent(name: string, include?: ComponentSection[]): string;
-/** `check_styles` — the engine's own answer, which is the only one that counts. */
-export declare function checkStylesTool(bag: Record<string, unknown>): string;
-/** `get_rules` — the numbered rules, or the index of them. */
-export declare function getRules(numbers?: number[]): string;
-/** `get_blocks` — F4's registry: whole sections the shadcn CLI installs, wired and compiling. */
-export declare function getBlocks(name?: string): string;
-/** Every nesting key, for the tool description's "what else can I write" — small enough to state whole. */
-export declare const nestingSummary: () => string;
-export type { ComponentRecord };

package/mcp/src/vocabulary.d.ts

@@ -1,41 +0,0 @@
-/**
- * Every key a Box takes that is *not* one of the 235 style props: the nesting keys, and the four
- * reserved names. Imported from the engine's own records rather than listed here, so a key added to
- * the library is in the MCP server the same day — the whole reason this package lives in this repo.
- */
-/** What a nesting key is for, in one line — the engine's records carry the selector, not the reason. */
-declare const KINDS: {
-    readonly pseudoClass: "a state of this element";
-    readonly pseudoElement: "a pseudo-element of this element (one per Box)";
-    readonly breakpoint: "a viewport width, min-width and up";
-    readonly media: "a reader preference or input device";
-    readonly container: "the width of the nearest query container";
-    readonly variant: "an attribute or position on this element's own selector";
-    readonly group: "an ancestor's or a preceding sibling's state";
-    readonly theme: "one named theme";
-    readonly startingStyle: "what these props start from, the first time the element is styled";
-};
-export type NestingKind = keyof typeof KINDS;
-export interface NestingKey {
-    key: string;
-    kind: NestingKind;
-    /** What it compiles to — a selector fragment, an at-rule prelude, or a width in px. */
-    compiles: string;
-    deprecated: boolean;
-}
-/** Every nesting key the engine dispatches on, in the order a reader meets them. */
-export declare const nestingKeys: readonly NestingKey[];
-export declare const nestingKey: (key: string) => NestingKey | undefined;
-export declare const nestingKindLabel: (kind: NestingKind) => string;
-/**
- * The four names a Box takes that are neither a style prop nor a nesting key. `props` is the one an
- * agent gets wrong most often: an HTML attribute written at the top level typechecks and is dropped.
- */
-export declare const reservedProps: Readonly<Record<string, string>>;
-/**
- * HTML attributes an agent most often writes at the top level, where Box drops them. Names the engine
- * already claims are filtered out rather than listed away: `checked` and `placeholder` are nesting
- * keys on a Box, and a hint that contradicted the engine would be worse than no hint.
- */
-export declare const attributeNames: ReadonlySet<string>;
-export {};

package/registry/blocks/dashboard-shell/dashboard-shell.d.ts

@@ -1,24 +0,0 @@
-import { ReactElement, ReactNode } from 'react';
-/**
- * The frame an admin app hangs off: a sidebar, a header with search, a theme toggle and an account
- * menu, and the page itself. The sidebar sticks to the top of its column and folds away below the `md`
- * breakpoint; nothing here is measured or positioned by script.
- *
- * `Box.Theme` is `use="local"` here, so the theme lands on this element and the block can sit inside a
- * page that has its own. Move it to your root layout as `use="global"` for an app-wide switch.
- */
-export interface NavItem {
-    id: string;
-    label: string;
-    href: string;
-    icon: ReactElement;
-}
-export interface DashboardShellProps {
-    /** The heading above the page, and the `id` of the nav item that is marked as current. */
-    title: string;
-    current?: string;
-    /** The theme to open in. Without it the shell follows the reader's saved choice, then their system. */
-    theme?: string;
-    children: ReactNode;
-}
-export default function DashboardShell({ title, current, theme, children }: DashboardShellProps): import("react").JSX.Element;

package/registry/blocks/dashboard-shell/dashboard-stats.d.ts

@@ -1,13 +0,0 @@
-/**
- * The row of tiles above a dashboard. The shapes are `components/chart` primitives — an SVG each, no
- * chart library — and there is no `'use client'` here on purpose: nothing in this file holds state, so
- * it renders in a Server Component, styles and all.
- */
-export interface Stat {
-    label: string;
-    value: string;
-    delta: string;
-    up: boolean;
-    trend: number[];
-}
-export default function DashboardStats(): import("react").JSX.Element;

package/registry/blocks/data-grid/invoice-rows.d.ts

@@ -1,15 +0,0 @@
-/** The rows the block is wired to. Replace this file with your own fetch — the grid reads plain objects. */
-export interface Invoice {
-    id: number;
-    reference: string;
-    customer: string;
-    team: string;
-    status: 'paid' | 'pending' | 'overdue';
-    amount: number;
-    issued: string;
-}
-/**
- * Two hundred invoices generated from the index, so the block has something to sort, filter, group and
- * total without shipping a data file — and every reload shows the same table.
- */
-export declare const invoices: Invoice[];

package/registry/blocks/data-grid/invoices-grid.d.ts

@@ -1 +0,0 @@
-export default function InvoicesGrid(): import("react").JSX.Element;

package/registry/blocks/settings-form/settings-form.d.ts

@@ -1,17 +0,0 @@
-/**
- * A settings panel: text fields, a searchable select, a radio group, a slider and a switch, each a real
- * form control. `Form` reads its own fields when it submits, so none of this needs state — `values` is
- * built from the elements carrying a `name`.
- *
- * `<Toaster />` has to be mounted once near the root of the app for the confirmation to show.
- */
-export interface Settings {
-    name: string;
-    email: string;
-    bio: string;
-    timezone: string;
-    theme: string;
-    density: string;
-    notify: boolean;
-}
-export default function SettingsForm(): import("react").JSX.Element;

package/registry/designs/store/address-form.d.ts

@@ -1,11 +0,0 @@
-export interface AddressFormProps {
-    /** The fieldset's caption, and the prefix every field submits under: `shipping.city`, `billing.city`. */
-    legend?: string;
-    prefix?: string;
-}
-/**
- * A postal address as a `<fieldset>`: name, two street lines, city, postcode, country and a phone. Every
- * field carries the `autocomplete` token a browser fills it from, which on a phone is most of the typing.
- * Drop two into one form, with different prefixes, for a shipping and a billing address.
- */
-export default function AddressForm({ legend, prefix }: AddressFormProps): import("react").JSX.Element;

package/registry/designs/store/cart-items.d.ts

@@ -1,10 +0,0 @@
-import { CartLine } from './store-data';
-export interface CartItemsProps {
-    lines: readonly CartLine[];
-    onLinesChange: (lines: CartLine[]) => void;
-}
-/**
- * The lines of a cart: picture, name, the options chosen, a quantity stepper, the line's price and a way
- * out. It holds no state — the cart is the page's, so the summary beside it reads the same list.
- */
-export default function CartItems({ lines, onLinesChange }: CartItemsProps): import("react").JSX.Element;

package/registry/designs/store/cart-page.d.ts

@@ -1,4 +0,0 @@
-/** The cart: its lines beside the summary, both reading one list, and an empty state once it is cleared. */
-export default function CartPage({ theme }: {
-    theme?: string;
-}): import("react").JSX.Element;

package/registry/designs/store/checkout-page.d.ts

@@ -1,7 +0,0 @@
-/**
- * The checkout: one form of contact, address, delivery and payment, beside the order it pays for. The
- * sections are separate blocks, each a `<fieldset>`, so the form reads every field by name on submit.
- */
-export default function CheckoutPage({ theme }: {
-    theme?: string;
-}): import("react").JSX.Element;

package/registry/designs/store/credit-card-form.d.ts

@@ -1,10 +0,0 @@
-/**
- * A card payment fieldset: number, name, expiry and security code, formatted as they are typed and checked
- * when a field is left, with a card drawn above that fills in as they go. It is a `<fieldset>`, not a form,
- * so it drops into a checkout form beside the address; the fields submit as `cardNumber`, `cardName`,
- * `cardExpiry` and `cardCvc`, with the `autocomplete` tokens a browser fills a saved card from.
- *
- * This only shapes the input. Sending a raw card number to your own server puts you in scope for PCI DSS —
- * in production these fields are usually your payment provider's hosted inputs, laid out the same way.
- */
-export default function CreditCardForm(): import("react").JSX.Element;

package/registry/designs/store/form-field.d.ts

@@ -1,19 +0,0 @@
-import { ReactNode } from 'react';
-/** What a field's control is handed: its `id`, and the two attributes that tie an error to it. */
-export interface FieldControl {
-    id: string;
-    'aria-invalid'?: true;
-    'aria-describedby'?: string;
-}
-export interface FormFieldProps {
-    label: string;
-    /** Shown under the control and read with it; the control is marked invalid while there is one. */
-    error?: string;
-    hint?: string;
-    children: (control: FieldControl) => ReactNode;
-}
-/**
- * A label, a control and what is wrong with it. The control is a render prop so the field can hand it the
- * ids — a message the screen reader is not pointed at is a message only the sighted get.
- */
-export default function FormField({ label, error, hint, children }: FormFieldProps): import("react").JSX.Element;

package/registry/designs/store/order-summary.d.ts

@@ -1,18 +0,0 @@
-import { ReactNode } from 'react';
-import { CartLine } from './store-data';
-export interface OrderSummaryProps {
-    lines: readonly CartLine[];
-    /** The shipping price once a method is chosen. Left out, the summary says it is worked out at checkout. */
-    shipping?: number;
-    /** List the objects themselves — what a checkout page shows, where the cart is no longer on screen. */
-    showLines?: boolean;
-    /** The button underneath: "Checkout" on the cart page, nothing on the checkout. */
-    action?: ReactNode;
-    /** Told the discount once a code is accepted, for a page that shows the total somewhere else too. */
-    onDiscountChange?: (amount: number) => void;
-}
-/**
- * Subtotal, discount, shipping, tax and the total, with a discount-code field and how far the cart is from
- * free shipping. Every figure is computed from `lines`, so it can never disagree with the cart beside it.
- */
-export default function OrderSummary({ lines, shipping, showLines, action, onDiscountChange }: OrderSummaryProps): import("react").JSX.Element;

package/registry/designs/store/product-art.d.ts

@@ -1,26 +0,0 @@
-import { Shape } from './store-data';
-export type ArtView = 'front' | 'set';
-export interface ProductArtProps {
-    shape: Shape;
-    finish: string;
-    /** For the `set` view: more finishes, each on its own tile beside the first. */
-    also?: readonly string[];
-    view?: ArtView;
-    /** Names the picture; without one it is decoration, hidden from assistive technology. */
-    label?: string;
-    /** The line's width in the icon's own 24-unit grid: thinner on a large tile, heavier on a thumbnail. */
-    stroke?: 0.5 | 0.75 | 1 | 1.25 | 1.5;
-    /** Rounds the picture’s corners, on the ÷4 scale: the tiles clip themselves, so nothing around them has to. */
-    radius?: 2 | 3 | 4 | 6;
-}
-/** Fills its parent: give the parent a size or an aspect ratio, and the picture takes the rest. */
-export default function ProductArt({ shape, finish, also, view, label, stroke, radius }: ProductArtProps): import("react").JSX.Element;
-/** A flat dot of the finish, for the colour swatches. */
-export declare function finishSwatch(id: string): {
-    vars: {
-        swatch: string;
-    };
-    css: {
-        backgroundColor: string;
-    };
-};

package/registry/designs/store/product-card.d.ts

@@ -1,11 +0,0 @@
-import { Product } from './store-data';
-export interface ProductCardProps {
-    product: Product;
-    /** The heading level the card's name takes in the page around it. */
-    level?: 'h2' | 'h3';
-}
-/**
- * One product in a grid. The whole card is the link, and its name is the link's text: the picture is
- * decoration beside it, and the finish swatches are spelled out for a screen reader in one sentence.
- */
-export default function ProductCard({ product, level }: ProductCardProps): import("react").JSX.Element;

package/registry/designs/store/product-gallery.d.ts

@@ -1,11 +0,0 @@
-import { Product } from './store-data';
-export interface ProductGalleryProps {
-    product?: Product;
-    /** The finish on show — the variant picker beside the gallery owns it. */
-    finish?: string;
-}
-/**
- * A product's pictures: one large view and a row of thumbnails that choose it. The thumbnails are tabs
- * (APG's tabbed carousel), so the arrow keys move between them and each picture is named by its tab.
- */
-export default function ProductGallery({ product, finish }: ProductGalleryProps): import("react").JSX.Element;

package/registry/designs/store/product-grid.d.ts

@@ -1,10 +0,0 @@
-import { Product } from './store-data';
-export interface ProductGridProps {
-    products?: readonly Product[];
-    title?: string;
-}
-/**
- * A product grid with filters: categories and finishes as checkboxes, a sort, and a count that is announced
- * as it changes. Filtering is a `useMemo` over the list it is given — hand it the page your API returned.
- */
-export default function ProductGrid({ products, title }: ProductGridProps): import("react").JSX.Element;

package/registry/designs/store/product-page.d.ts

@@ -1,5 +0,0 @@
-/** One product: the gallery and the picker share the finish, and adding to the cart moves the header's count. */
-export default function ProductPage({ slug, theme }: {
-    slug?: string;
-    theme?: string;
-}): import("react").JSX.Element;

package/registry/designs/store/quantity-stepper.d.ts

@@ -1,13 +0,0 @@
-export interface QuantityStepperProps {
-    value: number;
-    onChange: (value: number) => void;
-    /** What is being counted, for the buttons' names: "Add one Bolt the robot". */
-    item: string;
-    min?: number;
-    max?: number;
-}
-/**
- * Two buttons and the count between them. The count is an `<output>`, which is a polite live region of its
- * own, so a screen reader hears the new number after each press with nothing wired up.
- */
-export default function QuantityStepper({ value, onChange, item, min, max }: QuantityStepperProps): import("react").JSX.Element;

package/registry/designs/store/shipping-method.d.ts

@@ -1,14 +0,0 @@
-import { ShippingMethod as Method } from './store-data';
-export interface ShippingMethodProps {
-    methods?: readonly Method[];
-    value?: string;
-    onValueChange?: (id: string) => void;
-    /** Standard shipping is free above this subtotal. */
-    freeStandard?: boolean;
-}
-/**
- * Delivery options as cards. Each card is the `<label>` of a native radio, so the whole card is the
- * target, the set is one tab stop with the arrow keys inside it, and the chosen card is styled with
- * `:has(:checked)` — the radio itself stays visible, because it is what says this is a choice of one.
- */
-export default function ShippingMethod({ methods, value, onValueChange, freeStandard }: ShippingMethodProps): import("react").JSX.Element;

package/registry/designs/store/store-data.d.ts

@@ -1,53 +0,0 @@
-/**
- * The catalogue the store pages render: plain objects, so swapping in your own fetch changes nothing else.
- * A finish is the object's colour, the wash its picture sits on, and the ink the picture is drawn in.
- */
-export type Shape = 'lamp' | 'clock' | 'vase' | 'speaker' | 'mug' | 'chair' | 'glass' | 'desk-lamp';
-export interface Finish {
-    id: string;
-    name: string;
-    /** The swatch, as any CSS colour: the finishes are muted on purpose, between the palette's steps. */
-    color: string;
-    /** The wash behind the picture: the finish, lightened. */
-    tile: string;
-    /** The picture's line: a deep tone of the same hue, or a light one on a dark finish. */
-    ink: string;
-}
-export interface Product {
-    slug: string;
-    name: string;
-    shape: Shape;
-    category: string;
-    price: number;
-    finishes: readonly string[];
-    sizes?: readonly string[];
-    badge?: string;
-    summary: string;
-}
-export interface CartLine {
-    id: string;
-    slug: string;
-    finish: string;
-    size?: string;
-    quantity: number;
-}
-export interface ShippingMethod {
-    id: string;
-    name: string;
-    detail: string;
-    price: number;
-}
-export declare const STORE_NAME = "Still";
-export declare const finishes: Record<string, Finish>;
-export declare const products: readonly Product[];
-export declare const categories: string[];
-export declare const sampleCart: readonly CartLine[];
-export declare const shippingMethods: readonly ShippingMethod[];
-/** Orders over this ship free on the standard service. */
-export declare const FREE_SHIPPING_FROM = 250;
-export declare const TAX_RATE = 0.08;
-/** A price as a tag prints it: $240, with cents only when there are some. */
-export declare const formatPrice: (amount: number) => string;
-export declare const productBySlug: (slug: string) => Product;
-export declare const subtotalOf: (lines: readonly CartLine[]) => number;
-export declare const countOf: (lines: readonly CartLine[]) => number;