Loader
Three accent LEDs breathing in sequence — the device thinking. role=status; reduced motion holds the dots steady. Consumes var(--echo-*).
Feel Three dots pulsing in turn — the device is thinking.
Preview
Or let the agent fetch it: get_component("loader") on the Echo MCP server.
Installation
First time? Run npx echo-ui-cli init once — it sets the project up, and add refuses to run before it.
At a glance
- Version
- 0.3.0
- Weight
- 250 B · 388 B of CSS (minified and gzipped; React not counted)
- Reduced motion
- The dots stop pulsing and hold at a steady glow.
Usage
import { Loader } from "@/echo/loader";
<Loader label="Saving" />Composition
Loader
Examples
Default
Inline loading indicator.
<Loader />Small
Fits inside a button or chip.
<Loader dot={6} label="Saving" />Accessibility
role="status"named bylabel, so it is announced when it appears.- Remove it as soon as the work is done — it is announced when it appears, and a loader left on screen says the wait is still going.
Tested against WCAG 2.2 AA on every release:
axe— No axe violations, in the component's own gallery and on its page.keyboard— Every action is reachable and operable from the keyboard alone.focus-visible— Focus is visible on every focusable part, in normal and forced-colors mode.forced-colors— State stays visible when the look's colours are replaced by the system's.target-size— Every target's real hit area is at least 24×24px, at every density.reflow— Content reflows into 320px and survives a doubled text size.
Not covered: screen-reader: not yet verified by a person. Everything above is a machine check; a person has not yet driven this component with a screen reader.
Motion & sound
- Reduced motion
- The dots stop pulsing and hold at a steady glow.
Props
| Prop | Type | Default |
|---|---|---|
dotDot diameter in px. | number | 9 |
labelAccessible status text. | string | "Loading" |
Anti-patterns
- Never spin it — Echo has no spinners; the device pulses, it doesn't rotate.
- Never stack Loader with skeletons in the same region; pick one loading voice per surface.
Changelog
- Every item needs
echo-ui-core0.3.0 (all components). The drawn device, readability past AA and the design tests live in core, and the components that use them are built against it, so each item now declaresecho-ui-core >=0.3.0 <0.4.0. Update core with the items:npm install echo-ui-core@^0.3.0(or your package manager's), thennpx echo-ui-cli update. An item whose files didn't change is the same code under a new version; the 0.2.0 files stay published. - Components whose shadow is a recipe read it by name. 71 shadows in 54 items now say
var(--echo-shadow-<name>, <the same shadow>), so they look exactly as they did (every docs page was compared before and after) and follow a theme's recipes. Scope declares the recipes that read the accent again, so a Scope's own colour still reaches its focus rings and glows, and reflective screens do the same for theirs. Shadows that move with their part (a cap's drop as it's pressed) stay in the component. - Comments only, no behaviour change. Comments in the component source used to cite documents, milestones and ticket numbers from Echo's own planning, none of which exist in your project. The citations are gone and the sentences around them stay. Where a comment was only a citation, it now says what it meant. Three development warnings (
HardwareButton'sengraved/captionchecks andStatusDot's missing-label check) also dropped the ticket code at the end of the message.echo-ui diffwill show changes in most items; none of them are to code. - An item's version is now a function of declared data, not of how the changelog is formatted. The version an item ships under is published once and never rewritten, and it used to be inferred from prose: a regex for a bolded "Breaking" run across the whole unreleased section, and attribution by "does a bullet mention this name in backticks". One breaking entry therefore moved every item that changed that cycle, and an entry explaining that "
MenuandSheetare unchanged here" filed itself as a change to Menu and Sheet — which it really had. - The agent brief says Echo has not shipped.
llms.txtand the MCP server's instructions led withnpx echo-ui-cli init, and that name on npm is a reserved stub with no executable — so a model following the brief wrote an install step that fails with npx's own error. The brief now opens with the caveat, and the docs carry it on every surface that shows a command. One switch (CLI_RELEASED) silences all of them at launch, and a test refuses to let one move without the others. Affectsall componentsonly in what the brief says about installing them; no item's props, CSS or rendered semantics change. - Echo's home is
echo-ui.com. The registry, the docs and the packages all move to it fromecho.nawwara.studio. Nothing was published under the old host, so noecho.jsonanywhere points at it and there is nothing to migrate — this is the last release where that is true. - Weights, line heights, letter-spacing, z-index, border widths and icon sizes come from the theme scales in
all components, with the old value as a fallback, so components keep working withecho-ui-core@0.0.1. Strays moved to the nearest step: most by under a pixel; HardwareButton icons are 14/16/20px (were 15/17/19). - Content now reflows into a 320px screen (400% zoom) and survives a doubled browser text size (WCAG 1.4.10, 1.4.4), across
all components.Select's 180px floor,NumberField's readout,SegmentedandStepsas flex items,EmptyState's grid columns, andAvatar's fixed-pixel disc all gave way;Panelcounts its padding inside a width you set (box-sizing: border-box), so a<Panel style={{ width: 220 }}>is now 220px wide overall rather than 260px.