Reading Time

A compact "N min read" badge for article headers, blog cards and docs index rows. It renders an inline `<span>`, so it sits beside a date or a tag row without imposing block layout.

blog & long-formserver320pxuiv1.2.0

Preview

Reading Time — live renderprimitives-readingtime--variants

Rendered from the story the storybook (a11y) CI gate runs axe against — the preview can't show something that hasn't been verified.

Install

Two equivalent paths — the URL works in any shadcn-CLI setup; the alias works once you've registered @interlace in your components.json.

Via shadcn URL
npx shadcn@latest add https://ds.interlace.tools/r/reading-time.json
With the @interlace alias
npx shadcn@latest add @interlace/reading-time

Behavior

What this component does — the keyboard path, the measured colour, the text equivalent and the states it can be in. Every figure below is read out of the test or the source that enforces it by scripts/build-behavior-map.mjs, so nothing here can outlive the gate that keeps it true.

Every semantic colour pair this component's own source uses, measured against the shipped hexes in all 4 theme × scheme combinations. The tightest is muted-foreground on background at 7.82:1 (harbor · light), against a floor of 4.5:1.

Measured WCAG contrast ratios per token pair and theme
PairinterlacelightinterlacedarkharborlightharbordarkFloor
muted-foreground on backgroundsecondary copy9.41:111.32:17.82:19.52:14.5:1SC 1.4.3
muted-foreground on cardsecondary copy in a card9.41:110.48:18.25:18.64:14.5:1SC 1.4.3

Text pairs are held to 4.5:1 (WCAG 2.2 SC 1.4.3); borders, rings and chart axes to 3:1 (SC 1.4.11 non-text). Bold is the worst cell in the row — the one a brand fork has to keep an eye on.

Where it renders, how narrow it survives, and whether its lines are inside the coverage gate — three answers a consumer needs before the paste, not after the bug.

Render boundary
server component

Renders during SSR / RSC with no hydration cost. It can be imported from a server component without pulling the page into the client.

Minimum viewport
MIN_VIEWPORT = 320

Declared, not assumed. Below 320 CSS px the preflight contract draws a dev-mode outline — how to switch it on.

Coverage gate
100% × 4

Inside the v8 gate: lines 100, statements 100, functions 100, branches 100. A threshold under 100 only records how much you stopped caring, so there isn't one.

History

This component is at v1.2.0, first shipped in @interlace/ui 1.0.0. The version is stamped as a banner into the file the install writes, so the copy in your tree says which one you have — compare it with the number above before deciding whether to re-run the install.

No release note names this component yet. It shipped with the release above and has not changed since — see the full changelog for what moved elsewhere in the DS.

Import

2 named exports — pull the parts you need.

Public API
import { MIN_VIEWPORT, ReadingTime } from '@/components/ui/reading-time';

Anatomy

Extracted from the primitive's JSDoc header. The source is the only documentation that can't drift.

ReadingTime                        (span — data-min-viewport=320)
    ├─ {showIcon && <Clock />}       (optional 14px lucide outline, aria-hidden)
    └─ "<N> min read"                (text node)

API reference

Parsed from the type declarations in the source — the same file the install writes into your tree, so this table can't drift from the component you get.

ReadingTimeProps

Also accepts every <span> attribute.

PropTypeDescription
minutesnumberEstimated reading time in whole minutes. Rendered verbatim and emitted on `data-reading-time` for downstream consumers. Optional when `loading={true}` (no value to render).
showIconbooleanWhen true, prefixes the label with a small `lucide-react` Clock icon. The icon is decorative (`aria-hidden`) — the text label carries the semantic.
loadingbooleanWhen true, render a `<Skeleton variant="text" />` (short width) placeholder in place of the badge. Shape-matched to the typical "<N> min read" footprint so article-header metadata rows don't shift on data arrival.

Skeleton

Pass loading and the component renders a shape-matched <Skeleton /> in its own place — same box, so nothing reflows when the data lands. Below is the same story with loading={true}.

Reading Time — loading stateprimitives-readingtime--loading
Usage
<MIN_VIEWPORT loading={isPending} />

Accessibility

Every story for this component is rendered headlessly and checked with axe-core (wcag2aa, wcag22aa, best-practice, ACT) on every PR. That gate has no continue-on-error, so what ships has zero known violations.

What follows is what static analysis can see. Axe cannot press a key and never sees an overlay open, so the operable-without-a-mouse claim lives in Behavior instead, where the keyboard path is replayed step by step.

Focus + keyboard behaviour
Native element semantics — no interaction layer to get wrong.
Focus ring (WCAG 2.2 SC 2.4.13)
Not focusable — no focus indicator required.
Reduced motion
No animation to gate.
ARIA in the source
None — semantics come from the element or the Base UI primitive rather than hand-written ARIA.

Examples

3 more states from the same story file.

R-rule compliance

Every primitive in @interlace/ui models to the portable 26-rule floor enforced by the componentApi ESLint preset. The cells below pin exactly where each rule applies in this file.

RuleConceptWhere
R4Extends native el`React.ComponentProps<'span'> & ReadingTimeProps`
R6data-slot on root`data-slot="reading-time"`
R7className merged + ...rest`cn(BASE, className)` + `{...props}`
R8No `isXxx``showIcon` is a presence flag, not a state machine
R14Declares min viewport`data-min-viewport={String(MIN_VIEWPORT)}` + exported const
R18Tailwind onlyZero inline `style`; utility classes only
R19Tokens only`text-muted-foreground` + `text-sm` + `gap-1` token utilities
R20AA contrast`--muted-foreground` clears AA on `--background`
R25Server componentNo hooks → no `'use client'`
R26A11y from native el`<span>` is inert text; icon marked `aria-hidden`

Minimum viewport

This primitive declares MIN_VIEWPORT = 320 CSS px (DESIGN_PRINCIPLES #14). When mounted in a container narrower than this, the preflight contract draws a dev-mode outline so the regression is visible during local development.

Opt-in to the dev-mode warning
<body data-interlace-dev>...</body>

Add the data-interlace-dev attribute to the body in development builds only — preflight then outlines any primitive whose container is below its declared data-min-viewport.

Dependencies

Base UI primitive
Native / no Base UI dependency
Lucide icons
  • Clock
NPM dependencies
  • lucide-react

Source

The full implementation — components/ui/reading-time.tsx once installed.

114 lines · TypeScript
import * as React from 'react';

// @interlace/reading-time v1.2.0 — Interlace design system.
// Docs, props and live preview: https://ds.interlace.tools/c/reading-time
// What changed since: https://ds.interlace.tools/c/reading-time#history
// Generated banner — keep it, the upgrade diff reads this version.

/**
 * @interlace/ui — ReadingTime
 *
 * A compact "N min read" badge for article headers, blog cards and docs index
 * rows. It renders an inline `<span>`, so it sits beside a date or a tag row
 * without imposing block layout.
 *
 * The number is repeated on `data-reading-time`, so analytics, scrapers and
 * JSON-LD builders never have to parse the rendered text.
 *
 * The label is a literal: `{minutes} min read`, English, hard-coded. There is
 * no children slot and no way to translate it from a call site — localisation
 * means a wrapper at a higher altitude, not a prop here. Nothing rounds or

…94 more lines…

Registry JSON

The raw registry record — what the shadcn CLI fetches.