Repository navigation
Error Codes ui
github-actions[bot] edited this page Nov 16, 2026
·
2 revisions
Part of Error codes: every code @ultimat3/ui registers. x errors explain <CODE> --json prints the same row.
| Code | Means | Typical cause | Fix |
|---|---|---|---|
X_THEME_INVALID |
theme is not light or dark
|
a bad data-theme value |
set light or dark, or clear the attribute to follow the OS |
X_TOKEN_UNKNOWN |
design token role does not exist | a typo, or a raw colour that was never a token; a defineTheme() override of a role, radius or font slot that is not in the scale; or — as a Sass @error, so the stylesheet does not compile — a breakpoint rung handed to respond-to / respond-down / respond-between that is not in $breakpoints
|
use a role from @ultimat3/ui tokens; for a breakpoint, one of sm md lg xl 2xl — the @error lists them; see Theming
|
X_UI_CONTRAST_INSUFFICIENT |
a brand palette pairing does not meet WCAG 2.2 AA | a defineTheme() override whose RESOLVED channels — the app's overrides on top of the shipped palette — put a pairing in CONTRAST_PAIRS below its floor: 4.5:1 for text (WCAG 2.2 1.4.3), 3:1 for the focus ring (1.4.11), 1.4:1 for a border. Only pairings the brand can have CHANGED are measured, because blaming an app for the framework's own colours is how a rule gets switched off — and half a pairing is the usual defect: a new accent against the shipped white accent-fg. AA and never APCA: APCA is not a standard, and AA is the operative legal benchmark (EN 301 549, ADA Title II, the EAA) |
defineTheme({ colors: { <theme>: { '<role>': '<R G B>' } } }) — darken or lighten the named role's channels until contrastRatio() answers the required number — @ultimat3/ui exports contrastRatio and roleContrast to measure a candidate before shipping it |
X_UI_FORM_PATH_INVALID |
a form control name is not a usable field path | two conditions, one code. A control name — or a fields entry handed to formBinding — the path grammar cannot read (items.0.price where items[0].price was meant, or items[]); or two controls describing different shapes for one path, user beside user.name. Refused at DECLARATION, which is the only place either can be caught: a name attribute and a schema issue path are the SAME string, so a path no issue can ever equal is a field whose server errors land at the top of the form forever — indistinguishable from an app with no bug at all. The conflict half is refused rather than resolved because either answer silently drops one control's value, and the value dropped is something the user typed |
<Input name="items[0].price" /> — rename it to a segment, then .segment or [index] — "title", "items[0].price", never "items.0.price" or "items[]". For the conflict, rename one of the two controls: a path segment holds a value or a container, never both |
X_UI_INVALID_VALUE |
@ultimat3/ui received a value it cannot use |
NaN money or an invalid date reaching a formatting component; upstream icon data the glyph generator refuses — a body that is not JSON, a node that is not [tag, attributes], an attribute value or icon name off the allowlist; or — as a Sass @error — t.rem() / t.fluid() given a unit other than px or rem, t.fluid() given a viewport range that is empty or reversed, respond-between given $from at or above $to
|
fix the value upstream; formatting never guesses, and the icon generator never emits data it could not validate — data the pinned version published is bun run --filter @ultimat3/ui icons --bump, which moves LUCIDE_VERSION to the latest release and regenerates. A Sass refusal carries the literal replacement in its own fix: — write respond-between("md", "lg"), pass a px length, e.g. rem(24px)
|
X_UI_QR_CAPACITY |
text is too long for a QR code this component can draw |
<QrCode value> is more UTF-8 bytes than version 3 at error-correction level M holds — 42. @ultimat3/ui encodes versions 1–3 only (21×21 to 29×29 modules): the versions with at most one alignment pattern, no version-information block and one Reed-Solomon block, which is what keeps the encoder a dependency-free page rather than a library. A short URL (origin + '/' + 6-char slug) runs 25–30 bytes and fits; a full page URL does not. Refused rather than truncated, because a truncated link scans and then leads nowhere; the cause names the byte count and the ceiling |
<QrCode value="https://ex.test/p/1" /> — shorten the value: a short URL, not a full page URL — or draw it with a full-range QR library outside @ultimat3/ui
|
X_UI_RUNTIME_MISSING |
a host capability @ultimat3/ui needs is absent |
four conditions, one code, and the cause names which: no Solid runtime registered while a DOM render is under way (solid(), <UiProvider>); document/window absent when browserThemeEnv() is asked for theme control; Bun.CryptoHasher absent when hashing a brand stylesheet for CSP; the icon generator's own environment — no network to lucide-static, or no biome binary. Neither IntersectionObserver nor localStorage is one of them: InfiniteScroll returns without observing when the first is absent, and a theme read is wrapped in safeStorage for the private-mode Safari that throws on the second |
for the runtime, paste import { createContext, createEffect, createMemo, createRoot, createSignal, onCleanup, useContext } from 'solid-js'; at the top of the *.island.tsx and setSolidRuntime({ createContext, useContext, createSignal, createMemo, createEffect, onCleanup, createRoot }); as the first line of its mount(), above render() — x g resource <name> writes exactly those two lines, and a server render needs neither. Seven named imports, never import * as solidRuntime: the namespace registers too, and keeps every export of solid-js in the island chunk (14.8 kB minified, measured). Off the DOM, pass an explicit ThemeEnv: initTheme(myServerThemeEnv). For a CSP hash, call brandStyleCspSource() during build or SSR, never in browser code. For icons: bun install, then bun run --filter @ultimat3/ui icons
|
Ultimate — v31.44.0 As of 2026-10. The full-stack framework where the primary developer is an AI agent: bunx create-ultimate myapp → Getting started · live demo. MIT licensed. What npm serves is npm view @ultimat3/core version, never this line, and this footer is the only page that stamps a version.
Repository · Issues · Changelog · llms.txt
Edits to these pages are synced from wiki/ in the repository — change the file there, not the wiki, or the next sync overwrites it.
Start
- Getting started
- Installation
- Shapes
- Bare VM
- Project layout
- Migrating an existing app
- Compared to other stacks
Tutorials
- 1 · First app
- 2 · First feature
- 3 · Auth and admin
- 4 · Jobs and realtime
- 5 · Deploy free
- 6 · Growing up
Primitives
- The eight primitives
- Building your own base
- Actions
- Entities and migrations
- Policies and authz
- Queries and live queries
- Client data
- Jobs and workflows
- Scheduled tasks
- Routes and render modes
Capabilities
- Realtime
- Caching and invalidation
- Batching and preloading
- N+1 detection
- PWA and offline
- Client navigation
- MCP and AI
- Agents
- Admin dashboard
- Scraping
- Auth
- Notify
- Storage and uploads
- Feature flags
- SEO
- Static assets
Cross-cutting
- I18n
- Theming
- UI components
- Interface rules
- Timezones and dates
- Money
- Outbound HTTP
- Resource management
- Migrations and backfills
- Testing
- CI: the gate across parallel jobs
Reference