Skip to content
MIZU.

Meter

A bounded measurement that distinguishes a reading from task completion.

View .md

Live — this one is real

Storage used68 GB of 100 GB

Usage

tsx
"use client";

import { Meter } from "mizu-ui";

export function Example() {
  return (
    <Meter
      label="Storage used"
      value={68}
      low={30}
      high={85}
      optimum={20}
      format={(v) => `${v} GB of 100 GB`}
    />
  );
}

It starts with "use client" because it keeps state or passes functions to components, so it pastes into a Next.js page as it is. Other React setups ignore the directive.

Source & setup

Add this component to your project with the shadcn CLI. The command copies its source into your configured UI directory, with base.css, Mizu’s tokens, and the stylesheets that hold its rules. Each rule lives in one stylesheet, so components you add together never repeat CSS. In a project without a components.json, run npx shadcn@latest init 0xuser64bit/mizu/preset first: plain init installs shadcn’s theme into your global CSS. Then load the fonts.

sh
npx shadcn@latest add 0xuser64bit/mizu/meter

Every component imports from its own path, its name in kebab case. Its source, status/Feedback.tsx, also holds Status, Alert, Progress, Skeleton, EmptyState, ErrorState, ConnectionStatus, SaveIndicator, AsyncBoundary and TaskProgress. Each has its own command and path; adding one after this copies only its small entry file. To paste the example, replace its mizu-ui import with:

tsx
import { Meter } from "@/components/ui/mizu/meter";

For npm imports, import mizu-ui/styles.css once. Fonts are optional via mizu-ui/fonts.css. Override --mizu-* tokens or use className for local styling. Uses native React and CSS; install the package peers for root imports. A Client Component: its source starts with “use client”.

Inspect status/Feedback.tsx

Source is included in the npm package under src/status/Feedback.tsx.

Open full source ↗

Props

PropTypeDefaultDescription
value / min / maxnumber—Current reading and limits.
low / high / optimumnumber—Native measurement thresholds.
format(value: number) => string—Visible value formatting.

Accessibility

Uses native meter semantics rather than progress. Text repeats the meaningful unit and value.

Motion

CSS transitions explain state changes. Reduced motion removes travel.

Works alongside

StatusAlertProgressSkeleton