Uses its own close icon.
``` A name registered as `null` draws no glyph while the button, its stable part and its accessible name stay — the same meaning `closeIcon={null}` already has. Icons never touch an element's part, className, `aria-label` or keyboard behavior; only the mark inside changes. `icons` merges by name. Like `messages`, a partial map leaves everything it omits alone; unlike `messages`, an icon value is an opaque node and is carried over by identity rather than deep-merged into, so registering a React element hands that exact element to the component. ### Reading an icon in your own component `useCratisIcon()` returns the same resolver Components uses internally, for a product component that wants to follow the registered vocabulary: ```tsx import type { ReactNode } from 'react'; import { useCratisIcon } from '@cratis/components'; interface RemoveButtonProps { icon?: ReactNode; onRemove: () => void; } export const RemoveButton = ({ icon, onRemove }: RemoveButtonProps) => { const resolveIcon = useCratisIcon(); return ( ); }; ``` The vocabulary replaces a **glyph**, never an element that publishes a part. `ProgressSpinner` is the example that draws the line: its ring looks like an icon, but it is an `svg` carrying the `svg`, `track` and `range` parts, and a registered icon that replaced it would silently delete three parts a product may already be styling. Sites like that keep their own markup, and a product restyles them through the parts they publish. `expand` has two built-in glyphs today — `⌄` on a `Dropdown` trigger and `▾` on a `ComboBox` trigger. Registering `expand` makes both consistent; registering nothing leaves each as it is, so no existing rendering changes. ## Mount the toaster Pass `toaster` to mount the app-wide notification region: ```tsx