[pbroom]

parse() now implements CSS Color 4 instead of a handful of regexes:

• The 148 named colors plus transparent (conversion/named-colors.ts,
  packed into one name:hex string; *grey folds onto *gray).
• rgb()/rgba() and hsl()/hsla() in modern space syntax and legacy comma
  syntax, percentages everywhere CSS allows them (rgb 100% = 255), and
  plain numbers for hsl saturation/lightness.
• hwb(), lab(), lch() (CIE Lab D50), oklab(), oklch().
• color() with srgb, srgb-linear, display-p3, rec2020 (BT.1886 2.4
  gamma, as current CSS Color 4 / colorjs.io), a98-rgb, prophoto-rgb,
  xyz, xyz-d65 and xyz-d50, including values outside 0-1.
• Hue units deg/grad/rad/turn and negative hues; every parsed hue is
  normalized to [0, 360), matching the Color type's documented range.
• none is a missing component and behaves as 0 (CSS's rule for
  conversion); it is rejected in legacy comma syntax. Lab/OKLab
  lightness and LCH/OKLCH chroma are clamped at parse time per spec.

New conversion/xyz.ts holds the CSS Color 4 float64 matrices (XYZ D65 ->
linear sRGB, Bradford D50 -> D65, Rec2020/A98/ProPhoto -> XYZ) and the
Lab -> XYZ D50 conversion. color(srgb) reuses the existing sign-extended
sRGB transfer function export (p3ToLinearP3Into) rather than a new one.
A final finiteness check rejects values that overflow inside a
conversion (color(srgb 1e300 0 0)).

Tests: reference-accuracy compares every new syntax (all named colors,
random lab/lch/hwb/hsl/rgb% and extended-range color() samples) against
colorjs.io; max observed error is ~5e-15 (tolerance 1e-9). fast-check
properties cover hue normalization in every unit and toCss(oklch) ->
parse round-trips.

Bundle size: parse + toHex + contrastRatio grows 2.64 kB -> 5.13 kB
and the everyday toolkit 2.69 kB -> 5.18 kB, so their budgets rise to
5.2 kB and 5.25 kB (~70 B headroom). The named-color table cannot be
tree-shaken out because parse('red') must work; it is ~1.3 kB gzipped,
the color() / Lab matrices ~0.6 kB, and the parser itself ~0.6 kB.
Other budgets are unchanged. README/docs claims updated accordingly.

Part of a stacked set of PRs (#204 → #221) from the color-kit assessment. Validated per branch with pnpm build and pnpm test; lint, format, typecheck, size, artifact, preprod and agents checks pass at the top of the stack.

🤖 Generated with Claude Code

[pbroom]

• refactor(react)!: remove UI components; ship state and plane hooks only #249
• docs(react): rebuild the React docs around the plane hooks #248
• feat(react): add plane renderer, geometry and adaptive-quality hooks #247
• feat(docs): syntax highlighting palette for code samples #246
• feat(docs): native API map at /api/map #245
• docs: add concept pages, guides and entry-point narratives #244
• feat(docs): live plane hero on home and the example system #243
• feat(docs): generated API reference from TypeDoc JSON #242
• refactor(core)!: derive plane query budgets from step counts and drop PlaneWithSense #241
• fix(react): render input aria-label once, on the inner input #240
• fix(driver): map absolute percents as range positions and keep tiny-step precision #239
• fix(core): uncap saturate chroma and resolve planeHue as an OKLCH hue #238
• fix(driver): reject unknown gamuts and align validation error types #237
• chore(docs): remove Sandpack, the shadcn kit and the legacy docs shell #236
• docs(core,driver,react): document the public API #235
• chore: pin control-kit to a commit with its own pnpm workspace #234
• docs: update implementation backlog for the contrast solver replacement #232
• refactor(react)!: remove ColorPlane's deprecated edge option and webgl renderer alias #231
• fix(driver): validate the gamut in getColorAreaFallbackPoint #230
• feat(driver,react): keep the previous hue when an achromatic color is entered #229
• refactor(core)!: replace the hybrid contrast solver with chroma-column tracing #228
• perf(core): trim what contrastRatio pulls in #227
• perf(core): pack the named-color table #226
• feat(core): point 'p3' users to 'display-p3' #225
• chore: ignore local .claude files in prettier #224
• refactor(core)!: retire the legacy contrast-region engine #223
• fix(core): keep hybrid contrast contours connected through folds #222
• chore: add changesets for the assessment stack #221
• docs: generated API reference and repo polish #220
• chore: adopt changesets for versioning and release notes #219
• chore: fix facade peers, licensing, and lint ignores #218
• refactor(react): reuse core contrast and transfer functions #217
• refactor(core)!: make the contrast-region engine explicit #216
• refactor(core)!: remove pre-launch aliases and trim the root export surface #215
• refactor!: name the Display P3 space 'display-p3' everywhere #214
• refactor(driver): share pointer drag throttling between slider and area #213
• feat(react): keyboard, ARIA, disabled, and focus support for sliders and areas #212
• fix(react): stable refs, WebGL context loss, and handler composition #211
• fix(react): apply controlled updates against the latest snapshot #210
• feat(core): selectable gamut mapping method #209
• fix(core): compute contrast from unrounded values #208
• fix(core): consistent achromatic hue handling and single transfer function #207
• feat(core): parse CSS Color 4 syntax #206 👈 (View in Graphite)
• fix(core): reject malformed color input instead of producing NaN #205
• chore: add fast-check and axe-core test dependencies #204
• docs: graphics and performance APIs demo page #203
• feat(core): tuple and typed-array interop for GPU and three.js #202
• feat(core): allocation-free *Into variants for hot paths #201
• feat(core): interpolation space option for mix/interpolate/generateScale #200
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

[greptile-apps]

Confidence Score: 4/5

[Medium risk] Adds CSS Color 4 parsing support to the color library.

The PR should not merge until color() rejects unsupported space names.

Findings

1.  Invalid color spaces are accepted ▶

Summary

This PR expands parse() to handle named colors and CSS Color 4 functions and spaces, adds conversion matrices and reference tests, and updates documentation and size budgets.

• The new color() dispatch also accepts unsupported space names that coincide with top-level color functions.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  Input["color(rgb 1 0 0)"] --> Token["space = rgb"]
  Token --> Shared["Top-level rgb handler"]
  Shared --> Result["Color returned instead of rejection"]

Loading

_{Reviews (1) · Last reviewed commit: "feat(core): parse CSS Color 4 syntax"}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
color-kit	Ready	Preview	Oct 10, 2026 7:01pm UTC

[pbroom]

Merge activity

• Oct 10, 6:47 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• Oct 10, 7:00 PM UTC: Graphite rebased this pull request as part of a merge.
• Oct 10, 7:00 PM UTC: @pbroom merged this pull request with Graphite.