brand-ui — MapRoute

import { MapRoute } 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 MapRoute 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 MapRoute up before writing code: `npx -y @elabs-ai/components-cli docs MapRoute` 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

Dashed

API

`MapRoute`

Prop	Type	Description
`id`	`string`	Optional unique identifier for the route layer.
`coordinates`required	`[number, number][]`	Array of [longitude, latitude] coordinate pairs defining the route — or, in a `<MapCanvas plan>`, [x, y] pairs in plan units.
`color`	`string`	Line color as a CSS color value. Defaults to the theme's `--primary` token.
`width`	`number`	Line width in pixels (default: 3).
`opacity`	`number`	Line opacity from 0 to 1 (default: 0.8).
`dashArray`	`[number, number]`	Dash pattern [dash length, gap length] for dashed lines.
`direction`	`MapRouteDirection`	Draw chevrons along the line to show which way it runs (default: "none"). A conveyor, a one-way aisle and a walking route all need this, and an arrow is a second channel that greyscale keeps.
`directionSpacing`	`number`	Distance between chevrons in px (default: 80).
`onClick`	`() => void`	Callback when the route line is clicked.
`onMouseEnter`	`() => void`	Callback when the mouse enters the route line.
`onMouseLeave`	`() => void`	Callback when the mouse leaves the route line.
`interactive`	`boolean`	Whether the route is interactive — shows a pointer cursor on hover (default: true).