Skip to content
MIZU.

DataInspector

Open a payload, follow its structure and copy the JSON without a developer-tools panel.

View .md

Live — this one is real

Example release payload

Example release payload {4}
name"mizu-ui"
version"0.2.0"
checks {2}
typestrue
linttrue
files [2]
0"styles.css"
1"fonts.css"

Usage

tsx
import { DataInspector } from "mizu-ui";

export function Example() {
  return (
    <DataInspector
      label="Example release payload"
      value={{
        name: "mizu-ui",
        version: "0.2.0",
        checks: { types: true, lint: true },
        files: ["styles.css", "fonts.css"],
      }}
    />
  );
}

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/data-inspector

Every component imports from its own path, its name in kebab case. Its source, data/Inspection.tsx, also holds ActivityFeed, DiffView and TreeView. 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 { DataInspector } from "@/components/ui/mizu/data-inspector";

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 data/Inspection.tsx

Source is included in the npm package under src/data/Inspection.tsx.

Open full source ↗

Props

PropTypeDefaultDescription
valueunknown—A JSON-like object, array or scalar.
labelstring"Data"Section name.

Accessibility

Native disclosure controls. Circular objects are marked; copy is omitted when serialization fails. Depth is capped at eight and siblings at 200.

Motion

Native disclosure; no observers.

Works alongside