brand-ui — MapArc

import { MapArc } from "@elabs-ai/components-maps";

Install

npm install @elabs-ai/components-tokens @elabs-ai/components-ui @elabs-ai/components-maps

Skipping the @source line is the most common first failure: Tailwind does not scan node_modules, so every component renders unstyled. The one-time wiring

Prompt for your coding agent

Paste it into Claude Code, Cursor, Codex or any other coding agent. Text in [brackets] is yours to fill in.

Add the brand-ui MapArc component (from @elabs-ai/components-maps) to this project.

1. Read https://elabs-ai.com/llms.txt first: it maps every package and the rules. If you can use MCP servers, connect https://elabs-ai.com/mcp and use its search, docs and tokens tools. If not, run the same lookups in the terminal: `npx -y @elabs-ai/components-cli search "<what you need>"` and `npx -y @elabs-ai/components-cli docs <Component>`.
2. Look MapArc up before writing code: `npx -y @elabs-ai/components-cli docs MapArc` prints its real props, variants, what it pairs with and what to avoid.
3. If @elabs-ai/components-maps is not installed yet: `pnpm add @elabs-ai/components-tokens @elabs-ai/components-ui @elabs-ai/components-maps` (or `npm install @elabs-ai/components-tokens @elabs-ai/components-ui @elabs-ai/components-maps`). If this is the first brand-ui package in the project, wire it once: import `@elabs-ai/components-tokens/styles.css` plus the `themes/light.css` and `themes/dark.css` stylesheets in the CSS entry, add one Tailwind `@source` line per installed @elabs-ai package (Tailwind does not scan node_modules, so without it everything renders unstyled), and wrap the app root in `ThemeProvider` from `@elabs-ai/components-tokens`.
4. Use it here: [the screen or file, and what it should show]
5. Rules: use only @elabs-ai/components-* components and the semantic tokens — no raw colours, no raw font sizes, no arbitrary Tailwind values. Look up each component's real props with the docs tool before you use it; never guess a prop.
6. Done means: the typecheck passes, `npx -y @elabs-ai/components-cli audit src --strict` reports nothing, and you have opened the app and looked at every screen you touched in the light and the dark theme.

Examples

2 live examples

Globe With Hover

API

`MapArc`

Prop	Type	Description
`data`required	`T[]`	Array of arcs to render. Each arc must have a unique `id`.
`id`	`string`	Optional unique identifier prefix for the arc source/layers. Auto-generated if not provided.
`curvature`	`number`	How far each arc bows away from a straight line. `0` renders straight lines; higher values bend further; negative values bend to the opposite side. Arcs cross the antimeridian via the shorter direction. (default: 0.2)
`samples`	`number`	Number of samples used to render each curve. Higher = smoother. (default: 64)
`paint`	`MapArcLinePaint`	MapLibre paint properties for the arc layer. Merged on top of theme-aware defaults (`line-color` = the `--primary` token, `line-width: 2`, `line-opacity: 0.85`). Any value can be a MapLibre expression for per-feature styling; every field on each arc datum (besides `from`/`to`) is exposed via `["get", ...]`.
`layout`	`MapArcLineLayout`	MapLibre layout properties for the arc layer. Defaults to rounded joins/caps.
`hoverPaint`	`MapArcLinePaint`	Paint properties applied to the arc currently under the cursor. Each key is merged into `paint` as a `case` expression keyed on per-feature hover state, so only the hovered arc changes appearance.
`onClick`	`(e: MapArcEvent<T>) => void`	Callback when an arc is clicked.
`onHover`	`(e: MapArcEvent<T> \| null) => void`	Callback fired when the hovered arc changes. Receives the cursor's lng/lat at the moment of entry, and `null` when the cursor leaves the last hovered arc.
`interactive`	`boolean`	Whether arcs respond to mouse events (default: true).
`beforeId`	`string`	Optional MapLibre layer id to insert the arc layers before (z-order control).