What's New

Release notes and changelog for all packages.

0.7.16

Experimental APIs
  • astryx experimental theme editor: a new accent or neutral color keeps the base theme's own secondary text shade on selected items and rows, a dropzone, numbered citations and segmented-control labels while that shade still reads at 4.5:1; it moves only when it no longer does, and the note says it was kept readable. A write that repeats what the base theme already shows is no longer listed as a styled change. (#11468)
  • astryx experimental theme editor: the app copy in src/themes/<theme>/ is written exactly as theme build of its source writes it (the build header names that source), so theme build --check and astryx doctor read it as current, and a stable rebuild of it leaves it the editor's (the next change writes it again). A change that fails after its build no longer leaves the refused build in the app copy: the copy is written only once the change is saved. (#11468)
  • astryx experimental theme editor show: a show that is refused (or fails to render) leaves the app copy in src/themes/<theme>/ as it was; the copy is written once show succeeds. System files such as .DS_Store in the copy folder no longer stop the copy; a file of yours there does, and wiring then gives the steps by hand, naming that file. (#11468)
  • astryx experimental theme editor: CSS read with the current specifications' grammar. (#11378)
    • The editor also reads the current specifications' grammar from @csstools/css-syntax-patches-for-csstree (a new dependency, pinned). It adds about 0.1 MB unpacked to the install (one 79 KB JSON file, no dependencies of its own), and loads only when the editor checks a CSS value; no other command loads it, and startup is unchanged. A property MDN marks obsolete but the specifications still define, as browsers ship it, is taken: font-stretch, so the font shorthand split names a command that works.
    • A negative number the current grammar ranges at 0 or more is refused on a part (line-height -1, gap -2px), with the positive value as the suggestion.
    • A color-mix() share outside 0% to 100% is refused for tokens, part colors and the color dials, and the mix with the share at its limit is suggested.
    • A font size or weight given alone to font on a part (small, 1rem, 700) is suggested as font-size or font-weight, never as a family.
    • A relative color that keeps its channels (rgb(from red r g b)) and light-dark() with the same color twice are read as that color. A color-mix() in a space the editor does not mix in, or a relative color that changes its channels, says so and suggests the nearest color it can work out.
  • astryx experimental theme editor: more refusals and notes that are true. (#11378)
    • A negative percentage the current CSS grammar ranges at 0 or more is refused on a part (line-height -50%, gap -10%).
    • A color-mix() share may be written as any CSS percentage (5e1%, +50%, calc(50%)).
    • Line-height tokens (--text-*-leading) take a number with no unit, as Core multiplies them by a text size; 1.5em and 150% suggest 1.5.
    • headings in other letters or as a weight number suggests the word meant (BOLD is bold), and a weight number the nearest weight rung (800 and 900 are heavy), never a lighter one.
    • A whole-theme font under fonts set for body and headings says which role fonts it sits under and how to clear them.
    • A font one of the editor's own presets leads with (Comic Sans MS) gets no "must load" note.
    • text-size more or less at the end of the dial's range suggests the base font size token, never a size the dial refuses.
    • A CSS font value on a part made of keywords (italic bold, bold 1rem) is split into its longhands, never a family; after the size, the rest is the family, as CSS reads it (1rem bold is size 1rem with the family bold).
  • astryx experimental theme editor: number tokens read as CSS reads them. (#11378)
    • Only the tokens Core's stylesheet multiplies by a size inside calc() (the line heights) refuse a unit; weight tokens take the font-weight keywords again (bold, normal), so a theme saved with one stays editable.
    • Numbers are read as the browser reads them: 1.5e0, +1.5, 15E-1 and 1.5EM are numbers, and a color-mix() share like 50.% is refused.
    • A CSS font value on a part with a size and line height (1rem/1.5) or a size written as math (calc(1rem + 2px)) is split into its longhands; a part named twice (bold bold) is refused, never written as a family.
  • astryx experimental theme editor: weights on phones, and values read as CSS reads them. (#11419)
    • Heading and text weights (the headings weight dial, --text-*-weight tokens) now apply on phones too: they are written into the phone rules the base theme sets, as font families are.
    • A token set to var(--x, <fallback>) checks the fallback as the token's own kind.
    • Size tokens and color channels read numbers as CSS does: 1.px and rgb(255. 0 0) are refused (with 1px suggested where that is all), and +4px and 4e+1px are taken.
    • vibrancy suggests the value meant (MORE is more, 70% and 7e1 are 70), and no value when the theme has no color to saturate.
    • The headings result lists its weights in words, not [object Object].
    • The whole-theme and role font take a family alone: a size, a weight or a whole CSS font value is refused with the family, and the base size or headings command where it applies.
  • astryx experimental theme editor set: when a part does not read the token named, the suggestions name only tokens of the same kind (a weight goes to a weight token, never to a size or a line height). A var() fallback is checked wherever it sits (inside calc(), max(), color-mix()), and an empty fallback on a typed token is refused. A size token given a bare number suggests that number in px (16 → 16px), and text-size 20px, 2e1, +20 and 1.25rem suggest text-size 20. (#11419)
  • astryx experimental theme editor: fallbacks, saved font dials and size suggestions. (#11419)
    • A part value's var() fallbacks are checked against the property (padding 'var(--nope, red)' is refused), as token fallbacks are.
    • A saved font dial that set would refuse (a CSS keyword such as inherit, a size, a whole CSS font value) is reported with the commands that fix it, and never built.
    • A size one slip from a valid one suggests that size: 16 px and 16pxx suggest 16px, 1,5rem suggests 1.5rem. text-size suggests the nearest size it takes: 20 px and 125% are 20, and a size past either end is that end.
  • astryx experimental theme editor: font math is accepted as the CSS generic family it is; the generic families are read from the CSS grammar. With an exact --font-size-base set, how 'bigger text' steps that token (14px to 17.5px) instead of offering a text-size the token would mask. A color dial edited by hand to a see-through, system or variable color ([#2563](https://github.com/meta/astryx/pull/2563)ebcc, transparent, Canvas, var(--x)) is refused by name with the undo that removes it, instead of building a gray accent. A value typed with full-width characters, a trailing dot or a CSS comment (18, 18., #2563eb, [#2563](https://github.com/meta/astryx/pull/2563)eb /* brand */) is suggested as the value meant. set refuses a var() loop that closes through a token in the theme's own <theme>.theme.ts. show notes each token the theme's own source sets that a whole-theme dial also writes. (#11419)
  • astryx experimental theme editor: suggestions keep the value meant, and fractional text sizes say how they build. (#11419)
    • An exact token refused only for how its value was typed (a trailing ;, a comment, quotes around it, full-width #) suggests that same value, not a stock one.
    • A font name that needs quotes (Font Awesome 6 Free) on a font token or a part's font-family is suggested quoted, as the font dial writes it.
    • A fractional text-size (15.5) is saved as the whole pixel the type scale builds, and the result says so.
  • astryx experimental theme editor how: mode phrases, questions about what is set, the focus ring, and changes by an amount. (#11378)
    • "The same accent in light and dark" sets both modes, and a trailing "and dark mode only" still makes the theme dark-only.
    • A step that cannot move (badges already fully round) says so, with no command that would be refused.
    • Questions about what is set now or the choices ("how round are the cards now?", "what are the available corner values") get show and the lookup, never a change.
    • "Remove the focus outline" sets its width to 0 and says what that costs; "outline offset" and "focus ring offset" set --focus-outline-offset.
    • "Decrease the radius by 2px" moves the corners from the theme's own radius now (its corners setting applied); a change by an amount on a part points to its current value instead of setting the amount.
    • "Caret color" sets caret-color; placeholder text and the selection highlight say they have no setting.
    • Screen-size, print and device conditions ("below 600px", "on tablets", "the print version") say the editor has no such conditions, instead of reading "600px" as a radius or "tablets" as tables.
    • "Text less black" lightens the text.
    • Each item of a list keeps its own values: "headings 32px bold, body 16px regular, captions 12px" sets the headings and the body as asked, with no contradiction, and "captions" (no part) takes nothing from its neighbors.
  • astryx experimental theme editor how: a negated mode, the CSS cursor, device words beside an ask, and labels. (#11378)
    • "Don't touch dark mode, make the accent orange" changes light mode only.
    • cursor: pointer sets the CSS cursor; only "caret" or "cursor color" is the text cursor's color.
    • A device or print word ("cramped on mobile", "when printing") no longer drops the ask: the rest is answered, with a note that the editor has no such conditions.
    • A question about one part's state or group ("which parts are in the inputs group", "how round are the cards now?") gets that part's lookup as well as show.
    • "Not so round" is one step less; "avoid pure black text" picks a near-black; "flat cards, not flat buttons" changes only the cards.
    • NaNpx and Infinitypx are refused as not numbers; 1e3px is 1000px.
    • Labels are the field label part (a checkbox's or switch's own label when named); "visited links" says a link has no visited state set can name.
    • Tailwind border-2 is a 2px border width and rounded-full a pill; .btn-primary { … } is the primary button only.
    • "Remove all my changes" takes back every setting; a question in a script how cannot read gets no guess.
  • astryx experimental theme editor how: "2px rounder" is a change from the corners now, and "all corners like the buttons" copies the buttons' radius. (#11378)
    • An amount with a comparative ("2px rounder", "2px sharper", "8px larger") is a change from the value now: the theme's corners move from its own current radius (its settings applied, not the base theme's), and a part's corners move from the radius token it reads. Anywhere else ("4px wider") how says set takes the new value instead of setting the amount.
    • "All corners like the buttons" sets every other radius token to the one buttons read.
  • astryx experimental theme editor how: a negated dark mode, undo of what is set, typed times and transforms, and the right targets. (#11419)
    • "Except in dark mode", "but not in dark mode" and "leave dark mode alone" change light mode only; "not pure black" is a near-black and "not pure white" a near-white.
    • "Undo the corners" on a theme that sets no corners says there is nothing to undo.
    • "animation-duration 0s" is 0ms; "translateY(-2px) on hover" is a transform on hover; "shrink headings by 20%" says set takes the new value; "fade in tooltips" says the tooltip has no motion of its own.
    • "Why are my buttons black" is a lookup, never a change; "is my theme valid", "how many dials" and "list every change" get the command that answers them.
    • "radius sm/lg", "setRadius(4)" and "½rem" are read as values; "#22c55e in light, #4ade80 in dark" sets the accent for each mode; two-word CSS color names ("midnight blue") are the CSS color.
    • "Text on the accent is hard to read" sets the on-accent text color that reads in each mode; "5 lines tall text box" sets the text area's height in lines; "dropdown shadow" is the dropdown's menu; "checkboxes green" is the checked fill.
  • astryx experimental theme editor how: an amount in rem or em with a comparative ("0.5rem rounder") is a change from the value now, counted at a 16px root, and "tighter", "roomier", "looser", "bolder" and "heavier" read as comparatives too. Where how cannot work out the new value, it says to set the value now plus or minus the amount. (#11419)
  • astryx experimental theme editor how: a confidence gate, and dislikes, take-backs and dark-mode selectors read. (#11419)
    • When a question is a question ("is the card too round?"), says "tell me" or "but not too", or asks to "stop" something, how gives the lookup and asks for the change in words instead of guessing a write; "explain X" is the lookup of X.
    • "I hate the shadows", "skip …" and "not a fan of …" ask for none of it when that is the whole ask.
    • A change on one member of a group ("the text area") carries --only, so it does not reach the whole group.
    • "3 pixels sharper", "take 2px off" and "remove 4px from" move the value down from where it is.
    • "darkmode", html.dark .card {…} and @media (prefers-color-scheme: dark) {…} scope the change to dark mode.
    • "Take back the shadow change" and "shadows like before" undo only what the theme sets, else say there is nothing to take back.
    • "Pointer cursor on hover" sets the cursor; "opened accordion title" is the open state; "squre" and "eckiger" are square; "cards look flat" adds depth; "darker while being clicked" is the pressed state.
  • astryx experimental theme editor how: every change by an amount or a direction starts from the theme itself, not the base theme. A darker or lighter color starts from the theme's own color in each mode, and says when it is already as dark or as light as it goes; a bigger text size on a part starts from the size the theme set there; a part's corners moved by an amount start from the radius the theme set on it. Token lookups show the theme's own value. (#11419)
  • astryx experimental theme editor how: the confidence gate works per clause, and a one-mode change never removes a mode. (#11419)
    • A clause that is a question, a "tell me", a "stop …" or a "don't touch …" holds back only itself: "stop making the buttons so round, make them square" makes them square, "don't explain, just set the accent to crimson" sets crimson, "don't touch spacing, just make text larger" changes only the text. A whole question ("can the cards be rounder?", "are buttons too round?!") gets the lookup; "can you make …" is an ask.
    • Questions without a question mark ("are my corners too round", "does it use a shadow on cards") are lookups; suggestions ("why not square buttons", "what about a teal accent", "is there a way to …") are asks. Sarcasm ("yeah, because …", "just what I wanted", "…, nice") gets no write.
    • "Enough with X", "quit with X", "nobody asked for X", "who needs X", "loathe X", "X 👎" and "❌ X" ask for none of X; "I hate it" after a description leaves the description as the ask.
    • "Too airy" is tighter, "headings too thin" bolder, "not bright enough" brighter.
    • "Keep the dark mode accent, change only light to violet" sets the light accent; a light-only or dark-only theme only when the ask is about the theme's modes.
    • "Links not underlined until hover" removes the underline and adds it on hover.
  • astryx experimental theme editor how: "bolder" or "a bit lighter" headings move one rung from the headings rung the theme sets (and say so when there is no rung further), and "a bit bigger" text moves a numeric text size by the dial's own step. how <theme> <question> takes a first word that names an existing theme as the theme, as set, show and undo do. (#11419)
  • astryx experimental theme editor how: a write only for a direct ask. A clause that is a condition ("if the corners are round, …", "unless …"), an indirect question ("I wonder if …", "is 4px a good radius", "would #333 work", "should corners be 6px or 8px"), a double negative ("don't not round …") or a check ("can you check if …", "just checking: …") gets the lookup and a request to say it as an ask, not a guessed change. Politeness ("if you can, …") is not a condition. "Can the buttons be rounder?" and "can I get a serif font?" are asks; a question followed by an ask ("whats the padding on cards make it 12", "do badges have borders? remove them either way") answers the ask, with "it" or "them" read as what the question named; "dark page #0b0b0f" sets the dark page. (#11419)
  • astryx experimental theme editor how: "more muted", "pastel", "duller" and "subdued" lower vibrancy and "less muted" raises it (a token name such as --color-background-muted is never read as the word); "less light" or "less thin" headings are one rung bolder, "less heavy" one rung lighter, "less tight" wider letter spacing; a weight question lists only the weight tokens a part reads; "too dark" asks for lighter and "too light" for darker; "no big gaps" is less spacing; sarcasm anywhere in a question ("great, even more shadows, just what I wanted", "…, nice") holds back every clause. (#11419)
  • astryx experimental theme editor how: a write for a clause that reads as an ask: an imperative, a thing with a value, a style word with a part, a wish about a named thing, or a description of the look wanted ("the page is white"). A tag question ("cards have a shadow, right?"), a hypothetical ("imagine …", "consider …"), a condition ("whenever …", "once …", "should the cards …"), sarcasm or a double negative gets the lookup instead. "nuke", "zero out", "sharpen", "flatten", X++ / X-- and X: off say which way to go; "dark.page=#…" and "dark mode only: accent #…" set dark mode. (#11419)
  • astryx experimental theme editor how: "show me …" and "give me …" are lookups. "decrease", "shrink", "trim", "minimize" and "scale down" mean less. "Only when dark mode is on" and "except in dark mode" keep their mode. Removal words in other languages and 🚫 remove; "X are heavy" lightens; "don't touch the buttons" and "leave the corners" never write the excluded part. Inline list numbers ("1. … 2. …") are breaks, a color asked for a part in a long note stays with that part, and "tooltips darker" stays a color. (#11419)
  • astryx experimental theme: the thirteenth pass of fixes. (#11378)
    • undo leaves out what this Core refuses in the step it goes back to. A saved setting that names no design token or CSS property, or a property with no part, is reported.
    • show builds an own change to <name>.theme.ts, and names a theme source that no longer builds. Its colors say where the theme source wins over the generated shade.
    • A setting covered by a later one that spreads over its part is named in set and show.
    • corners 2e1px and +4px are sizes. A state is refused for padding on a part whose padding Core sets from the plain value only. --state disabled also matches a wrapper whose input inside is the one disabled. how <part> lists the states set takes there.
    • new suggestions keep every option given; --like twice is refused. More suggestions run as printed in JSON. The merge snippet's paths start from the generated themes module's folder. The help names experimental theme compile to build an editor theme again.
  • astryx experimental theme editor: corners set for a state (corners pill --on button --state hover) are accepted, and the result names the part's derived radius variable, which Core sets from the plain value only. Padding that a part expands into container spacing is refused with a state, judged on the part named (--only keeps it to one member of a group). focus-within is taken on a part that holds content. A one-mode value that is not a color is refused for that reason first. (#11378) show leaves every file in place when the theme source does not build, and names a token value that is not text. A theme named by a path or in capitals (use ./themes/t, use T) gets the editor-theme answer.
  • astryx experimental theme: show builds a change in a module the theme source imports, and an unreadable build with a broken source line says what to put back. compile of an editor theme from a subfolder names the run from the app root. --state disabled reaches the inner control only on form controls styled on a wrapper, never a whole button group. A step back writes the same color files. (#11378)
  • astryx experimental theme editor: every suggestion a refusal gives runs and does what it says. undo t Corners reads the setting name in any case, and a near name (undo t corner) suggests undo t corners, never a bare undo t that would step back another change. A hand-edited setting suggests a value to set only for a token whose value has the wrong type. A flag given twice suggests its first value that the flag takes (--like neutral, --corners small, --section actions, and for a color dial the first that is a color: --accent banana --accent red suggests --accent red), or drops it. A folder of your own files suggests a free, valid theme name (u-2). After damaged or lost settings, the note says undo steps back to the settings from before the last change, and that the last change itself is not kept. A corrected new keeps every other option given, with --like in another case read as the built-in theme it names. (#11378)
  • astryx experimental theme editor: --state disabled reaches the control inside only on a part that holds one control (a typeahead), never a radio list, input group or field. corners none, sharp, zero and 0% are square; spacing none names the tightest rung. Undoing a part's state setting names the group's setting for the same state. focus-within is taken on a part that holds content in a prop (a chat composer's input) or children (a popover). (#11419) A token in your own theme source that is not text, alone or in a pair, is refused before anything is written, with an example of the token's own type. A helper imported as ./x.js counts when only x.ts exists. A set refused for your own file suggests reading it. The compile help lists the editor-theme refusals.
  • astryx experimental theme editor: an invalid theme name suggests a name new takes (my-neutral for a built-in theme's name, a free numbered name for a taken folder), and says "a theme here already" only for the same name in another case. new on an existing theme suggests set <theme> base <the --like given> and a free name with the same options. A setting listed twice by hand names both values, and setting it to one value or undoing it fixes the list, without stepping back another change. With the built module missing, set and undo say the token changes are not listed, and never that the change shows nothing. (#11419)
  • astryx experimental theme editor show follows every local file the theme source reads, as the build resolves it (./tok to tok/index.tsx, ./c.cjs to c.cts, ./j.jsx to j.tsx), including your own files in the theme's tokens/ folder; only the editor's generated palette files there are left to their own stamps. A pair of values in quotes such as ['600', '700'] is no longer called "not text"; a size given as a number without a unit is named, with an example that passes, and a {light, dark} object is named instead of a raw error. experimental theme template in a folder the theme editor made guards only the editor's own files: an earlier template there is replaced with --overwrite, and for an editor file the skip names a free path instead of --overwrite. undo refuses an --only the setting was not made with, matches a value whatever its comma spacing (rgb(255,0,0)), and undo <theme> mode/base says when the history does not reach back to how the theme was made. A build that fails puts the files back and says nothing was changed, and show no longer says it built a theme its source cannot carry. (#11419)
  • astryx experimental theme editor: a bare number on a length (padding 4) suggests 4px with every flag kept, never the property's reset value. A part named by its class (.astryx-card) or its component (<Card>) suggests the part. What the buttons and surfaces dials write is read from the build, so an exact property under them is named in set and show, and undoing it names the dial that applies. An unknown state suggests the one meant (pressed is active), or how to see the part's states. After a change and its undo, the sheet no longer says it is out of date. (#11419)
  • astryx experimental theme editor show: a light/dark pair with a missing half is named even when the other half holds commas (rgb(0, 0, 0)). A helper the theme source reaches with require() or import x = require() counts as part of the source. A stylesheet or module that another theme's build wrote (compile other.theme.ts --out themes/g/g.css) is built again from the editor's settings. (#11419) A number given to a part property gets px on each bare number (4 8px, 8 / 4, 4 px), within the property's range, and never falls back to its reset value. --on checkboxes names the checks group as how does. corners sharper and spacing roomier step from the value now. A state in another spelling (focusVisible, focus_visible) is that state.
    When themes in the app is a file (or a link to one), every editor command refuses, saying to rename or move it, instead of failing with a raw error.
  • astryx experimental theme: template overwrite on any disk, and undo answers that are true. (#11419)
    • experimental theme template … --overwrite never replaces a theme editor file under another spelling of its name (themes/t/T.theme.ts on a case-insensitive disk, or through a link).
    • undo <theme> mode or base on a theme with no saved change says so, instead of claiming its history does not reach back; after every step is undone it says the value was never changed.
    • undo <theme> headings <word> with only the other half set names the half that is set.
    • A mistyped base suggests only a base this project has installed, and says when the name is a theme made here (which cannot be a base).
    • undo <thing> <value> matches the saved value in either quote style and with any spacing around /.
  • astryx experimental theme editor: a mistyped --like or base suggests only a base the app has installed, and with none near, base none and the installed bases. undo <theme> base or mode after a change and its reverse says it is back at the value the theme was made with. new refuses an option it does not take with its help, like the other editor commands. A theme folder copied or renamed by hand names the files to rename. A padding (or other) shorthand set after its sides on a part removes them, as its note says, and undo brings them back. A hand-edited part property value its CSS grammar refuses is named, like a dial's. show builds again when an output is missing or was edited by hand, as compile --check finds them. (#11419) When your own <theme>.theme.ts does not parse, set, undo and show refuse before writing or removing anything (the palette files under tokens/ stay), with cat of the file; a failed change that removed the tokens/ folder puts it back. A build temp file left by a command stopped mid-build is swept after ten minutes.
  • astryx experimental theme editor show renders its preview pages again only when what they show changed (the CLI, Core, the page or the theme's build): a show with nothing new takes about a second. A built output that cannot be read, or a folder in its place, is refused by name with a command to inspect it, in show and compile alike. Every file the editor's build writes counts when show checks the build, the generated color references too, and a hand edit inside the generated settings module is built over from the settings (and compile refuses it). A check of the outputs that cannot run is no longer read as a match. A theme busy with another command suggests this same command again, once the other ends. (#11419)
  • astryx experimental theme editor: a theme file that is a folder or cannot be read (its settings, source, stylesheet, module or undo history) is named with what is wrong and ls -la <file>, instead of a crash or "damaged"/"not valid JSON"; no message suggests deleting a file (a damaged history is moved out of the theme folder instead). ./t and .\t name the theme t. A mode or base written in other letters (Dark-Only, Neutral) is offered back fixed, and a base is suggested only when it is installed. A missing argument names what the command takes and what it was given (set corners small reads corners as the theme), with its usage and --help. (#11419)
  • astryx experimental theme editor: a settings file whose lifted field is not a list of text is named, with the undo that puts it back, instead of a crash. Setting a whole-theme dial notes each token your own <theme>.theme.ts sets itself, which wins over the dial, so a change that does not show is explained. (#11419)
  • astryx experimental theme editor show renders its pages again when the Core or base theme package it runs from changes, even at the same version (a linked or patched copy), and when a page was edited by hand: the page records a hash of itself beside its render key. A folder in place of an output the build writes for some themes only (the variants types) is refused by name, like the other outputs. (#11419)
  • astryx experimental theme editor: a built type file (<theme>.d.ts, .css.d.ts, .variants.d.ts) replaced by a folder is named with ls -la <file>, never with an --out the editor does not have. A theme name one letter off an existing theme suggests the same command with that theme's name first (set brnad corners small → set brand corners small), and new with the typed name only after. An empty theme name ('', -, an unset variable) says the name is empty and names the themes here instead of new my-theme. (#11419)
  • astryx experimental theme editor: a token your own <theme>.theme.ts sets only in a scope (onDark, components) no longer counts as page-wide, so it never masks a dial or closes a token loop; only its top-level tokens do. A preview page with text added after its render stamp is rendered again. The editor show docs list ERR_FILE_EXISTS and ERR_WRITE_FAILED, say ERR_UNKNOWN_THEME also covers a base theme package that is not installed, and the exit-code row names every refusal. (#11419)
  • astryx experimental theme editor: a render that fails in show (two copies of React, a component that throws) is refused with doctor and "Nothing was written" wherever it happens; outputs that show made again are put back first. Two copies of React are now named as the cause (Core's own React is found from its entry). In a workspace whose root does not use @astryxdesign/core (Core hoisted to the root), the root and folders without a package.json of their own are refused, naming the workspace's apps that use Core with the cd to run from, so no theme lands outside an app. undo <theme> radius-element and undo <theme> padding suggest the token (--radius-element) or the property with its --on <part>, never a step back that undoes another change. (#11419)
  • astryx experimental theme editor: a word that names a JavaScript object built-in (constructor, __proto__, toString and the like), given as a value, a scope, a state, a flag or a how question, gets the same refusal as any other unknown word instead of an ERR_UNKNOWN crash. Every word table the editor reads with typed text now answers only for its own entries. (#11419)
  • astryx experimental theme editor finds the app by one rule: the nearest folder at or above the working folder whose package.json lists @astryxdesign/core (in dependencies, devDependencies or peerDependencies). A workspace member that does not use Core, a subfolder of an app that does not list it, a workspace root with deep globs or any pnpm-workspace.yaml form are refused with where Core resolves from and the workspace's apps that list it, each with the cd to run from; nothing is written into the wrong folder. A nested repository inside an app no longer hides the app above it. (#11440)
  • astryx experimental theme editor: the home folder is the app when its own package.json lists Core; a folder inside node_modules is never the app; a dependency field that is not an object reads as no Core instead of failing; install suggestions use the app's package manager; a Yarn Plug'n'Play app gets its own refusal from any of its folders; the workspace refusal names apps up to six folders deep and writes a folder starting with - as ./-name; a package.json that does not parse is named with the parser's error and its place. (#11440)
  • astryx experimental theme editor: a token set on one part (--on) that reads a whole-theme token is checked for a loop only within the scope it is set in. The part reads its own settings first and the whole theme's after, and a whole-theme value never reads a part's, so --color-accent var(--color-text-primary) with --color-text-primary var(--color-accent) --on top-nav-heading is accepted in either order, and the saved settings no longer leave show and every set refusing; a loop within one part or within the whole theme is still refused. An exact accent (or other fill color) given as var() of another token, a two-color light-dark() or a color function of tokens is read as the color it shows in each mode, so the text on it is picked to read on that color and the notes name it (var(--color-warning) = #ffce2f); a value that still cannot be read as one color is named as unchecked instead of the generated shade. (#11419)
  • astryx experimental theme editor: a theme's own <theme>.theme.ts deleted by hand is written again by show or the next set, which say so, and compile of it suggests editor show. text-size and type name an exact role size they keep (--text-body-size, heading sizes), and a role or whole-theme font names an exact --font-family-<role> it keeps, with the undo that frees it; undoing a role font names that token as what applies. A value pasted with !important says it is not used and suggests the value without it, and the font dial reads a pasted Georgia, serif; or a comment as the font meant. (#11440)
  • astryx experimental theme editor reads the tokens your own <theme>.theme.ts sets from what the build made of it, so any way of writing the file counts (a namespace import, a renamed defineTheme, a template, a spread of a shared object); before its first build the file is read as written, and a change the next build shows to make tokens read each other is refused with the files put back. The base theme's own values are never counted as yours, and they close a token loop and make a part read a token as the base theme's rules do. An accent your theme file sets is the color the palette picks text for, and an exact token your theme file also sets says the file's value shows. (#11440)
  • astryx experimental theme editor: an exact token hand-edited in the settings file to a var() that names no design token (and has no fallback) is named by show and every later command, with the undo that removes it, as set refuses it; it is never built. The font dial reads any run of spaces or tabs inside a family name as one space, so font 'Open Sans' names Open Sans. (#11440)
  • astryx experimental theme editor: a Yarn Plug'n'Play workspace (its .pnp.cjs at the workspace root) gets the Plug'n'Play refusal from a member app or its subfolders; a repository inside an app in the home folder is refused naming that app and its cd, never an install into the repository; a suggested new my-<name> is a free, valid name, and names the user's own my-<name> when there is one; a base typed as its package name (@astryxdesign/theme-butter, theme-butter) or in other letters stays that base in the suggestion, after its install line when it is not installed. (#11440)
  • astryx experimental theme editor: the font, text-size and type dials no longer say your theme file sets the tokens they write; a palette token your theme file sets gets no shade note, and your theme file comes first in every note (before an exact setting, before a dial) and after an undo. A token loop inside one part is refused when it closes through the base theme's or your theme file's rule for that part, a setting on a part that your theme file also sets on it says the file's value shows, and undo counts only the steps it can still go back to. (#11440)
  • astryx experimental theme editor set: a font family list missing a comma ("Open Sans" serif) is refused with the comma put back ("Open Sans", serif), read with css-tree; a suggestion never folds the list into one family holding an escaped quote. A font pasted with its property name (font-family: Georgia, serif;, or a font: shorthand) is read as the family list it names, for the font dial and exact font tokens. A var() with a fallback is never refused as reading nothing; when its name is a slip from a design token, a note says the fallback always shows. (#11440)
  • astryx experimental theme editor: your theme file comes first in more places. A token loop inside a part's state or variant rule is refused when it closes through the part's plain rule (the base theme's or your file's); a part dial, a group or a variant setting that your file sets on a part says so; undoing a part setting your file also sets names the file's value; show names every exact setting your file sets itself; and a note that says to take a token out of your file names the exact setting that then shows. After compile of an edited theme file, show reads the build as current when compile --check would, instead of building it again. (#11453)
  • astryx experimental theme editor: undo <theme> headings Tracking (or TRACKING, Tight) removes the tracking half, never the weight half; a change removes only the pictures the editor took (and only while they are as it wrote them), never a file of the user's, and marks the section sheets show --section made as out of date (in sheetStale) instead of deleting them; a link in the theme folder whose target is gone is named with where it points, by set and by undo alike, instead of a copy step that fails or "Nothing to undo". (#11453)
  • astryx experimental theme editor set: a font file or link (./fonts/My.woff2, Inter.woff2, a font service URL, url(…)) and a name holding a colon are refused as font family names, for the font dial and exact font tokens, with how to load a file (@font-face or a font package) and never a suggestion that quotes them. A value pasted with its property name (color: #e11d48;, font-weight: 700, font-size: 18px) is offered as the value given, a var() with a fallback as its fallback, and light-dark() on a color dial as its light color with a note; font-family: ; with no value is refused as no value. A size suggestion is the token's own default instead of 6px, and a token typed with its colon (--color-accent:) is offered without it first. (#11453)
  • astryx experimental theme editor: its phone rule repeats only your exact font settings, and the notes say what phones show (on top of a base theme, phones show the base theme's type for fonts your file sets as plain tokens; the note says to set them on the theme's typography, or in a rule for the same screens). A [light, dark] pair your theme file gives a token that is not a color (a font, a size, a weight) is refused by name, as --mode is on those tokens, and a font your file sets through typography is seen as the file's. (#11453)
  • astryx experimental theme editor: --png writes a picture only over one the editor took (unchanged since); a file of the user's by that name is named and left as it is, and no picture is taken. The record of the editor's pictures is a file of the theme (<theme>.pictures.json), so it moves and is copied with the theme. A new refused for its name never suggests a dial value the dial refuses: the value is left out and the refusal says so. A section sheet's out-of-date notice names show <theme> --section <section>, the command that makes it again. A theme folder renamed by hand is refused with every step it takes to edit it under the new name: the file renames and the names inside <theme>.theme.ts. (#11453)
  • astryx experimental theme editor set: in a font family name, every Unicode space (a no-break space, a thin space) is one space and zero-width characters are dropped, so Open<no-break space>Sans names Open Sans. A dial's value pasted with its property name (border-radius: pill, font-size: 18px; for text-size, color: #e11d48 for accent) is read as the value, one path for every dial. A declaration pasted as one argument (set b '--color-accent: #e11d48' or --color-accent:#e11d48) sets that token to that value; set's usage now shows the value as [value...], and a set with no value gives the same missing-value error as before. (#11453)
  • astryx experimental theme editor: a [light, dark] pair on a token that is not a color (a shadow too) is refused however your theme file writes it (a constant, as const, satisfies, a spread from an imported module), by set, show and undo and by experimental theme compile and --check. A state rule your theme file sets on a part (:hover) is named like a variant: in set, show (with no contrast caveat for a setting that does not show) and undo. compile of a theme whose saved settings hold a value the editor refuses names the undo that removes it, and the phone note says to set fonts on the theme's typography, or in a rule for the same screens, to keep them on phones. (#11468)
  • astryx experimental theme editor: one entry normalizer reads every setting before any check, typed or saved. Every Unicode space (no-break, thin) is a plain space and zero-width characters go, for every value type; a saved value holding one is named with the clean value to set. A declaration typed whole or split (accent: #e11d48, --color-accent=#e11d48, font:inter, accent: then the value) is the setting and its value, for dials and tokens; a token typed with an em or en dash or as var(--x) is that token, and one typed without its dashes is offered with them. A refused value's suggestion comes from that setting's own check: text-size 14pt suggests the size in pixels, type large or type 18px suggests text-size (never corners), mode lists its modes, and a saved size token suggests its own value with a unit. (#11468)
  • astryx experimental theme editor: an empty theme folder (or one holding only system files such as .DS_Store) is no theme yet: set, show and undo say so and suggest new <theme>, which makes it there, instead of calling it a theme the editor did not make. (#11468)
  • astryx experimental theme editor: new and show end with wiring, the steps that put the theme into this app: astryx theme add <theme> for its app copy (a one-mode theme's mode for the <Theme> too), and what builds it; only when a folder of yours holds the copy's place does it give the root file's imports and the <Theme> by hand. The editor's help says the same. A token set on a group names the members that read it and take the change, and what the others read instead; a part that never reads it is still refused. (#11468)
  • astryx experimental theme editor: every build of a theme (new, set, undo, show, and experimental theme compile of its source) also writes its app copy, src/themes/<theme>/: a standard local theme (descriptor, a source that re-exports the built module, the built module, its stylesheet and font stylesheet), marked as written by the editor and never edited by hand. astryx theme add <theme> then puts the theme into the app, and theme use, remove and list take it as any local theme; new and show say so in wiring. The first time the copy is written (by new, or by the first build of a theme made before), the result names its files (appCopy in JSON); later builds write it quietly. A folder there that is not the editor's own copy is never written, and the wiring gives the imports by hand instead. (#11468)
  • astryx experimental theme editor: a part setting saved for one mode no longer locks a theme switched to one mode (it stays saved, is named as not applying, and applies again with both modes); a part's length (padding, a corner radius, a gap) that reads a design token of another kind (a color, a font, a duration) is refused like the token form, naming a length token that works; and a var() whose name is not a CSS variable (var(color-x), var(-x), var()) is refused for every value, with the repaired form. (#11468)
  • astryx experimental theme editor: a saved setting written in a form the editor cleans up when typed (Corners, var(--radius-element), an em dash, backgroundColor, state Hover) is removed by the undo its refusal suggests, and only that setting: a valid setting the cleaned name also matches (corners = pill, the real hover rule) stays. A saved value's cleaned form is offered as a set line only when set takes it. Curly quotes in any value are the straight ones CSS reads (a font family in curly quotes is no longer saved with the marks in its name), a quoted CSS string keeps its no-break spaces, and any run of dash-like characters at the start of a token name (em or en dash, non-breaking hyphen, minus sign, full-width hyphen) is its two dashes. (#11468)
  • astryx experimental theme: list, add, use, remove and eject given an editor theme with no app copy yet name the same steps editor new and show give in wiring (build it once, then theme add <theme>, and a one-mode theme's mode for the <Theme>). A color change stopped before its settings were saved no longer leaves its color config and tokens/ behind: the editor records the config before it writes it, and the next build removes it when the saved settings set no color; a config of your own is never removed. (#11468)
  • astryx experimental theme editor how: a focus ring request keeps its scope ("focus ring on inputs only" sets the ring's tokens --on inputs, the other parts keep theirs), and an exact amount ("half", "double", "twice", "50% strength", "x0.5") is worked out from the theme's own value: the ring's width, a part's corner radius or its padding when the theme sets one. An amount alone after a comma ("…, at half strength") belongs to the ask before it. A comparison ("cards with twice the padding of buttons") is of the other part's value, when the theme sets one; otherwise the answer is a step and says so. The answer names the value it starts from and, for "strength", that it reads it as the ring's width. (#11490)
  • astryx experimental theme editor how: "header(s)" or "title(s)" with a text word (bolder, bigger, font, weight, size, serif) means the headings' type, and with a surface word (background, bar, border, sticky, height) the app header part; a part that owns its header ("table header") keeps it. "just" and "only" keep the scope they name ("just the headers bolder" changes the headings, never the body text). (#11490)
  • astryx experimental theme editor: a dark-only or light-only theme keeps both halves of its colors, and its mode is the one the app's <Theme> is given. (#11468)
    • The theme's colors keep their light and dark values, so a toast, a lightbox or an overlay Core draws in the other mode stays readable; the generated settings module carries only names Core's types take, so the app type-checks.
    • set <theme> mode dark-only (or light-only) says to give the app's <Theme> mode="dark" (or "light"), and the wiring after theme add says where it goes; the preview passes it already.
    • Settings for the other mode stay out of a one-mode theme and are named, as before.
  • astryx experimental theme editor new ends with how to look at the theme after each change: editor show <name> --png writes themes/<name>/preview.png and sheet.png from real components and changes nothing in the app; open the pictures and check them against what was asked. (#11500)
  • astryx experimental theme editor reads the page-wide tokens of your own <theme>.theme.ts however they are written (inline, a const, a spread, as const or satisfies), from the defineTheme the build loads, never a sibling theme in the same file; a value it cannot read in the file comes from the build. The experimental theme template --overwrite and compile --out help match what they do. (#11419)
  • astryx experimental theme editor: shorthands by what they set, and part values Core can carry. (#11419)
    • A shorthand set after its longhands replaces only the longhands it really sets, read from MDN's data (overflow keeps overflow-wrap, transform keeps transform-origin, flex keeps flex-direction), and a part's background keeps reaching its variants when background-blend-mode comes later.
    • A group's shorthand replaces its members' longhands as a part's does, so the later setting wins either way.
    • On a part whose padding Core writes one variable per side (card), a variant's padding after a side set for every variant is refused, with the commands that work: it would not show.
    • --on cards, dialogs, tabs and other plurals name the part, with the set command.
    • Word hints keep the value given: shadow none is box-shadow none, rounded 8px is corners 8px, bold false is font-weight normal.
  • astryx experimental theme editor: card padding and radius written exactly. (#11419)
    • On a part whose padding Core writes one variable per side (card and the other containers), the editor writes each side itself, split as CSS splits a shorthand: calc(4px + 2px) 8px, clamp(12px, 2vw, 24px) and four different sides reach the part as typed.
    • A variant's padding after a side set for every variant now shows: the editor writes the variant's side variables too, instead of refusing it.
    • A card radius of more than one value (12px 12px 0 0, 10px / 20px) gives each corner its own radius; the content that reaches the card's edges takes one radius, the first corner's, and the result says so.
  • astryx experimental theme editor: variant values win over lifted base values, and card padding keywords written exactly. (#11419)
    • A part's base value lifted onto a variant (so Core's own variant rule does not hide it) now goes before the variant's own declarations, so a longhand or shorthand set for the variant wins (border-color for the destructive button after a base border).
  • astryx experimental theme editor: padding sides and inner radii that win as written. (#11419)
    • A later part padding replaces a side its group set.
    • A part's own multi-value radius keeps the content's radius it gives over a single radius from a group, a dial or the base theme's lifted onto a variant.
  • astryx experimental theme editor: the chat composer's box is reached as it is drawn. (#11419)
    • padding on chat-composer goes to the padding of the visible composer box, with no gap outside it. Background, border, shadow, a side padding or a padding for one density, which would land on the composer's transparent wrapper, are refused with the reason.
  • astryx experimental theme editor: one padding model for parts whose box reads Core's padding variables. (#11440)
    • On card, clickable-card, selectable-card, dialog, drawer, bottom-sheet, section and number-input, each part's padding is worked out per variant and per state from every padding setting in the order made, side by side for each text direction (a physical left is the start in a left-to-right box and the end in a right-to-left one; so is the padding shorthand's left), and written to the variables the box reads. The later setting wins in both directions, a variant or a state out-ranks the base, and the content that reaches the box's edges stays in line.
    • A clickable or selectable card is padded as a card.
    • A part's base rules come before its variants', and its rules for a direction before its states', whatever order the settings were made in.
    • padding on chat-composer takes one length, as Core reads it inside calc(): a length, a variable such as var(--spacing-3) (Core's own default), or calc(), min(), max() or clamp() giving one. Several values, a bare number or a percentage is refused with one that works.
  • astryx experimental theme editor: padding that stays where it is set, and one length wherever Core reads it inside calc(). (#11453)
    • Padding set on a clickable or selectable card, or on a card's variant or state, no longer reaches plain cards nested inside it: each side the narrower rule writes is reset on a plain card inside it, so Core's own fallback holds, and the narrower rule writes each side rather than the whole padding.
    • Every part whose padding Core reads inside calc() (found from Core's own stylesheet: chat-composer, dropdown-menu, context-menu, segmented-control, and an item's inline padding) takes one length there, as chat-composer does, also through a group (--on menus).
    • A padding with --state on a card, dialog or a group of containers is now taken: the padding model writes the state's own sides.
  • astryx experimental theme editor: nested sections that follow their parent, and lengths Core can calculate with. (#11453)
    • A section padding the same on every side is written as the section's whole padding, which Core reads after the padding a parent section passes down, so nested sections keep following their parent.
    • A padding of 0 is written as 0px on parts where Core calculates with it (card, section, dialog, drawer, bottom-sheet); initial and unset leave the padding to Core's own default.
    • A hand edit to the settings file that set would refuse is reported by the next set with the command that removes it, as compile does, instead of being built.
  • astryx experimental theme editor: a part's padding replaces the base theme's, and every padding writes a length Core can calculate with. (#11453)
    • A padding on a card, section, dialog, drawer, bottom-sheet or number-input replaces the base theme's padding there, whichever sides the base theme set: the editor writes it as padding properties Core works out together with the base theme's, where the later one wins.
    • A clickable or selectable card's padding wins over a card's left or right padding in each text direction.
    • A plain part nested in a narrower one is reset only on the sides its own rule leaves unset, so a padding in your own theme source on that part still applies.
    • A zero written any way (0e0, 0.0) is written as 0px; initial and unset name the part's own default padding from Core.
    • A hand-edited padding on one part is reported when a set changes padding on another part too.
  • astryx experimental theme editor: what the editor builds, compile --check takes. (#11468)
    • Two to four corner radii on card, button, dialog, avatar, banner, popover and the other parts with an inner-corner radius are written as CSS properties Core reads (the whole radius, which Core turns into the content's radius, then each corner), never as a private variable, so compile and compile --check pass.
    • A padding on chat-composer is refused with the reason: the box inside its transparent wrapper reads its padding only from a variable of Core's own, which a theme cannot set, and a padding on the wrapper would add a gap outside the box.
  • astryx experimental theme editor: a padding in your own theme source wins over the editor's on the same part, whatever sides each names. (#11490)
    • A padding your <theme>.theme.ts sets on a part's plain rule, a variant or a state wins over an editor padding there (padding 20px --on card under your own card padding of 6px shows 6px), and the result says so, also right after an edit to that file, before any build.
    • An editor padding on a part's plain rule that differs by text direction keeps the plain rule's weight, so any variant, your own included, out-ranks it.
    • padding inherit (and revert) on parts whose padding Core keeps in its own variables is taken like initial and unset, and the result names the default it means.
  • astryx experimental theme editor: the spacing dial keeps the small, medium and large control sizes apart and in order at every step. (#11490)
    • A denser spacing still makes controls shorter by the plain scale, but no size meets the one below it: one that would keeps its own step, scaled, above it, and none goes under 24px (spacing tight on Neutral gives 24px, 27px and 30px, where small and medium both ended at 24px). The dial's help says control heights follow it.
  • astryx experimental theme editor: every picture --png takes carries the editor's stamp (a PNG text chunk naming the theme), so it is known as the editor's even without its record; a picture an earlier version took, with no record yet, is taken over when it is the editor's 1280-pixel window, and the result says so once. Only links among the files the editor reads or writes are refused, each named with where it points; a link to a file of yours (notes, a mockup) is left alone. A new refused for its name leaves out of its suggestion a vibrancy that would change nothing (no color given), and says so. The --png help of new, set, show and undo names the picture record and when no picture is taken. (#11453)
  • astryx experimental theme preview: the route and pages it writes type-check with noUncheckedIndexedAccess, noImplicitOverride and noUnusedLocals. add --path refuses a folder name that is no plain URL segment (a space, an accent, #, %), suggesting a slugged one. Folder names Windows does not allow are refused in full: reserved characters, a trailing dot or space, and COM¹-style device names. The free folder a URL conflict suggests is one whose URL no other page serves. preview app leaves out a temp file a stopped command left in the theme folder. (#11419)
  • astryx experimental theme preview: in the preview's nav, only a plain left click switches the page in place; a Ctrl/Cmd, Shift, Alt or middle click opens the page's URL as a link does. The see line after an editor change now leads with a look that changes nothing in the app (the editor's own preview.html, current after every change it renders, and --png), then the in-app preview page when there is one; adding the preview to the app comes last, as an option. (#11490)
  • astryx experimental theme preview add: a folder name that Next serves at a plain URL (letters, digits and . _ ~ ! $ & ' ( ) + , ; = @ -) is accepted. For any other name, every odd segment is slugged and the suggested folder is a free one. A folder that differs from another only in case is refused, since macOS and Windows treat them as one. In an app with no TypeScript, the result names the install line. When the app's tsconfig turns on noUncheckedIndexedAccess, the result names the template pages written as their template ships. The Colors page shows a seed color as it is stored. (#11419)
  • astryx experimental theme: going back to the preview's bare URL shows its first page, as a reload does. editor undo points its see line at the page about what it reverted. A preview whose URL depends on the app's routing, or whose folder was renamed by hand, is named where it is, by see and by preview list, instead of suggesting a new one. preview add --theme takes a pasted label (theme: t, name: t) as the theme t; an editor command given one refuses it and suggests show t. A change the editor could not render says why in its see line instead of pointing at a preview.html it did not write. (#11490)
  • astryx experimental theme preview: a default page's id beside another page asked for is refused ("drop one of them") instead of dropping the other. preview add colors on a theme with no generated colors says how to get them. preview list marks a page whose file is gone and notes a change that was stopped part way, and add writes a missing page back as added. Running a stopped preview remove again finishes it and exits 0. basePath is certain only when set as a literal on the exported config at the top of next.config; one set in an if or a function, deleted, or added by a wrapper is named as set from code. (#11378)
  • astryx experimental theme preview: the preview route renders its pages only in the browser, so a component that crashes a server render no longer stops next build when Components is the first page. next.config is read the way Next loads it: .js before .mjs, .mts, export {config as default}, a key set after the object, and the last of a repeated key; a config changed in other ways gets a note instead of a guess. Table pieces (TableHeader, TableBody, TableFooter) are no longer shown alone on the Components page. preview add overview (or another default page's id) brings back the default pages that are missing. (#11378)
  • astryx experimental theme preview app --theme <t>: the new app installs the Core and base theme versions this project has, the ones the copied build was made on, so the theme is current after install; a note names them and how to move to this CLI's release. (#11468)
  • astryx experimental theme preview: add rebuilds the theme whenever its build is not current (an output missing, or a build that does not match the settings), the same rule preview app uses, so the route never imports a missing file. A pasted --theme 'theme: t' names the theme t. A distDir with a subfolder blocks only that folder. remove --path on a folder with no preview names the preview there is, with its remove. The preview app help says that with --theme Core and the base theme are pinned to the project's versions. (#11468)
  • astryx experimental theme: every in-app preview page has its own URL (/theme-preview?page=components), which the nav links to, so a link, a reload, the back button or a screenshot reaches any page; preview add, list and app give each page's URL. Every editor change carries a see line: first a look that changes nothing in the app (the editor's preview.html, current after the change, and --png, which takes pictures with no dev server), then the in-app preview page most about it (Colors after a color, Components after a part, Overview otherwise) at its URL when there is a preview, and adding one last, as an option. The --png help says it needs a Playwright or a Chrome and adds a few seconds. (#11490)
  • astryx experimental theme preview: a --path that goes through a file, has a folder name longer than 255 bytes, or is longer than 3,500 bytes, is refused with a reason. A folder that differs from another only in case is refused for preview app and for a --path outside the routes folder too. preview remove leaves a page file it cannot read in place, says so and keeps it recorded. A preview flag given twice with different values is refused. (#11419)
  • astryx experimental theme preview remove: a page the app's own code imports is kept, and the importing file is named, for one page and for the whole preview. The check reads the whole project, following relative imports, @/ and tsconfig path aliases. (#11453)
  • astryx experimental theme preview: popovers shown open on the Overview and Components pages no longer take focus, so the page stays where it opened. The Overview points to the Colors page only when the preview has one, and a color set on a theme whose preview has no Colors page says which preview add adds it. preview remove takes away the empty folders the preview's first add made, never one that was there before. The Overview reads its font line again when the theme changes while the page is open. The preview app starter lists @types/node, so its first npm run dev installs nothing. (#11440)
  • astryx experimental theme preview add: an app frame's exact name as the description (blank, shell-top-nav) is refused with a clear reason and the --template command. An exact template name is called the page named, not the closest page. With no routes folder, the refusal names the Next apps below with a --path into each, and a --path that would make a routes folder with no root layout is refused before writing. Page packages are read from the app the preview is in. The Core stylesheet check starts from the root layout over the preview, route groups included, and follows tsconfig path aliases. (#11440)
  • astryx experimental theme preview add: a short description that names a page template (checkout, hero, a landing page) takes the page build ranks first, instead of being refused. A description that is exactly a template's id or display name adds that page, or says why it was skipped. The Core stylesheet note follows the root layout's imports, so a stylesheet imported from a root styles/ file counts. A theme font whose package the app lacks gets a note with the install line, and the Overview marks a font that is not installed. (#11440)
  • astryx experimental theme preview remove: the check that keeps a page your code imports now reads the whole project (every source file outside installs, build output and dot folders), parses each file's imports, exports, import() and require() calls, template-string ones included, and also guards the route a file re-exports. A project too big to check is refused rather than half-checked. A route changed by hand is told to move out of the preview folder. preview add --template overview|components|colors adds just that page when it is missing, or says why not. Temp files a stopped preview command left are cleaned by the next one and by a full remove. (#11453)
  • astryx experimental theme preview: when both spellings of a folder are already there, the case-clash refusal suggests a new folder beside them, and names preview remove for a preview already inside. A theme-preview.json entry that leads outside the folder (../) is reported as damaged by add and list. remove drops such an entry and deletes nothing outside, and its messages show paths from the project. (#11419)
  • astryx experimental theme preview: the route of a one-mode theme no longer imports the mode switch it does not draw, so apps with noUnusedLocals build. A refused --theme says exactly what leaving it out does in this app: the theme the preview keeps wearing, or the one theme under themes/ it picks. (#11453)
  • astryx experimental theme preview: no demo on the Components page takes focus as it mounts. A dialog part such as DialogHeader shows inside an open inline Dialog, and an open Popover is named. When the preview's theme is gone, its Colors page goes with it. preview remove refuses while a file of yours in the folder imports the preview pages, and its advice for a route changed by hand is to move it out of the folder. preview list with no preview says why add would refuse the folder instead of suggesting it. remove takes away the empty folders add made outside the routes folder too. Every page-template list suggestion names the command the way the app runs the CLI, in --json as in text. (#11453)
  • astryx experimental theme preview: the base theme's fonts stylesheet is imported only while the theme's build still names a family it loads, so a theme on font system or its own fonts fetches nothing it does not use. preview add names every page it writes again, the Colors page included, when the preview switches theme. (#11419)
  • astryx experimental theme preview: add --path refuses an intercepting route folder ((.)x, (..)x, (..)(..)x, (...)x), where a page breaks the whole app. The preview loads the fonts stylesheet of the theme it is built on (Figtree for neutral), and so does the preview app starter, so the Overview shows the family it names. preview list text marks a page whose file is gone as missing, matching --json. (#11419)
  • astryx experimental theme: padding sides by direction, a failed show leaves the folder as it was, and how reads "not dark enough". (#11419)
    • On dropdown-menu, context-menu and segmented-control, one logical padding side is written for each direction (the left in a left-to-right box, the right in a right-to-left one), so it changes that side only; under a state it is one rule per direction (:hover:dir(ltr)), and a later padding or physical side replaces it.
    • show whose render fails puts back every output it touched, removing one it made new and restoring the palette files in tokens/.
    • how "not dark enough" / "not light enough" asks for darker or lighter, not for one mode.
  • astryx experimental theme editor: a card's physical padding side beside others, a failed show beside your own folders, and the busy-lock suggestion from the API. (#11419)
    • A card padding-left or padding-right set beside another side, as a keyword (initial) or as math (calc()), reaches that side.
    • show whose render fails leaves a folder you put in tokens/ alone.
    • When another command holds the theme, the suggestion to run again names the call's own command with every option it got (--only, --like and each dial of new, --png), never the arguments of the process the API runs in; a preview command waiting on another names preview list.
  • astryx experimental theme editor: every set a refusal suggests is now checked the way set checks it, without writing anything, and a suggestion set would refuse is left out. Suggestions carry what was asked instead of a fixed example. headings light --on heading offers headings light and weight 300 on one level. text-size large --on card offers that size on the card. A number token reads the number meant (700px is 700, 1,5 is 1.5, calc(1rem+2px) gets its spaces). A word dial given a number offers its own words, or the nearest type preset for a scale ratio. An invalid color is never copied into the text color token. A color property refuses a var() fallback inside color-mix() that is not a color. how "more washed out colors" lowers vibrancy. (#11419)
  • Icon sets: a project picks one look for every icon. astryx experimental icon use <main> --variant <variant> writes experimental.iconVariant beside experimental.iconSet, in one write, and refuses a variant the main set does not declare; without --variant it removes the key. Each set in the list draws its variant of that name, or its default look when it declares none, and the receipt (icon.use) adds variant, previousVariant, looks, and themeMap. A copied template imports each icon in that look where its set has it, reports the look as icons.variant, and moves an icon a template imports from the main set's own library, or from a listed set in another look (by: 'variant'), to that look. A set's generated module also writes a theme map for each other look an icon draws (themeIconsFilled), and integration check holds it to map. astryx doctor fails when the main set does not declare the variant, and experimental icon --list shows the variant and each set's look. A CLI before 0.7.16 refuses an astryx.config that sets experimental.iconVariant, so use warns when the project's CLI range admits one. An icon-set package whose generated module an earlier CLI wrote, and whose icons draw a look other than the default, fails integration check until it runs experimental icon add --variant <variant> --from <module> --all again; the finding names that run. Projects that do not set experimental.iconSet see no change. (#11499)
  • astryx experimental theme editor counts a base theme as installed only when the project installs it, in its node_modules folders or through Yarn Plug'n'Play, as the app's bundler sees it. A theme found only through NODE_PATH or Node's global folders is no longer taken as installed: new and set base offer to install it instead of writing a theme the app could not build. (#11444)
New Features
  • astryx doctor warns when the @astryxdesign/core peer range of a loaded integration, other than the packages of added themes, which theme-core-peers already checks, excludes the installed Core (integration-core-range). A package made for another Core installs with only a package manager warning, and its components, themes and docs may not work; the warning names the package, its version and range, and the installed Core, and the fix names the release to look for. A project whose other integrations all declare a range that includes its Core gets a passing row naming them; a project where none of them declares one sees no new row. It is a warning, so no project that passed before fails. (#10350)
  • Doc examples take an optional kind: 'demo' | 'setup' (default 'demo'), on component, sub-component and function examples. A setup example is code that cannot run on its own, such as an app setup file, a server route, or a snippet that uses variables defined elsewhere: astryx component <Name> labels it "(setup, code only)", and a docs site shows it as code with no live preview. In astryx component <Name> --json, every example carries its kind. Any other value fails to load with a message that names both kinds. astryx docs authoring explains when to use setup. (#11434)
  • Add Table infinite loading with useTableInfiniteScroll({hasMore, isLoading, onLoadMore}). One Promise request latch coordinates automatic and manual loading, failures pause automatic retry, and the persistent busy Button owns progress announcements and focus continuity. (#10570)
Fixes
  • In the AI Chat page template, the chevron on the artifact card now points toward the end of the line in right-to-left layouts, as it does in left-to-right. (#11477)
  • In the AI Chat page template, the message list's scrollbar no longer sits under the artifact panel's resize handle. On desktop the chat column keeps a small gap before the handle, so the whole scrollbar scrolls the messages; before, a press on the half of the scrollbar nearest the handle resized the panel. Mobile, where the handle is hidden, is unchanged. (#11473)
  • astryx build starts more whole-page ideas from a page template instead of the empty app shell. When build would start an idea on an app shell and search matched no template directly, a fixed decision over the scores build already computes (plus a fixed word table) gives a whole-page probability; at 0.30 or more, the start is build's best-ranked page template. Ideas with an edit phrase keep the shell, and block suggestions do not change. The decision picks only templates build's word tables list, so an integration's own template is never the lifted start; its other results are unchanged. (#11519)
  • Running any command from a folder that no longer exists now gives a plain error with a cd to the nearest existing folder (text and --json, code ERR_PROJECT_REQUIRED) instead of a stack trace; --help, --version and docs still answer. (#11440)
  • astryx doctor's theme stylesheet check no longer fails on a theme's own files when the theme it extends is added too (theme add d and theme add neutral): a theme source, its build and the editor's generated files only extend the other theme, so they are not asked to import its stylesheet. An app file that imports an added theme's module without its stylesheet still fails the check. (#11506)
  • A refusal longer than a pipe holds (64 KiB) reaches a slow reader whole, such as bash $(…) or a reader that takes its time: the --json envelope stays valid JSON with its code, and the text refusal keeps its last line. The CLI writes its final error output out before it exits. This is a small change to the shared error output, made for the theme editor's long refusals. (#11419)
  • No public API function takes an undocumented __-prefixed option. themeBuild() reads only its documented out, check, and iconsSpecifier options; what theme build hands a batch, family, or package-check build now travels through the CLI's own internal path, so theme build and integration pack-check behave and print exactly as before. A test fails if a hidden option comes back on any exported function. (#11446)
  • Kept catalogs and check results no longer depend on the value of every environment variable when code only lists the variables' names (as a TypeScript transform does). Tools that set a new value per call, such as AI agent harnesses, missed every kept answer on every call; they now hit like any other run. A variable whose value is read still decides the kept answer, including one read inside a kept gather that another one wraps. (#11427)
  • astryx doctor integration validate and astryx integration check name unreachable contribution metadata with forward slashes on every platform. On Windows the path in "Found contribution metadata ... outside every declared integration root" used backslashes, while the fix in the same message used forward slashes. (#11084)
  • A kept entry in the per-user cache whose value is missing or has the wrong shape for what it holds is now worked out again and stored over, instead of being used: a damaged entry could make search, doctor or template --list fail until the folder was cleared. (#11474)
  • astryx theme palette generate and generateTonalPalette() honor darkChromaTaper, so every official theme palette regenerates from its saved config exactly as committed. Neutral's config asks for a muted dark edge on its chromatic families, but the generator dropped the field: 99 of Neutral's 420 colors came out more saturated than the committed ones (blue.dark[25] was [#003978](https://github.com/meta/astryx/pull/003978), not [#253](https://github.com/meta/astryx/pull/253)c5a). A dark stop now keeps edgeMultiplier of its in-gamut chroma through throughStop, then recovers along a smoothstep to the standard recipe at recoverAtStop; familyMultipliers sets the edge share for one family. Light ramps, neutral families, the black and white endpoints, and configs without the field generate the same colors as before. A taper with a field it does not read, a stop outside the layout, a family the request does not have, a neutral family, or a multiplier outside 0 to 1 is refused. (#11491)
  • astryx experimental render says why a page ended without an answer: the stage it reached (such as importing the page or rendering on the server), how long it ran, the memory left, and the page's last error output. A page process that loses its channel or reaches its own time limit is reported as that, never as a clean exit. (#11398)
  • theme build: the refusal for a quoted glob keeps --family and --family-key in a family run, and builds its suggestion with the same builder as the build's other refusals of a source; the experimental compile's refusals for the editor's settings file and for a subfolder keep --out (rebased onto the app root for the cd one), so the suggested check reads the output you asked about. (Minimal change to shared code: buildSuggestion gains an optional shape for a glob or a family run, and the build command passes --out to a group's preflight.) (#11461)
  • On Windows, astryx theme build prints install snippets that import the built theme with a working path. The import path joined the output folder with backslashes and kept a stray one after the dropped src/, so the snippet read import { oceanTheme } from './\themes\ocean/ocean';, which is not a valid specifier (and \t is a tab in a JS string). It now reads ./themes/ocean/ocean on every platform. (#11288)
  • From a project subfolder, theme template and theme eject print a build step that works from that folder (cd ../.. && … theme build theme.template.ts when the file is above it), and a blank template path is refused with theme template (no path) suggested, which writes at the project root; an absolute template path is told that paths are read from the current folder. theme build --out warns that it replaces another source's output only once every output may be written, reads a backslash in --out as a folder separator, and its --check "Rebuild with" line uses the project's invocation and quotes a path with a space. Building a theme the theme editor made with theme build still works, as released, and now warns (once per --watch session), naming experimental theme editor show <theme>. A theme file that is a link and fails on a relative import is named with the file it points to, with a build of that file that keeps its outputs in the working folder; no load error shows Node's require stack. (#11422)
  • A command theme build (or experimental theme compile) suggests after refusing a source (a Windows-style path, a folder, a file that is not a theme module, or a build output) keeps the --check, --out and --icons-specifier it was given, so following it still checks instead of writing outputs. This holds for a family check, a theme file that is a link, a plain-object family member and a file that changed while loading, and the suggested command is quoted for the shell it runs in (PowerShell too). (#11461)
  • The install example theme build --detail full (and experimental theme compile --detail full) prints says its paths are relative to a file in src/, and now they are, from whichever folder you run it: an output beside src/, such as themes/ocean/ocean, is imported as ../themes/ocean/ocean, not ./themes/ocean/ocean, which does not resolve from src/. The theme build --family snippet uses the same paths and says the same thing in its header. (#11471)
  • theme build and experimental theme compile refuse a theme that sets a private --_* variable: the build fails with ERR_THEME_INVALID (exit 1, a JSON error envelope) and writes nothing, a --check included. Before, it printed the errors and exited 1 but still wrote the outputs and reported [ok] and a success receipt, so a reader of the JSON saw a pass. (#11475)
  • theme template run from a folder inside a project reads its path from that folder within the project root, and with no path writes theme.template.ts at the project root, as its help says; a backslash in the path separates folders, as for theme eject; astryx init --features theme, run below the project root, writes theme.template.ts at that root too, because it uses the same template step. Outside any project (no package.json in the folder or above it) it writes in the current folder, as released CLIs did, and when it writes the file it warns once on stderr in text mode, naming how to write it at a project root (run it inside a project, or npm init -y first); --json stays silent. A stale theme build --check (and experimental theme compile --check) result carries code: "ERR_THEME_STALE" beside upToDate: false, the code it exits 1 with. A file at an --out path that the build did not write is left alone with its real reason and, when one exists, an --out path where no output of this build exists yet (a new folder when the theme's module beside it is taken); the build never suggests deleting it. The build-beside-the-source suggestion keeps --icons-specifier. --out into a folder the theme editor made, for a theme source outside that folder, writes there as released CLIs did, and warns once on stderr in text mode, naming how to keep the editor's folder to its own theme (build beside the source, or pick another --out); --json stays silent, and --watch prints it once per session, not on every rebuild. (#11389)
  • theme build --check (and experimental theme compile --check) names every output the build writes as checked, the .css.d.ts stylesheet types too. When the only missing output is a .css.d.ts stub, as in projects that keep it out of version control, the check prints one warning line in text mode naming it, and the stub alone does not fail it; --json stays silent and the result is unchanged. Every output the check failed on before still fails it, a missing .d.ts or .variants.d.ts included. theme eject into a subfolder of a folder the theme editor made (themes/g/sub, where themes/g/g.settings.json exists) writes there as released CLIs did, and warns once on stderr in text mode, naming how to keep the editor's folder to its own theme (fork into the project's local themes folder, or pick a path outside the editor's folder); --json stays silent and the receipt is unchanged. (#11410)
  • The dashboard page template typechecks in an app with noUncheckedIndexedAccess (it renders the same), so experimental theme preview add --template dashboard no longer adds a type error to a strict app. themeBuild() no longer takes internal hand-off options for theme build --watch or the private-var exit code; --watch still warns once per session about a theme editor folder. (#11420)
  • astryx theme template --overwrite no longer replaces a theme editor file reached through a link to its folder. (#11419)
  • An installed dependency that ships an Astryx integration manifest which fails to load because a package it requires (a dependencies entry or a peer not marked optional) is missing (a broken install) is now reported as that package's integration issue: component, template, theme, discover and search print the usual one-line warning, and doctor's integration contributions check names it with the load error. Exit codes are unchanged. A command that cannot load also reports why whatever options it was given (component --list used to answer "unknown option"). (#11486)
  • A dry run of astryx upgrade no longer tells you to review a .astryx-conflict file it has not written. When a copied ShadCN composition conflicts with a newer release, the dry run now says that --apply writes the file for review, and an apply still names the file it wrote. The JSON result is unchanged. (#11356)
Performance
  • In a project with integrations, docs keeps the integration check results it gathers, with the theme records they include, so a repeated docs call reads them back instead of checking every integration again. An edit to a doc topic shows on the very next call. doctor's cache row names docs among the commands that keep what they gather. (#11483)
  • Once the per-user cache folder exists, doctor keeps its three checks that read only files (the docs tree, progressive disclosure and the CLI's docs) beside search's catalogs, and reads each back while every file it read is unchanged, so a later doctor skips them (about 0.2 s, more with large integrations). An edit to any doc shows on the very next run. Its cache row names doctor among the commands that keep what they gather, and doctor --help no longer calls it read-only. (#11394)
  • In a project where no integration can load (no Astryx config, no integration manifest of its own, and no installed dependency that ships one), help and commands that don't need the project no longer load it first just to read the commands integrations declare: --help, manifest and blog answer about 65 ms sooner. Output is unchanged. (#11495)
  • In a project with integrations, each integration's discovered themes are kept beside search's catalogs and read back while every file they read is unchanged, so theme list and the other theme commands skip re-reading an integration's themes on later calls (about 0.1 s with a large integration). An edit to a theme, or to a module it imports, shows on the next run. doctor's cache row names the kept theme records. (#11469)
  • In a project with integrations, the whole integration issue list is kept beside search's catalogs (the template and component replacement checks over Core and every integration, as well as each integration's own checks) and read back while every file it read is unchanged, so component, template, theme and search skip those passes on later calls (about 0.1–0.25 s each with a large integration). (#11384)
  • In a project with integrations, template discovery's records are kept beside search's catalogs and read back while every file and folder discovery read is unchanged, so template --list, template <name> and build skip discovering templates on later calls (about 0.1 s with a large integration), and a template added, renamed or edited in an integration shows on the next call. A record that would not read back exactly (a function, a Map, a shared object, -0 and the like) is never kept. doctor's cache row names template discovery's records. (#11393)
  • Importing @astryxdesign/cli/api, as integration codemods and other integration code do, no longer loads Babel, recast, jscodeshift and postcss-selector-parser up front: each loads the first time it is used (about 0.25 s and 350 fewer modules per import). The API's exports are unchanged. (#11432)
  • component --list finds a component that has no folder of its own about 20 ms sooner: one index of Core's folders replaces a check of each folder in turn. Output is unchanged. (#11504)
  • The published CLI reads the icon definitions and built-in theme descriptors it ships from values stored at publish instead of parsing each file, so docs answers about 45 ms sooner and doctor and theme list about 10 ms sooner. An edited or unknown descriptor is parsed as before. Output is unchanged. (#11496)
  • experimental theme commands read each folder of Core's sources once while they build Core's component docs. experimental theme preview app and experimental theme preview add do the same as they write the Overview and Components pages, instead of once per component name. Every run writes and prints the same. (#11426)
Documentation
  • The CLI points agents and people to the experimental theme editor for making or changing a theme, labeled experimental each time: the agent block astryx init writes (its one theme line, which also keeps extending an imported theme before ejecting one to fork it), one added line in astryx init's next steps (its other steps stay), astryx --help, the theme docs (astryx docs theme, the author-a-theme guide, in English and Chinese) and the theme command's help and summary name astryx experimental theme editor new <name> --like neutral, then editor set / editor how, theme add <name> to wire it, and editor show <name> --png to look at each change. theme eject adds one line, experimental theme editor new <name> --like <base> (the ejected theme when it is a built-in base the editor knows and its package is installed, else neutral), and theme palette generate adds one line, experimental theme editor set <name> accent <color>. (#11500)
  • Hook docs for useOutlineFromDOM, so astryx hook useOutlineFromDOM and astryx search return it, and a useOutlineFromDOM — Article example block: an article and an Outline built from its headings through the hook, with a button that adds a section and its linked entry. (#11234)
  • MetadataList's guidance now says that assistive technology reads each label with its value, and that the title does not name the list or add a heading. Its prop docs now list className and style, and the label docs say that position: 'start' places a label at the inline start of its value, not on the left. (#11391)
  • astryx docs styling/tokens-and-setup has a Next.js with webpack section. It shows experimental.optimizePackageImports: ['@astryxdesign/core'] in next.config.mjs and recommends a component entry, such as @astryxdesign/core/Button, in Server Components. Without either, a webpack build ships every Astryx client component to a page whose Server Component imports from the package root. The theme preview starter app that astryx experimental theme preview app copies has the same setting. No API changes. (#11305)
  • A new example block shows useTableColumnsVirtualization: a 121-column Table with a pinned first column that mounts only the columns near its horizontal scroll position. (#11014)
Contributors
Thanks to everyone who contributed to this release:

0.7.15

Experimental APIs
  • astryx experimental theme: the component catalog and the all-components sheet are now built from each component's doc playground. Overlays show open, and each component shows its variants, its checked and disabled states, and a heading's levels. The editor's own copies of these demos are gone. A playground default that lists several elements now renders, so the editor now knows the tokens that radio lists, steppers, carousels and similar components read. (#11350)
  • astryx experimental theme editor: colors and fonts that stay safe and say what they do. (#11244)
    • Undo never deletes the generated color file (tokens/<theme>.palette.ts) when you edited it by hand. The file stays, and the result names it. The theme reads only the selected-shades file (tokens/<theme>.palette-refs.ts), which the editor writes from the generator on every change, so a hand edit to the palette file never shows; the result says so.
    • A focus color (--focus-outline-color) or any other color token set for one mode no longer locks the theme. Every later command checks it as the color it is.
    • A color file counts as edited only when its colors differ. Formatting, a byte order mark, semicolons or a hand edit to palette.config.json without a receipt do not count. When an edit blocks a color change, the refusal says how to keep or discard it and names the command to run next.
    • An exact main color (--color-accent and the other fills, tints and on-colors) reports what it changes around it, including the light-page check, when you set it.
    • The accent tint stays at the official shade. Secondary text on the parts that sit on it (selected items and rows, a dropzone, numbered citations) and on segmented-control labels (which sit on the neutral track) is lifted, as the official Neutral theme lifts it, to the nearest gray that reads at 4.5:1 there and under a hover: the neutral color's shades, else grays grown from the base theme's own secondary text, so every accent gets it. An exact --color-text-secondary, for the whole theme or on one of those parts, wins there, per mode. The contrast check measures those parts with the text they show, at 4.5:1.
    • On a base whose light page is dark (Gothic), the colors take the shades meant for a dark page in light mode too, so text reads on it. See-through exact colors (a hover tint, a fill) are measured as they show over the surface.
    • On a layout without shade 85, the light accent tint takes the lighter neighbor. Shades are shown rounded.
    • font inherit and the other CSS keywords are refused, because the browser would drop the whole font. Generic families (serif, system-ui) and the usual desktop fonts (Arial, Segoe UI) count as system fonts, and the fallback never repeats the family. A family name that is not a plain CSS name (3Dumb, My/Font) is quoted, and @fontsource/<font> names its preset.
  • astryx experimental theme editor: every CSS math function is read by its type, and fonts are judged against the theme build's own list. (#11350)
    • pow(), sqrt(), hypot(), log(), exp(), the trigonometric functions, mod(), rem(), abs(), sign() and round() are accepted where the type they give fits; sqrt(4px) and mod(10px, 3s) are refused.
    • Which system fonts need no install comes from the list astryx theme build warns by, unchanged; the editor only knows which of them ship on one system.
    • font more names the commands that work.
    • Math inside a color is checked too (rgb(calc(1px) 0 0) is refused), and color-mix() needs a share of at least one color. calc(1fr) is refused, since math takes no fr.
    • A token only widths and offsets read (--border-width, --focus-outline-width) refuses a percentage, which those properties drop.
    • A font that ships on one system says which one ("Segoe UI" ships only on Windows), instead of calling it no system font.
    • The check for a hand-edited settings module reads files with Windows line endings.
  • astryx experimental theme editor: every refusal on fonts and part colors names a command that works. (#11350)
    • A dial typed in other letters (Font, FONT) is answered as the dial.
    • A CSS font shorthand on a part (bold 16px/1.5 Georgia, serif) is split into the longhands to set, one command each.
    • A suggestion is never MDN's note in place of a value (dependsOnUserAgent).
    • A bad color on a part's color property suggests a color that works.
  • astryx experimental theme editor: per-mode part colors with commas, both-mode values and every color() space. (#11350)
    • A part color set for one mode, then the other, keeps a color that holds commas (rgb(0, 0, 255)) whole, in either order.
    • A value that already gives both modes (light-dark(…)) is refused with --mode; drop --mode.
    • The color dials read every color() space CSS has: rec2020, a98-rgb, prophoto-rgb and xyz, as well as srgb and display-p3.
  • astryx experimental theme editor: font shorthands on a part split whole, and color mixes read. (#11350)
    • A CSS font value on a part is split into every longhand it holds (font-variant-caps small-caps, font-stretch condensed, style, weight, size, line height, family). A lone keyword goes to its own longhand (bold is font-weight bold), never to font-family, and a system font keyword (caption) gets a family that works.
    • A color-mix() of two fixed colors in srgb, srgb-linear, xyz, oklab or oklch is worked out to the color it gives, so a color dial takes it. A mix the editor cannot work out says so and asks for the mixed color.
  • astryx experimental theme editor: values the browser would drop are refused, and type and font settings do what they say. (#11350)
    • An installed @fontsource/<font> package always loads the font it names.
    • Math inside calc() and the other math functions must be sound (calc(1px banana) is refused).
    • A duration or easing token takes one value, never a list.
    • A line height of 0 is accepted.
    • An exact --color-text-secondary reaches the parts that lift secondary text, with or without a color dial.
    • A font for the body alone keeps the headings' font.
    • After font <x> --on body, later commands keep working.
    • more or less past the last text-size step is refused, instead of going the other way.
    • A dial whose tokens an exact setting holds says so.
    • A token only the base theme's part styles read is no longer called unused.
  • astryx experimental theme editor: what set accepts always loads, and a theme keeps the colors it shows. (#11350)
    • A setting that the theme could not load is refused when you set it, such as a font with !important or a comment.
    • A border or outline width below 0, a duration below 0, and an unquoted url with brackets are refused on a part.
    • Switching a theme to light-only or dark-only lists the colors that visitors in the other mode lose.
    • A change that leaves the colors, the mode and the base as they were keeps the shades the theme already shows, so a theme an earlier editor built keeps its colors, and undo brings them back. The next color change maps every color with the current rules.
  • astryx experimental theme editor: a theme an earlier editor built gets its colors right on the first change. (#11350)
    • The color files are brought up to date before the theme is built from them. A font or corner change on such a theme no longer moves its colors, and the next change no longer moves them back.
    • filter and backdrop-filter take only values the browser reads; filter banana is refused.
    • A font for code alone falls back to a monospace font.
  • astryx experimental theme editor: math, keywords and fonts checked the way the browser reads them. (#11350)
    • Math in calc() and the other math functions must add like types and give the type the value needs. calc(4px + 2), calc(10px / 2px) and padding calc(1s) are refused.
    • A token never takes a CSS-wide keyword (--font-family-body inherit): it would leave the token empty.
    • A font that ships on one system only (Segoe UI, Consolas, Menlo, Helvetica Neue, Roboto) is named as such.
    • font refuses var() and names the role's token that takes it. font geist-sans is the geist preset, and text-size Medium suggests medium.
    • A hand edit to the generated settings module is built over from the settings, as the module says, instead of being kept by the next change.
    • how font no longer says a body font moves the headings.
  • astryx experimental theme editor how: number words, typed token names and states worded as actions. (#11350)
    • Numbers written as words are read: "zero radius everywhere" is square, "twelve pixel corners" 12px, "a two pixel border" 2px, "forty pixels tall", "a quarter rem", "one and a half line height".
    • "least", "minimum", "as little as possible" and "barely any" mean less; "maximum roundness" is a pill.
    • A token typed by name with a value ("--focus-outline-width: 3px", "--color-background-card to #fafafa in light mode") is set exactly. A token name that does not exist is refused with the nearest names, never answered with another token.
    • States worded as actions keep the state: hover, click and press (active), typing and tabbing to (focus), "after I check" (checked), "picked" (selected). "Tab to" no longer names the tab part, and a link's color in one state is set for that state.
    • "Cards the same radius as buttons" gives cards the token buttons read; "buttons twice as round as inputs" changes buttons; "the same color as the danger color" uses that color's token.
    • "Shouldn't links be underlined?" asks for the underline.
    • A pasted h1, h2, h3 { … } includes h1.
  • astryx experimental theme editor how: a mode phrase scopes the ask, and typed tokens are read only when they are real. (#11350)
    • "In dark mode only, cards #111111" sets the cards in dark mode; the theme becomes dark-only only when the ask is about the theme's modes. A clause that only names a mode scopes every clause after it. "Daytime" is light mode; "at night", "night mode" and "OLED" are dark mode (a bare "day" or "night" is not a mode); "dark: …, light: …" sets each mode, and two values for different modes are not a contradiction.
    • A token typed at the start of a question is set exactly; a flag-like word that is no token (--like, --value) is read as words, and a real token in a later clause ("and set --border-width 2px") joins the other changes. A quoted font stack keeps its quotes.
    • "No more than 2px borders" and "at most 2px" are 2px, not none.
    • "Error text" and "labels" with no part name give a lookup, never the whole theme's text.
  • astryx experimental theme editor how: lists of parts, undo wording and typed numbers beside direction words. (#11350)
    • Parts listed before the ask all take it: "cards and dialogs with no shadow", "tooltips and toasts black". "Less padding on cards but more on buttons" answers both, each its own way.
    • "Every part bold except body text" makes the headings bold and leaves the body as it is.
    • "Remove my accent override", "revert the cards to default", "I set the accent to red by mistake" and "put the card shadows back" take back what the theme sets with undo.
    • A typed number beside a direction word is the value: "thicker focus outline, 4px" is 4px, "bigger tap targets, at least 44px" is a 44px minimum height, "8 or so px" is 8px.
  • astryx experimental theme editor how: lists, several colors and per-mode colors. (#11229)
    • Each line of a question, and each item of a bulleted or numbered list, is its own ask. A "no" on one line never reaches the next.
    • Several colors in one question are each kept: "accent #0ea5e9; danger #ef4444; success #22c55e" sets all three. A hex binds to its word whether it comes before or after it ("#0d6efd primary"), "bg=#fff text=#000" splits per color, and "primary" is the accent. "Secondary" has no setting of its own, so it is offered as the secondary button fill.
    • A color that how works out (darker, lighter, more contrast, stronger borders, a darker overlay) is set per mode, each from that mode's own value, so dark mode keeps light text. "More contrast" acts in light and dark mode and says so. "Fails contrast on white" never picks white. Text already at full contrast says so instead of changing nothing.
    • CSS property names read as their properties: letter-spacing, line-height, font-size, font-weight.
    • Better meaning: "drop shadow: x 0, y 4, blur 6, spread -1, <color>" sets that shadow; "ditch" removes; "revert the rounded corners" takes back the corner settings the theme has; "swap A for B" asks for B; a radius of 0 is square; "12 pixels" is exactly 12px; "taller (44px)" sets that height; "too warm" makes the grays cooler; a part with no recorded fill gets darker or lighter through a brightness filter.
    • Typed values are kept: gradients written "from A to B", shadows with several layers, quoted font names and font names before the word "font". Quoted text that is not a font name is read as words.
    • Parts: a table's header, the error banner (--when status:error), "button color" as the text color. Markup and comment text in a question are ignored.
    • Italian, Spanish, Korean, Russian, Arabic and Hindi words for buttons, cards, rounded, shadow, remove and accent are read; "y", "et", "und" and "и" join two asks.
    • A step given twice in one answer runs once. undo is suggested only when there is a change to undo.
    • When font --on body also changes the heading font (the theme sets no heading font), how font says so, and a body font question uses --font-family-body.
    • An answer with no command says why. Commands in an error's suggestions start the same way in JSON as in text.
  • astryx experimental theme editor how: "swap A for B" and "replace A with B" ask for B only when A and B are both colors or both fonts. "Replace the shadow on cards with a border" removes the shadow and adds a border, and "switch off" or "switch the buttons to" no longer names the Switch component. (#11262)
  • astryx experimental theme editor how: right way round, whole font names, and the app's themes from any folder. (#11262)
    • Polarity: "flat cards" removes the cards' shadow ("too flat" adds one); "not round enough" is rounder; "nothing rounded except avatars" is square with round avatars; "shadows too strong" is softer; "borders too dark" is fainter and "too light" stronger, per mode; "not so much padding" is less.
    • "Border radius" in two words is the radius, never the border width. A rem or em radius for the whole theme is set in pixels (0.75rem is 12px), and a % radius keeps its %. "button padding 8" is 8px.
    • Font names of several words are kept: shipped fonts by their full name (DM Sans, IBM Plex Sans, Geist Mono, JetBrains Mono), and other names as typed (Roboto Mono, Source Sans 3). "Sans-serif" is never read as serif.
    • "Off-white" is #fafafa. "Headings too big" changes the heading scale. "#e5e5e5 not pure white" sets #e5e5e5.
    • "1) … 2) …" markers and "Feedback round 2" are not values. primary=[#7](https://github.com/meta/astryx/pull/7)c3aed radius=10 font=Geist reads each pair. "Body text 16px" is the text size.
    • A link's color is --color-text-accent, the token a link reads; the answer says it also colors other accent text.
    • Parts: table cells, menu items, radio buttons, text areas, selects, skeletons and popovers. A variant word before a part ("success badge") adds --when variant:success. "Card and Dialog" answers both. "Match the header to the sidebar" changes the header. A shadow ask after "serif headings" is for the theme, and a tab's text color is on the tab.
    • "What does spacing more do" is a lookup. Light and dark values in one question set each mode. "I hate the purple, make it orange" sets the accent.
    • A typed text color that one mode's page would make unreadable is set for the other mode only, unless the question asks for every mode or sets the page too. A sequence never gives the page the color it gives the text.
    • how from a subfolder of the app finds the app's themes, like the other editor commands; a picture named from there still opens.
  • astryx experimental theme editor how: a picture named from a subfolder of the app opens from that folder. A number that ends a sentence ("Use radius 8. Shadows off.") is a value, not a list marker; only "N)", or "N." at the start of a line or after a semicolon, starts a list item. "Shadows off" and "borders off" remove them. (#11303)
  • astryx experimental theme editor how: named CSS properties, typed values kept whole, and parts it cannot name. (#11350)
    • A CSS property named in the question is set as named, with its value checked against the property's grammar: caret-color, outline-offset, text-shadow, accent-color, text-underline-offset, font-variant-numeric, text-wrap, transition, padding-block, any property set accepts. It is never swapped for another property.
    • Typed values are kept whole: clamp(), calc(), color-mix(), a four-value radius, line-height: normal. A font size of 0 is refused by name.
    • "Modal" names the dialog again; "carrd" and "caard" are corrected to card, and "lines" is no longer corrected to "links".
    • A typed color is the target: "too bright, use #b91c1c" sets #b91c1c.
    • Gray stops are read ("gray-50", "zinc-900", "slate 100", "neutral-200"); "subtle gray" is a light gray; "charcoal text instead of black" sets a charcoal.
    • Fonts any machine has (Arial, Menlo, Times New Roman, Helvetica Neue, SF Pro) and typed names (Plus Jakarta Sans, Noto Sans, Fira Code) are set as named; "the default Mac font" is the system font.
    • "menu", "select", "list", "divider" and "footer" name their parts, and so do "combobox" (the complex selector) and "accordion" (the collapsible). A part word how cannot name ("image") gets the closest parts and a lookup, never a whole-theme change.
    • "too shadowy" is softer. "On focus" reaches the next clause; "night mode" is dark mode; "dark by default" is a dark-only theme; "lift it with a bigger shadow" is the hover shadow only; "ON: CARD" names the part; "the cards and the dialogs both" answers both.
    • A picture whose name has spaces, as macOS names screenshots, is read as a picture.
    • Questions about the tool get the command that answers them: help, "list every dial", "which token sets the page background?", "explain text-size", "how do I see my changes", "difference between corners and border-radius".
    • The corners lookup's example is a token whose change shows.
  • astryx experimental theme editor how: typed values win without a colon, and words read the right way round. (#11350)
    • A percent inside a gradient or after a color is never an opacity; "50% opacity" still is. A typed gradient with stops ("#2563eb 0% to #9333ea 100%") is kept.
    • A typed value after a property word is used whole, colon or not: gradients, opacity 0.5, border 0, border color transparent, light-dark(), var(), margin 16px, filter: blur(2px), backdrop-filter blur(8px), two-layer shadows. A property name never picks a part ("backdrop-filter" is not the backdrop). A value the property cannot take ("padding NaNpx") is refused by name, and so is a font size of 0.
    • drop-shadow() is kept as typed.
    • "halve", "half", "cut in half" and "x0.8" mean less; "twice" and "double" mean more. "0.5 rem", "1.5 em", "14 px" are one length.
    • "reset", "revert", "back to default", "what it was", "clear the override" with a setting take it back with undo <theme> <setting>, or say the theme does not set it.
    • "lighten up" is lighter, "tighten" is tighter tracking, "knock the contrast down" is less contrast, "open up the leading" is line height, and "the gray text fails contrast, darken it" darkens the secondary text. A clause that only describes the problem ("the hierarchy is flat") is not a change; "or maybe not. actually yes" keeps the ask.
    • "heading color" is the text color. Accordions, comboboxes and notifications name their parts; a part list with no match lists the parts of components that use the word. "error toasts" adds --when type:error, "read-only" is the readonly state, and "loading" or "unchecked" say the part has no such state.
    • CSS named colors such as tomato are read.
  • astryx experimental theme editor how: complete border values, layer opacity, and the right kind of change. (#11350)
    • A border or outline value is complete or goes to the right longhand: "card border 2px" sets border-width (a border with no line style draws nothing), "border width 2px" and "border bottom width 2px" set those properties, "border 0 0 2px" keeps all four widths, a width with a color gets a solid line, and "text-decoration #2563eb" sets text-decoration-color. "border width" never sets the part's width.
    • "shadow opacity 0.2" sets the shadow's alpha, and "background opacity" or "border opacity" make that layer see-through, never the whole part.
    • Font names win over dial words: "Space Grotesk headings" and "headings in Space Mono" set the font.
    • Negation is kept: "should not shrink when pressed" is no scale, "but not bold" is a regular weight, and "why are my headings not bold" asks for bold.
    • The right kind of change: "thinner body text" is a lighter weight; "faster hover transitions" sets transition-duration; "turn off all animations" and "transition duration 300ms everywhere" set the shared duration tokens; a part with no motion of its own, or no fill (the spinner), says so; "dim the white text" dims it; "a border instead of a shadow" removes the shadow and adds the border; "button press scale 0.98" scales on press.
    • Point sizes are read (11pt is 15px), and a rem text size is read in pixels.
    • A heading's color, which comes from its prop, is set with --color-text-primary --on heading; "headings red" is the text color.
    • The divider is a part: its thickness and color are --border-width and --color-border on the divider.
    • "go back to the neutral theme" takes back every setting, one undo each.
    • Small caps, tabular numbers, balanced heading lines, "I can barely see the borders" and "hover does nothing visible" are read; tool questions about using, renaming, versions, files and hand edits get the command that answers them.
    • A fully see-through picture is refused: it has no visible colors.
  • astryx experimental theme editor how: a question names a part by any theming target name in Core's catalog ("drawer", "date range input"), read from Core instead of a list of its own; phrases, groups and variant words stay as overrides. Near misses are corrected with the CLI's shared edit distance. (#11350)
  • astryx experimental theme editor how: "day" is light mode only in a mode phrase ("daytime", "day mode", "in the day"), so "the selected day in the calendar" or "all day" no longer scopes the change to light mode; a token typed in a later clause ("and set --shadow-high 0 4px 12px black") keeps its whole value. (#11350)
  • astryx experimental theme: the tenth pass of fixes. (#11350)
    • --state disabled styles a disabled button, link or tab the way Core marks it (aria-disabled as well as :disabled). A focus or active state on a part that never takes it is refused.
    • A spacing step on a group member set alone starts from the group's value. Refusals keep every scope flag they can (--when, --state, --only). A tab inside a value is white space.
    • Undoing an exact property names the dial that applies after it. A font var(...) refusal suggests only a command that works. A name Windows reserves (con, nul, com1) is refused, with one that works.
    • compile of an editor theme finds the theme from the file, from any folder, and never mistakes a src/themes/<name> folder for one. A damaged settings file is refused as a normal error. Its suggestions run as printed in JSON too.
    • The refusal for list, add, use, remove and eject on an editor theme says how to use its module, and not to edit the generated themes module.
  • astryx experimental theme: the eleventh pass of fixes. (#11350)
    • A local theme with the same name as an editor theme keeps the stable message. Compile guards only the editor's own files, also through a linked folder. The refusal for an editor theme shows a merge snippet that runs, with its stylesheet.
    • A list where one theme goes names each theme. corners more at pill and less at square write nothing. A corner word on buttons or surfaces names the corners dial.
    • A bad property value suggests a value the property takes (no-wrap → nowrap), in the same scope.
    • --state disabled is refused on a part that is never marked disabled. focus-within is refused where nothing inside takes focus. how <part> lists only states set takes there.
    • Option errors suggest a help command that runs as printed in JSON too.
  • astryx experimental theme: a build is judged by its content, never by file times, so a settings module saved again (a format-on-save, a checkout) no longer fails compile --check, and preview app --theme copies a build that matches its settings without building it again. --state disabled on a tab styles it the way Core marks it. (#11350)
  • astryx experimental theme: the third pass of fixes. (#11262)
    • Saved settings are checked on load as set checks them, including where they apply. Each setting the editor no longer accepts is listed with a command that removes it. Each command works on its own, however many are listed. A setting that is not accepted never reaches the build.
    • corners more and less read the base theme's radius in any unit. A saved corners value must be a rung or a pixel size.
    • undo <theme> base and undo <theme> mode go back to what the theme was made with. undo <theme> headings weight|tracking removes that half. A value given to undo is compared as set reads it. undo <theme> <thing> <part> names --on <part>. A blank --on, --when, --state or --mode is refused.
    • If a group setting hides a value, setting the value again moves it last, so it wins. A change that changes nothing writes nothing, the preview included. A newer background wins over an older background-color on every variant. A color on text, a heading or a link is refused, naming the text color token, because the color prop decides it. A quoted string may hold < or >, and a value may span lines.
    • A <theme>.theme.ts that no longer extends its settings is refused, and show says so. A built-in theme's name is refused for new. A theme written by hand or ejected gets a clear refusal from the editor. In both cases the refusal gives a command that works.
    • show rebuilds a damaged build and says so, and show --section --png photographs the section's own sheet. A damaged palette.config.json is made again from the settings, and its text is kept as palette.config.damaged.json. The preview route compiles for names like b-2. preview.html is the same on every build, and a change of letter case alone is not listed as a token change.
    • Refusals show control characters as escapes. Suggested commands quote their words for any shell, and fill in real values. A misspelled property points to the property.
    • In experimental theme, a moved or misspelled subcommand names where it is now. A bare group answers --json with its help. --detail compact and --dense print the status line alone. compile refuses the editor's own settings files and --family for an editor theme. compile --check checks an editor theme by the editor's rules, and waits for a change in progress. The editor's builds write the same headers as compile. Compile errors and stale checks name the experimental commands and never change text that you typed. add, use, remove and eject explain what an editor theme is.
  • astryx experimental theme: the fourth pass of fixes. (#11303)
    • The theme lock is the release cache's lock, renewed while a command runs, so a long build is never taken over from another computer or container. The lock and the part-data cache come from the same node_modules.
    • Corners keep the base theme's proportions between radii, so a step up never makes a container or page radius smaller. Going up the scale never makes any radius smaller, inner corners included. A step on a part moves to the next rung that part shows bigger or smaller. A group setting that covers an earlier part setting says so, and show marks the part setting as not shown.
    • A word for a value names that value (surfaces elevated suggests raised). how base lists installed bases and names the rest with their install line. Values a property does not take (display flexx, padding auto) are refused. A plain value that replaces per-mode values says which it replaced.
    • A base theme updated since the build is noticed, and the theme is built again. A folder where a file goes is refused. When React is missing, show still lists the settings and builds the theme, skips the pages and pictures, and names the install line. The editor's own temp files left by a stopped command are removed.
  • astryx experimental theme: the fifth pass of fixes. (#11303)
    • A theme lock whose holder stopped renewing it is taken over after 30 seconds, whatever computer it names, and a lock renewed or taken a moment before that takeover is put back. compile holds an editor theme's lock while it builds or checks it. The editor's cache stays in the project's node_modules.
    • A corners rung gives a part what it gives the radius token that part reads, pill keeps checkboxes square, and corner sizes written any way are read plainly. Spacing is refused where it shows nothing, and controls stay at least 24px.
    • Saved settings on a part, state or variant that does not exist are refused with the undo that removes them. A damaged mode or base is fixed by setting it. Text contrast is measured for each variant of a part.
    • A one-mode theme changes the build. A per-mode color keeps the other mode as a color. Big files beside a theme are never read. Undo after a gray color writes the same bytes. A render folder a stopped command left is removed once it is ten minutes old. A damaged palette config is copied aside only by a command that writes, and the result names the copy.
  • astryx experimental theme: review follow-ups. (#11303)
    • A corners step on a part moves to the next rung that part shows bigger or smaller, counting a group setting that covers it, and show reports the radius the build writes.
    • CSS values are checked against the property's grammar, so valid values such as 12pt, stretch and env() are taken, a value that is only a var() is taken on any property, and values the browser would drop are refused, with a value that works.
    • A color set for one mode on a part keeps the base theme's own value in the other mode. Text contrast reads the same values.
    • Every saved setting the editor no longer accepts is named, and each suggested undo works while the others are still saved.
    • The CLI now depends on css-tree for these checks. It adds about 2.09 MB unpacked to the install (css-tree 1.36 MB and its mdn-data 0.73 MB), and loads only when the editor checks a CSS value; no other command loads it, and startup is unchanged.
    • show suggests installing React only when React is missing, and the busy message says how long the other command has held the lock.
  • astryx experimental theme: the sixth pass of fixes. (#11350)
    • A theme lock is never taken from a command that still runs: not from one in a container on the same computer, and not from one that is only stopped. A command that lost its lock while stopped writes nothing more, and leaves the files as the command that took the lock left them.
    • A theme whose settings were deleted or damaged, or left by a stopped new, is made again by new with its name. Your own files stay, the damaged file is kept, and undo steps back to the earlier settings.
    • show rebuilds a cut-short stylesheet, and names a picture cut to the window. Demo images open from disk. Leftover temp files are removed.
    • Refusals for a bad argument, a damaged or missing theme file, a busy theme and a missing project lead with a command that runs.
  • astryx experimental theme: the seventh pass of fixes. (#11350)
    • Settings of the wrong shape are recovered like damaged ones: new with the theme's name makes it again and keeps the file. A new that recovers a folder changes nothing until every check has passed.
    • A command that lost its lock while stopped puts nothing back and leaves the other command's files alone.
    • Pill never makes a container or page less round, and a whole group of containers gets the container radius. A step reads every setting that reaches the part. Focus on a text input is named as focus-within.
    • show works without React and says what it skipped. The sheet says when a change made it out of date. A variable that is not a design token needs a fallback, and a value that is only a variable is taken on any property.
    • compile --watch builds an editor theme again.
  • astryx experimental theme: a theme an earlier version built keeps its corner radii until corners or the base change, and undo restores the radii a step was built with, exactly. Each undo step now records those radii; steps an older version wrote are still read. (#11350)
  • astryx experimental theme: the ninth pass of fixes. (#11350)
    • The undo history is never deleted by a recovering new, and a stopped new's leftover marker is removed by the next change.
    • A theme typed as a file name (t.theme.ts) is refused with a suggestion of the theme it names. An undo that is refused suggests undos.
    • Undoing a radius token rebuilds the corners without it. Inner corners never get smaller going up the scale. A step never moves a part the other way, starts from an exact border-radius, and for a variant starts from the part's plain setting.
    • A --state that a part never takes (disabled on a card, which is never marked disabled) is refused and says what to do.
    • undo names the setting that applies after it. Refusals suggest the nearest value that works.
    • A command that lost its theme lock publishes no build output. A change that changes nothing rebuilds a build left stale.
  • astryx experimental theme preview: add refuses a folder whose URL the app's own route handler or page already serves, including a route.ts or page.jsx in the folder itself and a route.ts in a route group. add --path and app refuse Next's build folder (.next/, out/ or the distDir next.config names), which the next build empties. On the Components page, a component as tall as the window scrolls in a bounded frame, and each cell is only as tall as its content. (#11350)
  • astryx experimental theme preview add: next.config is read from its syntax, not its text. Comments, keys inside other objects and constants are read as Next reads them. A pageExtensions list built from a spread no longer refuses the app; the result notes that only running the config tells. basePath and distDir are read the same way. (#11350)
  • astryx experimental theme preview: last fixes. (#11262)
    • Install suggestions name npm when nothing says which package manager the app uses, never npx add or npx install.
    • A change stopped before its route was written is undone, so list shows only the pages the route shows. A refusal says what finishing a stopped change wrote. editor set names a preview it left as it was while such a change waits. A damaged step record no longer leaves temp files behind. A move of an older preview's pages stopped part way is finished: the old copies go once they still hold what the move planned to remove.
    • remove --path at a folder that holds the app suggests a plain remove.
    • Suggested --path and preview app folders are written from the folder the command ran in.
    • preview app -app says to put the folder after --.
  • astryx experimental theme preview: running prettier over the preview, with any options, no longer makes its files count as changed by hand. The check compares the code, not its formatting. An edit to code, a string or a comment still counts. (#11303)
  • astryx experimental theme preview add: only an optional catch-all route ([[...slug]]) in or at the preview's URL is refused; a required one ([...slug]) never serves the folder's own URL. A root layout inside nested route groups is found. basePath is read with comments left out, and one set from code is named in the URL to open. (#11350)
  • astryx experimental theme preview: safer refusals and recovery. (#11209)
    • No refusal suggests deleting files: a damaged theme-preview.json, a page changed by hand, or a file in the way gets plain instructions (fix it by hand, rename it, or move it into a folder of its own) instead.
    • --path at the project root, in src/ or at the routes folder itself is refused: those folders hold the app. An older preview found there is named, with the remove that clears it.
    • A whole remove stops, deleting nothing, when page.tsx was changed by hand, since it imports the pages.
    • A formatter run no longer counts as a change by hand. editor set and show name the preview files they left as they were (previewStale).
    • A recorded page whose file is gone is written again, or left out of the nav, so the route always builds. Moved pages get a hash. A failed write leaves no temp file or empty folder, and says which step failed. A read-only file keeps its mode.
    • preview app --theme waits for other commands changing that theme, and its retry suggestion keeps --theme.
  • astryx experimental theme: with an older installed Core whose component docs have no playground defaults, the catalog now builds each component's demo from its doc's props. Required props get a sample, and a group gets three of the items its doc suggests. The contact sheet, the Components page, how answers and contrast checks keep every component. A part with its own doc, such as Heading, now shows on its own. An open overlay shows once on the pages people see, and a switched-off switch or checkbox is labeled for the state it shows. preview list marks a theme whose folder is gone (themeMissing). After a damaged step record, a page file in no record is named, never deleted. --png with a browser that is installed but fails now names the error. (#11350)
  • astryx experimental theme preview: removes that never touch project files, and previews only where Next serves them. (#11229)
    • remove deletes only the route file, the record and recorded page files, and only when a recorded hash shows they are as the preview wrote them. Any other file the record names, and any file with no recorded hash, is kept and named.
    • add refuses a folder that holds a package.json, a URL another page already serves, an app whose next.config leaves out tsx page files, src/app/ while app/ is what Next serves, and a folder outside the root layout. An app with its root layout in [locale]/ gets the preview there.
    • A template's needs come from its real imports, never words in comments or strings. A package the app does not name gets the command that adds it.
    • A theme with no build is built only after every check passed, holding the theme's lock, with a note. An edit inside a string counts as a change by hand.
    • editor show and preview app run when the lock folder cannot be written.
    • A damaged record in a folder that holds the app names renaming the record. A record with a byte-order mark is read. list says when the theme is gone. Base themes count as package themes, installed or not. --template takes any case. preview app refuses public/ and names Windows does not allow. An empty route group folder goes with the preview.
  • astryx experimental theme preview: a preview change stopped part way (a kill, a crash) is finished by the next preview add or preview remove. The change writes a step record before its first rename. The next command removes leftover temp files, records the preview's own files, keeps a page whose new file never landed at its old place, and says so in a note. (#11262)
  • astryx experimental theme preview add: in an app with a root layout in each route group, the preview is accepted under any of them, and a refusal names each one. (#11262)
  • astryx experimental theme preview: the Components page now uses the playground a doc gives a component in its own entry, so Stack shows its cards. A nav that opens over the page, such as MobileNav, is left out like a drawer. The Text cell now suggests the text color token, a command that works. A divider fills its row, and a one-pixel line no longer counts as showing nothing. For an app folder named like a flag, preview app prints cd ./-k. (#11350)
  • astryx experimental theme preview add: refuses a folder with an optional catch-all route ([[...slug]]) in it or at its URL, an app whose routes folder has no root layout anywhere, and a default or recorded preview folder that leads outside the project through a link. The URL to open now starts with the basePath next.config sets. When the app never imports Core's stylesheet, the result names the import line to add. When a theme loses its last color under a Colors page changed by hand, the page is kept and the palette module it imports becomes an empty stand-in, so the app still builds, and the result says so. A link inside the preview folder that leads outside is refused, naming the link. (#11350)
  • astryx experimental theme preview add: the refusal for a next.config whose pageExtensions leaves out tsx now suggests commands: the same add once tsx is listed, or preview app for a new app of its own. (#11350)
  • astryx experimental theme editor reads CSS from one source instead of its own lists. Property names and value grammar now come from css-tree. The neutral color's shades come from the shipped Neutral theme, and system fonts from the list astryx theme build already uses. (#11350)
    • Six newer standard properties (timeline-trigger-range and its relatives) are accepted. An outline style in capitals (SOLID) is accepted.
New Features
  • The integration file takes an optional logo ({light, dark?}, paths to images the package ships): the logo catalogs show beside the package name. When the integration file has no logo, the check uses package.json marketplace.logo. astryx integration check adds two notes that say what a catalog needs to list a package: package_without_logo, when the logo names no PNG, JPEG, WebP or shapes-only SVG of at most 512 KB that the package ships, and package_without_example, when the package has components but no example block. A package of themes, docs or codemods alone needs no example, and a package of icon sets alone draws neither note. Both are information only: they fail no check, with or without --strict or --next. The new "Get your package ready to list" section of astryx docs authoring/ship/checks shows how to add both. (#11278)
  • integration verify adds an information line, in text output only, after a successful pack whose manifest is astryx.integration.ts: the CLI transpiles it on first read on each machine, so shipping astryx.integration.mjs loads faster (pointing at astryx docs authoring/ship/publishing keep-private-files-out). It changes neither the result nor the exit code. (#11382)
Fixes
  • In a run under Yarn Plug'n'Play's loader, such as yarn astryx, doctor's search catalog cache row still names the folder and its size and adds that such a run keeps no catalogs, as search and build gather every time there. The plain astryx command in the same project keeps them as usual. (#11299)
  • The code the CLI transpiles from TypeScript files (an integration's astryx.integration.ts, a TypeScript config, codemod or template doc) is kept in the CLI's per-user cache folder (~/.cache/astryx/jiti on Linux, ~/Library/Caches/astryx/jiti on macOS), made for the user alone, instead of the system temp folder, which on Linux every account on a machine shares; on macOS, where that folder is already per-user, the copy now survives temp clean-ups. A folder another account owns or can write to is not used; the transpiled code is then kept in memory only. Emptying the temp folder no longer makes the next run transpile everything again. (#11360)
  • A catalog search or build kept between runs now records which inputs it is for and is used only for those, so a cache file copied under another entry's name is never used. (#11301)
  • A run under Yarn Plug'n'Play's loader, such as yarn astryx, no longer reads a search catalog that a plain astryx run kept: it gathers every time, as doctor says, since its modules resolve through Plug'n'Play, which a kept catalog's checks do not follow. (#11344)
  • The release cache's lock takeover checks the owner record of the lock it moved aside. A lock another command took in the moment between the check and the move is put back instead of removed, and the takeover waits for it. (#11313)
  • astryx swizzle reports ERR_WRITE_FAILED when its output path is a file on the minimum supported Node version. The original file stays unchanged, and the error identifies the failed write relative to the project instead of exposing a cleanup error. (#11186)
  • theme build --out warns, naming both sources, when it replaces the built output of another theme source that still exists; an output there is its own when its header names this source, or names a source that no longer exists. A build output's header names its source from the project root of the outputs, so a build from any folder writes the same outputs and --check agrees with it from every folder; the source a header names is matched exactly. Builds to the default paths beside the source are unchanged. An --out path that does not end in .css still builds, with a warning, and the import line the build prints names the file as written. Several themes that build the same outputs are refused before any of them writes. The next steps after theme eject and theme template quote their paths, and theme template on a file --overwrite would refuse names a free path instead (its receipt adds overwritable and alternative). A damaged generated theme module names how to rebuild it (delete it, then theme add each theme it held), a default that is not added names theme use with an added theme, and a folder where the module goes is refused in plain words. A --family member that is a plain object says so and names a build of it on its own. (#11346)
  • Every refusal of theme use, theme remove, theme add, theme eject, theme template, theme targets, theme build and theme list names a command that works. theme use and theme remove of a theme that is not added suggest theme add <slug> only when that theme exists, and theme list otherwise; removing the default names theme use with another added theme. Unknown slugs in theme add and theme eject suggest whole commands for the closest themes, theme targets with no match suggests the full list, and refused paths, flag combinations and loads suggest the command that runs. A theme that imports a package the app lacks names the install command in theme build, without absolute paths, and in doctor, followed by the rebuild command of any other stale local theme. theme use or theme remove of a theme that is not added and that more than one package provides names theme add <slug> --package <package> for each. theme build --check text lists the checked outputs, as the JSON does. (#11346)
  • theme build refuses one of its own outputs (.css, .d.ts, .js) or a file of a kind no theme module has (a plain .css file) before loading it, and names the theme source to build instead of a loader error. A missing input that is a bare theme name (theme build brand) or a path with backslashes suggests the theme source that exists. theme eject from a subfolder forks into the project's src/themes, as theme list and theme add read it, and reads a relative path from the working folder. theme targets .astryx-switch reads the class as the output prints it. The experimental theme copies no longer reword text you typed that holds astryx theme …. (#11323)
  • theme build --watch (and experimental theme compile --watch, whose help says so too) rebuilds when the theme source or any local file it imports changes (an ejected fork's palettes, a split theme), not only the entry file. theme eject refuses the local themes folder itself, which made theme list and theme add fail for every theme, and a folder in it named after another theme, which they skipped; it names the default target. A fork into a new folder in the local themes folder takes the folder's name: its entry, descriptor and export are renamed to the build's binding (src/themes/acme-ocean → acmeOceanTheme.ts, acmeOceanTheme), so theme list, theme build and theme add find it as that theme; a backslash in its path separates folders. --package on theme add, theme list and theme eject also takes the package a bundled theme is imported from (@astryxdesign/theme-butter), the name the CLI records and prints. A bundled theme whose package is missing names the install command and then the add. An unknown subcommand of theme or experimental suggests whole commands, closest first, and theme editor / theme preview point at experimental theme editor / experimental theme preview. The discovery refusals for a theme descriptor outside a theme folder, or in a folder with another name, say where to move the files. (#11375)
Performance
  • build keeps its block picker's per-block vectors beside the kept search catalog and reads them back on a later run with the same catalog, instead of working them out on every call. Every answer is the same. (#11342)
  • Checking whether a kept search catalog is still fresh no longer builds an error for each absent path it looked up, so warm search and build start a little faster. Every answer is the same. (#11316)
  • component, template, theme, discover and search keep each integration's contribution-check results in the per-user cache folder beside search's catalogs, and read them back while every file, folder and environment variable the checks read is unchanged, instead of checking the integration again on every call. On a project with a large integration this takes about 0.2–0.3 s off each of these commands. doctor's cache row names the commands that keep what they gather. (#11367)
  • search and build keep the catalog they gather in a private folder in the user's cache folder (catalogs, beside the release cache), and a later run uses it only while every file and folder it read, every module it loaded, and every environment variable it read (kept as a digest, never its value) are unchanged. Otherwise the run gathers fresh, exactly as before. A run with unchanged inputs answers in about a third of the time, with the same output. Only a published CLI keeps catalogs, and not where folder ownership cannot be checked (Windows) or under Yarn Plug'n'Play; doctor lists the folder and its size, and deleting the folder clears it. (#11251)
  • search keeps the index it builds over a kept catalog beside that catalog, so a later search over the same catalog reads the index back instead of building it again. The index is a function of the catalog's text, so it reads back exactly as built; it is keyed by that text and by the CLI code and files that build it (the CLI files the catalog depends on, the index's own code and the component cards), so an edit to an installed copy, as patch-package or a hand edit leaves it, is never answered from an index built before the edit. It is kept only where catalogs are kept. Every search prints the same answer. (#11300)
  • Contribution validation now loads @babel/parser only when it parses a contribution's source, so a run where nothing else loads the parser, such as component <Name> --json or hook --list, no longer loads it. Every command prints the same output. (#11256)
  • jiti now loads on first use instead of with every command, and component --json no longer loads the theme API, which only component's text output needs, so commands that never need them start faster. Every command prints the same output. (#11242)
  • search (and build, which ranks with it) splits each name into words, lowercases each description, and builds each query term's word pattern once per run instead of once per candidate and term. Every result is the same. (#11243)
  • In a project with no integration (no Astryx config, not an integration itself, and no installed dependency that ships one), component, template, theme and discover no longer record their run for kept check results, so they skip that work entirely (about 15–40 ms each). (#11380)
  • The stored doc exports now cover Core's docs and the CLI's own command and API docs too, and a read parses only the docs it needs. Any doc file whose text matches a stored doc reads the stored exports, since such a doc's exports depend on its text alone. search and build print the same output faster. (#11240)
  • astryx manifest reads the manifest stored in the package when it is published, instead of loading every command to build it. The stored manifest is what the fully loaded CLI builds, and the publish step checks it is the same beside each package manager's lockfile, so while every command loads manifest prints the same output. A command whose module fails to load is listed in the published manifest under its normal entry, instead of being marked as failed; running that command still reports the failure. (#11233)
  • doctor reads its audit of the CLI's own authoring docs from a copy stored in the package when it is published, instead of parsing the CLI's authoring sources on every run. The copy is used only while the package version and every doc, type file and folder the audit reads are unchanged, so an installed CLI's doctor reports the same thing. (#11232)
  • build reads which packages a template Astryx ships imports from a copy stored when the package is published, instead of parsing the template's source on every call. Any other template, such as an integration's, is parsed as before, and every answer is the same. (#11315)
  • upgrade --from a version before 0.7.0 skips the theme-alias codemod on source files that name none of the removed theme targets, as it already skips other codemods on files they cannot change. Every run writes and prints the same. (#11265)
  • upgrade skips a codemod on a file it cannot change: a core codemod may declare the words a file must say for it to act, and a file that says none of them, holds no backslash, and parses, is left untouched without running the transform. A file that does not parse still reaches the transform, so it is reported as before. One codemod that checked every spread against every component now checks only components the file imports. Every run writes and prints the same. (#11249)
Documentation
  • The calendars guide is titled "Calendars", and the docsite shows it under Internationalization in the sidebar, at the same address. (#11269)
  • Hook docs for useThemeName, so astryx hook useThemeName and astryx search return it, and a useThemeName — Active theme example block: the name of the theme wrapped around the caller. (#11235)
  • List's anatomy now names its optional header and drops a description part that List does not render. The ref docs now say that the ref reaches the list element, with or without a header. (#11277)
  • astryx docs authoring/ship/publishing recommends shipping astryx.integration.mjs rather than .ts (and .mjs doc files and codemods): the CLI transpiles each TypeScript file it loads on first read per machine. It also says a package with two manifests fails to load. (#11364)
Other Changes
  • Internal: the scanner that finds template fixture references takes the replacement as a function, so the docsite's preview build finds those references the same way a copy does. No change to any command's output. (#11320)
  • On Windows, the CLI's test setup now rebuilds a stale Core. It started pnpm directly, which Windows installs as a pnpm.cmd batch file that cannot start without a shell, so the setup stopped with spawnSync pnpm ENOENT before any test ran. It now runs the build through cmd.exe. macOS and Linux run the same command as before. (#11051)
Contributors
Thanks to everyone who contributed to this release:

0.7.14

Experimental APIs
  • astryx discover lists WeightedSVGIcon among @astryxdesign/lab's components: an experimental SVG icon whose drawing follows the surrounding font-weight. (#7918)
  • astryx experimental theme editor how answers a question that names the background ("a yellow background") for the background, with its tokens first, instead of as a color question. The preview's Overview page shows its open popover and tooltip first, below their anchors in space kept free for them, so they no longer cover the table. (#11159)
  • astryx experimental theme editor: colors are generated the way the official themes are. (#11209)
    • An exact color you give stays exactly as given. In light it never moves: when no text reads on it, the text changes, and a pale fill that does not stand out from the page is reported. In dark it is kept too when text on it reads at 4.5:1 and it stands out from the dark page at 3:1, so the dark shades around it follow it; otherwise dark mode starts at shade 70, as the official themes do, and the result says why. A dark side never uses a light shade.
    • set <theme> neutral <color>: your exact color sits at its own shade in light and dark, and the shades around it follow it.
    • Text on accent and status fills comes from the neutral color's white or near-black (near-black first on warning), or pure black or white without a neutral color. Status tints are see-through in dark, and their text is measured over the surface; the accent tint is dark shade 30, or the nearest darker shade that citation text reads on; a tint is never the fill's own shade.
    • An exact --color-accent (or another main color token) wins over the color it would replace: the text on it is picked to read on your color, the focus ring keeps following it, a pale one is reported, and the result says so.
    • Text, icons and the focus ring take the nearest shade that reads, lighter or darker, so bases with dark light-mode surfaces get readable colors too.
    • Hand edits to palette.config.json are kept: your own anchors, names, kind, neutralProfile, vibrancy written by hand, and colors of your own. One-mode themes generate one mode. A stop layout maps by its own shades, half stops included; one without black and white, with too few shades or with a wide gap is refused. Fields the generator does not read are named. What the editor replaced is named when a color change touches the config.
    • A hand-edited generated color file is never overwritten, receipt or not; formatting is not an edit. Only color changes wait, and the refusal says how to keep or discard the edit; other changes go ahead. A file from another generator version is generated again. No unresolved color ever reaches the built CSS.
    • The theme imports only the shades it uses, from tokens/<theme>.palette-refs.ts.
    • Colors are read as browsers read them: negative hues, out-of-range saturation and chroma, color(srgb …) and color(display-p3 …). Malformed functions, system colors and see-through colors are refused with the reason and a command that works, such as the color with its #, without quotes, opaque, or the nearest color name. A dial named another way (gray, brand, error, saturation, Accent) suggests the dial; a color dial with --on suggests what the part really reads.
    • vibrancy more at 100 and less at 0 are refused, a number out of range suggests the nearest one, undoing the last color removes vibrancy too, a vibrancy edited by hand into something invalid can be fixed with undo or set, and a replaced color shows what it was. A wide-gamut color says it is used as its nearest sRGB color.
  • astryx experimental theme editor: colors without palette commands. Colors come only from editor set <theme> accent|neutral|success|warning|danger|info <color>, which generates the light and dark shades and points the color tokens at them, as before. The new vibrancy <0-100> setting (more/less step by 10) sets how saturated the generated colors are; it needs a color and applies to the whole theme. editor new <theme> now takes any setting as a flag (--accent "[#7](https://github.com/meta/astryx/pull/7)c3aed" --font inter --corners round --vibrancy 60), checked the same way as set and applied in one build. The experimental copy experimental theme palette generate is gone; theme palette generate is unchanged, and editor set lists it as the command it replaces. Help, results and errors say "colors" and "shades" instead of palette, family and stop; show lists each color with its seed and the shade each token uses, with the generated files last (colors, colorNotes, vibrancy and colorFiles replace palette). Component families are now groups: how --list groups, and the group field in set and how results. how colors (or how palette) explains how colors are made, and plain-words color questions ("brand color", "make it more colorful", "dark mode colors", "error red", "see all shades", "exact color for one token") answer with the commands. preview add with no description adds a Colors page when the theme sets a color: every shade in light and dark with its number, hex and the tokens that use it, kept in step with each change. (#11149)
  • astryx experimental theme: make and change a theme one checked change at a time (editor), and preview it on real pages in your app (preview). Only the new experimental command group changes; astryx theme and its output stay as they were. (#11101)
    • Checked changes. editor set <theme> <thing> <value> takes a dial (corners, spacing, accent, neutral, success, warning, danger, info, font, headings, surfaces, buttons, type, text-size, base, mode), a design token, or a CSS property on a part, with --on <part|family>, --when <prop>:<value>, --state, --mode light|dark and --only. Each change is checked against what the installed Core's parts really read and against the token's type. A change that cannot take effect is refused (exit 1, an ERR_THEME_* code, nothing written), and the error leads with the command that works.
    • What parts read. It is derived from the installed Core itself, version for version: a catalog of every component renders on the server with the project's own React, joined to Core's stylesheet. The result is cached under node_modules/.cache/astryx-theme/. No new dependency.
    • An ordinary local theme. <theme>.settings.json holds the settings; <theme>.settings.ts is generated from it; <theme>.theme.ts extends it, is written once, and keeps your own edits; the CSS and JS are built by the same build as astryx theme build. A plain part setting that a more specific base-theme rule would beat is repeated on those variant keys, and the result says so.
    • Families, modes, contrast. Styling one input or check styles its whole family unless --only; --on containers and --on menus style every member. Only colors and shadows take --mode. Text this theme makes unreadable (below 4.5:1, and not that low in the base theme) is reported.
    • Editor commands. editor new, editor set, editor undo (one step back; with a thing, removes that one setting so it goes back to the base theme's value), editor show (every setting, key values, contrast problems, and two self-contained HTML pages: the sample app page and every component; PNG pictures only with --png, using a Playwright or Chrome found on the machine), and editor how (what a part reads, a family, a setting or aspect, a question in plain words answered with exact commands, a PNG picture's colors, or --list dials|tokens|parts|families|properties).
    • Preview in your app. preview add writes one route into the app's routes folder (theme-preview/ in app/ or src/app/, or --path): a normal page that keeps your layout and providers, in an app shell with a nav item per page and, when it wears a theme made by editor, a light, dark and system switch. With no description it adds the sample app page and every component; with a description it adds the page templates the build ranking picks for it (--top); --template adds one. preview list and preview remove manage the pages; only files the preview wrote are replaced or deleted, only inside its folder, and every check runs before the first write. A template page that needs a package the app lacks is skipped, with the install command. With no app, preview app <dir> writes a starter Next.js app with the preview in it (--theme copies a theme in for the pages to wear) and prints the install and dev commands.
    • Experimental copies of astryx theme. compile (the copy of theme build), list, add, remove, use, eject, template, targets and palette generate run the same functions with the same flags and JSON. Each experimental command doc names the stable command it will replace in a new replaces field, shown in its help as "Will replace: astryx theme build".
  • astryx experimental theme editor how: questions read the way people write them. (#11209)
    • Negation and "too" read the right way round: "shouldn't", "turn off", "never", "stop", "unbold", "too sharp" (rounder) and "too heavy" (lighter). "Everything except X", "but not in X" and "all but X" keep X as it is now. "Without" is read in the shipped languages, and "sans" means a typeface only before serif or font.
    • A typed value always wins. A hex beats a color word. A hex with the wrong number of digits is refused by name and never replaced with a sample. The sign, multi-value padding, % opacity, em tracking, numeric weights, written-out shadows and "40px tall" are kept. No color is picked when the question gives none.
    • "In dark mode" carries --mode dark to every color command, parts included. A change that is the same in both modes, or a dark-mode ask on a light-only theme, says so instead of changing light.
    • Better parts and properties: side nav items, focus rings as outlines, tab underlines, icons, border colors (darker, subtler, contrast), the overlay, transparent backgrounds, progress bar thickness, smaller headings, underlines, line height and body weight. A question about what something is ("what does --color-accent do") gets the lookup.
    • Typos with swapped letters and short forms (bttn, brdr) are corrected. Portuguese, Italian and Korean words for buttons and rounded are read.
    • Sequences drop repeated and overwritten steps and stop at 12. Two asks that contradict each other are offered as choices, not run in turn. Changes come before lookups.
    • Text output prints each command on its own line and never wraps one. A sequence prints as one line.
    • --theme "" and a repeated --theme are refused, for every subject. The default theme is the one an editor command changed last, not the newest settings file, and themeChosenBy says how it was picked.
    • Pictures: every pixel is read up to 4 million, so 1-pixel lines count. tRNS is honored for gray and RGB pictures. A 0x0 picture names its size. 16-bit pictures are capped at 20 million pixels.
    • Parallel lookups in an app with no themes leave no empty themes/ folder. A refusal's commands start the same way as the answer's.
  • astryx experimental theme editor how: answers that are safe, bounded and right. (#11209)
    • Every command how suggests names your theme (the only one, the one changed last, or --theme <name>; with no theme, my-theme, made first), has a real value instead of a <placeholder>, carries no shell comment, and is checked as set checks it: a command that set would refuse, or that changes nothing, is left out, and the answer says why.
    • Plain-words questions read negations and more or less ("remove shadows from cards" gives box-shadow none, "less rounded cards" gives corners less), the values you type (hex, rgb(), lengths, dashed), states (hover, focus, checked, selected, disabled, pressed, invalid), dark or light mode, several changes in one question, a few words in other languages, and small typos. A question with no answer says so in JSON too, with the next commands to try.
    • how <part> writes each condition as the --when and --state flags set takes, or says why no flag reaches it; lists every state set accepts; and says when a part has no recorded reads, with commands that still apply.
    • how <token> says when no part in the part data reads a token but Core's stylesheet does.
    • Lookups take any case, plurals and token names without dashes; --list takes the kind anywhere, singular or plural, --list=tokens and a filter that starts with --, and refuses --list given twice.
    • Pictures: a header bigger than 40 million pixels or pixel data shorter than the header says is refused at once; damaged files are refused; see-through pixels are skipped; --at gives each point's alpha and refuses points it cannot read exactly or that fall outside the picture; any file name works, and other formats are refused by their bytes.
    • set refuses a value that holds a <placeholder> or a # comment.
    • A damaged part-data cache is built again, the cache is written whole, and a lookup in an app with no themes leaves no themes/ folder.
    • Text and JSON start commands the same way, and text output escapes control characters in what you typed.
  • astryx experimental theme: data safety and value checks. (#11180)
    • A refused change puts back only the files that command wrote in that run, each whole, and only while they still hold what it wrote; a file changed by someone else meanwhile, or one it cannot restore, is left and named. The settings and undo history are written inside that rollback, and a refused new leaves no trace. A link anywhere in themes/ or the theme folder is refused, and never followed or removed. A palette.config.json the editor did not write is kept. show finds a build that does not match the settings (a command stopped mid-build, a hand edit) and builds it again, saying so. Temp files have their own editor names and are removed by the write that made them; nothing else is ever removed. Run from a subfolder, a command acts on the Astryx project above it, found as upgrade finds it: the search stops at a repository root and never takes the home folder. A package without Astryx inside that project is refused with the folder to run from, a package.json that does not parse is never walked past, and reply paths are absolute when the project is above the current folder. Yarn Plug'n'Play and a package.json without Core get their own messages. A full or read-only disk is ERR_WRITE_FAILED.
    • Commands on one theme run one after the other, so no change is lost. The lock lives in the project's node_modules/.cache (a folder that cannot be written is refused with ERR_WRITE_FAILED); a lock left by a stopped command, or by one on another computer that stopped, is taken over. A command that waits more than 30 seconds is refused with the new code ERR_THEME_BUSY, naming the lock.
    • Every name the name check accepts builds (brand-2). Names are at most 64 characters. new refuses a link or a file where the theme goes, a stray word, a flag given two values, and an empty --like; --headings takes a weight and a tracking; a refused flag suggests a new command.
    • Settings edited by hand are checked on load, and so is the step undo goes back to. A saved value the editor no longer accepts names the undo <theme> <thing> that removes it, and that command works; a step undo goes back to that holds one is passed with that value left out, and the result says so. A damaged undo step drops only itself and the steps before it. A quoted string or a data URL may hold a semicolon.
    • Token values are checked by their type: time, easing, font, shadow and outline style too, and heading weights as numbers. A value that would break the CSS, read itself, or name a placeholder such as <color> is refused. Only colors take --mode; a shadow per mode would remove it in both.
    • Code highlighting, display text sizes and colored icon tokens can be set.
    • An exact font family applies on phones too; phones keep their own reading sizes.
    • A text size or type scale keeps the base theme's ratio and the theme's heading weights (an exact weight token still feeds them), on phones too.
    • text-size takes 10 to 32 pixels. font refuses values that would not build. vibrancy is refused when every color is a gray.
    • undo <theme> <token> names the dial that still writes the token.
    • Reading a built theme writes no copy into the theme folder.
  • astryx experimental theme editor: settings that do what they say. (#11222)
    • An exact token or part property always wins over a dial, whatever the order. A changed setting moves last, so it wins over what came before it. A shorthand set after its longhands says it replaces them. A setting for both modes replaces the one-mode settings it would sit under.
    • One mode on a part whose variants each have their own value is refused, with the command that names the variant. A setting saved for a mode a one-mode theme does not have can still be removed. A base theme package that is gone no longer blocks moving off it.
    • --when must be one property and value, and on a group it must belong to a member, as --state must. An empty or repeated --on, --when, --state or --mode is refused, and so are extra words after undo and show.
    • undo <theme> <thing> <value> removes the setting only when that is its value. Scope flags without a thing are refused. undo <theme> base and undo <theme> mode set them back to their defaults. A stored setting this Core does not know can still be removed.
    • show builds the theme again when its settings were edited by hand or built by another CLI; --section writes sheet-<section>.html, not over the full sheet, and takes any case. A setting listed twice is refused.
    • spacing scales the base theme's spacing; a corners step starts from the base theme's radius or the whole-theme setting; corners pill keeps checkboxes square; headings refuses --mode; font refuses --when and --state and takes a preset in any case.
    • A change that shows nothing says so. A switch of base or mode lists the parts it restyles and the color notes. A misspelled token in var() and a typed path or capital letter for a theme get a did-you-mean. Text contrast that is not measured (one variant or state, the soft or outline button) is listed as not checked. The colors in show give each mode its own exact value.
    • The copied theme commands name experimental theme commands in their refusals. editor new and editor how no longer claim to replace stable commands their copies replace. A package.json without Core gets the install command.
    • A whole-theme token that no rendered part was seen reading is set with a note saying so, not refused. A part that reads the token the user named takes it for whatever property it feeds. A token named for another variant value (--color-error-muted with --when status:error on a banner, --color-icon-pink on an icon) is taken. A part name such as constructor is an unknown part, not a crash.
    • A font for one role keeps its font after a whole-theme font, whatever the order.
    • Easings, font family lists, light-dark() and color-mix() colors, shadows and times are checked the way the browser reads them. A shadow may use a token color, any length unit or a stacked shadow token. var() with a fallback, relative colors and system colors are taken. A time is at most 60 seconds. A font name may hold an apostrophe. var( --x ) with spaces is checked for cycles.
    • Saved exact tokens are checked on every command; one the rules no longer take names the undo that removes it.
    • A size change says that phones keep the base theme's reading sizes, and names scale steps outside 9 to 200 pixels. A refusal that suggests setting a property directly names the property that takes the value. Every suggestion set, undo and show give names the theme and a value it takes, never a placeholder.
    • The theme lock lives beside the Core the command reads, and a command outside a project takes none. When show builds again, it says why: a file missing, another CLI version, settings changed after the build, or a build that did not finish.
  • astryx experimental theme editor: theme colors now come from the palette generator. set <theme> accent <color> (and the new neutral, success, warning, danger and info dials) writes the color as a family in themes/<theme>/palette.config.json, in the shape theme palette generate reads, and runs the same generator to write tokens/<theme>.palette.ts and its receipt. The theme's color tokens point at stops of that palette, light and dark from one color, following the stops the official themes use. A token moves to a nearer stop of the same family when it must read (text at 4.5:1, the focus ring at 3:1); the editor no longer mixes colors of its own. show reports the palette, which stop feeds each token, and the contrast behind each choice; how palette explains it; undo <theme> accent removes the family and its tokens. An exact token (set <theme> --color-accent <color>) still wins over the palette. Color dials apply to the whole theme: --on and --mode are refused, with the exact-token command to use instead. (#11134)
  • experimental theme preview add checks the theme before it writes any page, and skips a StyleX template page in an app with no StyleX compiler (the result says why). experimental theme preview app checks the folder before it builds a --theme, so a refusal writes nothing. (#11134)
  • astryx experimental theme preview: the preview pages work in a production build. Leaving the Components page no longer crashes the route: a typeahead part (Tokenizer, CommandPalette) gets a small sample search source. On the Components page, a part renders inside the parent its playground names (Step in a Stepper, a SegmentedControlItem in a SegmentedControl, a RadioListItem in a RadioList), a part that only works deeper inside its parent is left out, a status variant is passed as {type}, ButtonGroup shows three buttons, and layers that stay closed are left out. A component that still throws shows a short note instead of a blank cell. The Overview page is the sample page's content, without a second app shell. Font: editor set <theme> font <name> and editor show say near the top when the font's package is not installed, with the exact install line; once it is installed, the next set or show makes the preview route import its stylesheet. (#11134)
  • astryx experimental theme preview: safer refusals and recovery. (#11209)
    • No refusal suggests deleting or moving files: a damaged theme-preview.json, a page changed by hand, or a file in the way gets plain instructions instead.
    • --path at the project root, in src/ or at the routes folder itself is refused: those folders hold the app. An older preview found there is named, with the remove that clears it.
    • A whole remove stops, deleting nothing, when page.tsx was changed by hand, since it imports the pages.
    • A formatter run no longer counts as a change by hand. editor set and show name the preview files they left as they were (previewStale).
    • A recorded page whose file is gone is written again, or left out of the nav, so the route always builds. Moved pages get a hash. A failed write leaves no temp file or empty folder, and says which step failed. A read-only file keeps its mode.
    • preview app --theme waits for other commands changing that theme, and its retry suggestion keeps --theme.
  • astryx experimental theme preview: safer adds, removes and starter apps. (#11209)
    • Preview pages go in _pages/, a folder Next never routes, so a preview at the project root or in src/ no longer turns on the Pages Router. A preview an older release wrote into pages/ is moved on the next add or remove.
    • A refusal deletes nothing: remove <page> loads the theme before it deletes a file, and names the whole-preview remove when the theme does not load. A theme that is gone is replaced by the app's own theme, with a note.
    • Only files the preview wrote are replaced or deleted, and never one changed by hand since (theme-preview.json records a hash of each). remove names the files it kept, the ones already gone, and the ones it wrote again.
    • Files are staged and renamed into place together; a failed write puts every file back and is refused with ERR_WRITE_FAILED.
    • A damaged theme-preview.json is refused with ERR_THEME_INVALID, naming the file and the way out, in add, list and remove.
    • --path is refused when it is a file, in themes/, node_modules/ or a Pages Router folder, in a folder Next does not route, or written with Windows separators, ~ or white space at either end. The open line drops route groups and encodes each folder name.
    • Without --path, list and remove find a preview recorded for a theme.
    • add: an empty --template is refused; a block passed to --template says it is not a page and suggests page templates as commands; --top is taken as typed and only with a description; a description may be several words without quotes, and only its first 40 different words are ranked; a package that is named but not installed counts as missing; a changed theme writes the default pages again; a page file an interrupted run left behind with the same text is taken over.
    • Suggested commands are shell-safe, and a wrong --theme names the closest editor theme.
    • list, remove and preview app refuse extra arguments.
    • preview app: the app is written into a temp folder and moved into place, so a failure leaves nothing; folders inside the routes, themes/ or node_modules/, files, dangling links and odd names are refused; a folder with only .git counts as empty; every open font the theme names is added with a pinned range; the Colors page is included; a one-mode theme starts in its mode; a stale theme build is rebuilt first; the home page links to the preview, the .gitignore covers node_modules, and the open line is quoted.
  • astryx experimental theme editor how --list is now a switch, as --list is everywhere else in the CLI: the first word says what to list and any words after it filter the list (how --list tokens accent), and --list alone lists the kinds. Reading a built theme no longer writes a temporary file into themes/<theme>/; it uses the project's cache folder. (#11173)
  • astryx experimental theme: fixes from a third theming round. preview add "<description>" adds the closest page when no page is exactly the one described, and matched says which words of the description it covers; only a description no page relates to is refused, and its suggestions repeat --theme and --path. A page the app cannot show is skipped and the next match is taken, from the ranking and then the template search. A page's nav label is its template's name, however it was added. The accent and status fills keep your exact color in dark mode too when text on them reads at 4.5:1; otherwise dark mode uses the nearest shade that reads, and the result says why. Setting vibrancy names the status colors the theme does not set, which keep the base theme's colors (and so do info-tinted surfaces such as colored cards), with the commands that bring them in. new lists the mode it applied with the other settings. show prints your exact value where an exact token setting wins, and sizes, numbers and fonts once instead of per mode. Notes name a part inside the part a token is set on ("button inside toast"). A token no part reads says it changes nothing you see now. how names the resting border (border … --when variant:secondary), answers a part's fill and text together ("light gray button with dark text"), and answers a status background ("the error background") with the status color. The Overview page's tabs and other controlled samples no longer throw when clicked, and its open popover and tooltip keep clear of each other at narrow widths too. (#11163)
  • astryx experimental theme: fixes from a fourth theming round. preview add "<description>" adds an app page when the description names one (an issue tracker, a board, a dashboard, an app screenshot) instead of a hero, takes the side hero for a left-aligned or split hero, says that no page has a top nav of its own, and always says why it picked a page. A base preview add says which pages were there already and are written again (refreshed). how gives each token a value of its own type (--color-border "<color>", --border-width 1px; only the border property takes a whole border), keeps the fill for a named tint ("light blue tint with blue text"), and no longer reads "border color" as a fill. undo <theme> <thing> names the setting it removed (removed) instead of printing it as the value in effect. A light-only or dark-only theme lists only its own mode's shades and notes. show lists corners or spacing set on a part or group, with what its parts get beside the whole-theme value (partValues). neutral names the base theme's page background and the command for a white page. type says what it still sets when headings sets weight or tracking; type and text-size keep each other's part of the scale in any order. A token no part reads says which tokens are built from it instead of claiming it changes nothing. An installed font says it is installed. A color's text switching between white and near-black says why. (#11165)
  • astryx experimental theme: an accent or status fill keeps your exact color in dark mode only when it also stands out from the dark page (3:1) besides text reading on it; otherwise dark mode uses the nearest shade that does both, and the result says why. The preview's Colors page marks such a fill under the shade it really uses, for dark mode too. Suggestions from preview add quote the options they repeat, such as a --path with a space. (#11165)
  • astryx experimental theme: preview add "<description>" picks an app page only when the description names the app in a phrase (an issue tracker, an issue detail, a kanban board), so a page with a "buy tickets" button or a landing page for an AI tool no longer gets an app page; a detail view comes before its list, and the ranked page stays first when it already is that app. how keeps the fill when a color word belongs to it ("a dark card with a thin border", "colored buttons with a border"). show names the radius token each part's corners really read. The neutral note offers a white page only in a theme with a light mode. When your exact accent or status color cannot be the dark fill, dark mode uses the shade nearest your color where text reads at 4.5:1 and the fill stands out from the dark page at 3:1. undo <theme> <thing> prints setting and removed as its JSON does. (#11168)
  • astryx experimental theme: fixes from a full review. (#11173)
    • preview app --theme copies the whole theme folder, generated colors included, byte for byte, so the new app type-checks.
    • preview app <dir> writes only into a new or empty folder (its --overwrite option is gone): a folder that is not empty is refused, with a free folder name to use.
    • Translucent text and backgrounds are measured as drawn: each is laid over what is under it before contrast is checked.
    • Two commands can run at once: each render uses a folder of its own.
    • A change that is saved but cannot be checked says "saved, not checked" and exits 0.
    • A light-only or dark-only theme applies only its own mode's settings and names the others, writes one value for the colors it sets, and its in-app preview starts in that mode with no switch.
    • A damaged undo history no longer breaks set (a new history starts, with a note), and undo says how to fix it.
    • Colors are picked against the theme's own exact page and surface colors.
    • A change that changes nothing builds nothing and adds no undo step.
    • undo <theme> <thing> says what applies now (now).
    • show names the radius token each part reads, or says it is unknown.
    • how answers border-only questions without a fill.
    • The preview picker matches app and article pages by phrase: a news story or blog post gets an article page, never a record page; a description no page relates to (no phrase, and fewer than three words or two fifths of them matched) is refused.
    • A preview outside the routes folder says the app does not serve it.
    • More than eight contrast problems end with "and N more".
  • astryx experimental theme editor show: the text output prints the palette paths and contrast notes whole instead of one character per line, and keeps one line for each token a palette family feeds. (#11149)
  • astryx experimental theme: fixes from a real theming round. headings now keeps heading weight and letter spacing whatever order it and type are set in; type says what it no longer sets, and show marks a setting another one partly hides. A steep type scale (editorial, display) keeps text below the base size at its standard sizes, so small text stays readable. show lists every setting with its whole scope (--on, --when, --state, --mode). A gray color (accent [#171717](https://github.com/meta/astryx/pull/171717)) makes gray shades in light and dark instead of inventing a hue. neutral no longer tints the page background (--color-background-body stays the base theme's). set accepts every token a color, type, headings, corners, spacing or text-size writes, so a dial's notes never name a token set refuses. When the components cannot be rendered (two copies of React, say), new, set and undo save the change and say "saved, not checked" with the cause and the code ERR_THEME_NOT_CHECKED, instead of failing after writing; how says what it could not check instead of listing no readers. A font that is not installed names the closest font that needs no install. how answers each aspect once, turns sizes in the question into --when size:…, takes each color from the word it belongs to, says when text takes the page's text color, and how --list with no kind lists the kinds. preview add "<description>" says what it matched and why, leaves app frames out, refuses with the closest pages to name when no page really matches, and takes the next match when a page cannot be shown here. The preview fills the whole window with the theme, shell and edges included; the Overview page now shows what themes most often break, and each cell of the Components page names the command that changes it most. show --group is now show --section: it picks a section of the theme-building sheet, so "group" only means a group of parts (--on inputs). (#11149)
  • Icon sets: authoring a set is easier. An author sees which icon meanings the bundled templates use that the set does not map yet, such as document and share; a copied template shows a placeholder for each. Only the experimental icon commands, the icon-set lists in integration check and Doctor, two icon definitions' search words, and the icon-set guide change. (#11090)
    • Authoring receipts. experimental icon new-set, add, and map end with one line when the set leaves template meanings unmapped: how many there are, the most used first with their template counts, and the map command to run. The JSON adds templateMeanings: {unmapped: [{definition, templates}]}. A dry run adds nothing.
    • experimental icon --definitions. Each definition shows how many bundled templates use it (templates) and whether the set maps it (mapped). The set is the one --set names, else the project's main set, else the only set of the icon-set package you run it in. --set is now accepted with --definitions.
    • integration check. Each set's iconSets entry adds templateMeanings, printed under "Template icon meanings not mapped". It is never counted and never fails a check, even with --strict.
    • new-set --adapter ./<path>#<export>. Declares the adapter a library of icon data objects or SVG strings needs, so the set wraps it with no hand edit to the data file.
    • Clearer receipts. The first new-set --from into a set with no icons says the set was created, not refreshed. add --variant <look> --all names the first ten icons the module lacks and how many more; the JSON still lists every one. The command that adds unlisted sets as backups (from icon use and Doctor) names every set the same way: by its name, or as <package>/<set> when two packages ship that name.
    • Better suggestions. A suggested icon whose id only starts with the definition's name and adds another thing (delete-left, a backspace key) comes after the icons the definition's words name (trash), and a word two definitions share (store) comes after the words only one has. save adds the word "floppy disk", and bank reads "building library" instead of "library".
  • Icon sets: copied templates draw the right icons in more sets, once a set maps the five new icon definitions. Only the experimental icon-set rewrite of astryx template, five new icon definitions, the bundled templates' icons declarations, and the icon-set guide change. (#11142)
    • Distinct icons keep distinct meanings. Some bundled templates gave two different icons one meaning, so both drew the same icon in every set. The Settings Dialog's "Keyboard shortcuts" and "Developer" rows, and its paintbrush and swatch, now draw different icons, and so do the icon pairs in Table Filter, Theme Showcase, and the Button Group showcase block. New icon definitions: keyboard, paintBrush, documentSearch, bookmarkAdd, and wallet. No set released before this change maps them, so with such a set the Settings Dialog's "Keyboard shortcuts", "Color theme" and "Verbose logging" rows, Table Filter's save-view button, and Theme Showcase's wallet draw the placeholder. A set draws these icons once it maps the new definitions (astryx experimental icon map <definition> <icon> --set <main>); until then each draws the placeholder, unless a set in your list wraps the template's library.
    • An icon from a set's own library stays. When a set in your list wraps the library a template imports an icon from, the icon is one your project chose. With the main set's own library, the icon keeps its import as written. With a backup set's library, an icon that no set maps keeps its import instead of becoming a placeholder. The report lists each one under kept with the reason.
New Features
  • Open a sign-in dialog from the theme showcase's Sign in button, which was an inert link, so a theme's dialog header, close control, fields and footer buttons can be reviewed together. (#11130)
Fixes
  • astryx component <ExampleName>, given an example block, still fails with ERR_UNKNOWN_COMPONENT and the same name suggestions, but its message now says the name is an example block, that astryx template <ExampleName> prints its source, and which astryx component <Parent> --blocks lists it. (#11153)
  • astryx search no longer counts a component or hook keyword that is another entry's name as a match for that entry, so spinner lists Spinner without NumberInput beside it. A keyword still counts when the entry's own description uses the word, or when it names the entry's own family member or its hook. build reads keywords as before. (#11162)
  • astryx template and astryx build read a template's needs from its real imports only. Words in comments, strings and JSX text no longer count as packages, so templates such as form-wizard, form-wizard-vertical and table-tree no longer ask you to install Next, Distribution or canvas-editor. A path alias such as ~/lib or #internal, or a name npm does not accept, is not reported as a package to install. (#11224)
  • Template placeholder images follow dark mode. The placeholder a copied template page shows in place of its demo pictures is now a soft gray at low opacity that takes its tone from the surface behind it, so it no longer shows as a bright light-gray block in a dark theme. The gallery-hero, side-gallery and lightbox gallery examples no longer warn about duplicate keys when every picture is the placeholder. (#11150)
  • Theme commands no longer replace files they do not own, and they report the right errors. theme template --overwrite replaces only an earlier copy of the template or a theme source file, and refuses folders, blank paths and paths that are not .ts. theme eject --overwrite never writes into another theme's folder or a theme the theme editor made, and the result names the packages the fork needs (missingPackages, installCommand). theme build --out <folder> writes <name>.css into the folder; a build never replaces its source, or a file at a path --out names that it did not write, and two themes with one name in one run are refused (a header-less output of a CLI before 0.6.7 at the default paths, family outputs included, is still replaced). When --out names a file that a CLI before 0.6.7 wrote, the build says so: delete that file and run the same build again. Two theme add, use or remove commands at once keep both changes. A theme whose local folder or package is gone no longer blocks use, add or remove of other themes; it is left out with a note; one broken local theme folder no longer hides every other theme from list and add. add says which owner it chose when a local theme shadows a package theme. An option without its value is ERR_MISSING_ARGUMENT with the command's usage, and astryx help <group> <command> prints that command's help. (#11210)
  • The theme showcase's Sign in dialog opens empty each time, not with what was typed before a Cancel. (#11139)
Performance
  • The CLI turns on Node's compile cache, so a run skips most of compiling the CLI's modules again. The cache sits in the user's own folder in the system temp folder (node-compile-cache-<uid>), used only once it exists (the first run on a machine just makes the folder, so a one-off run pays nothing for it) and only while it is a real folder the user owns and no one else can reach. Where the system has no user ids (Windows), that cannot be checked, so the cache stays off. NODE_DISABLE_COMPILE_CACHE=1 turns it off. A cache that cannot be read or written is skipped without a word, and every command prints the same output. (#11217)
  • astryx --help, -h and help print the root help from a command list stored in the package when it is published, instead of loading every command first. The list holds the terms and descriptions the fully loaded CLI prints, so while every command loads the help reads the same. A command whose module fails to load is listed in the published root help under its normal description, instead of being marked as failed; running that command still reports the failure. (#11194)
  • Commands that read the docs Astryx ships (search, build, docs, template) read each shipped doc that holds only plain data from a copy of its exports stored in the package when it is published, instead of importing the file. The copy is keyed by the file's text, so an edited doc, a doc that imports or calls anything as it loads, and every integration's docs are imported as before. Every command prints the same output. (#11191)
  • search and build read the components of a template Astryx ships from a list stored in the package when it is published, instead of parsing the template's source on every call; template does too when it leaves a template's demo content unchanged. The list holds exactly what parsing returns, keyed by the source text, so a changed source or an integration's template is parsed as before. Every command prints the same output. (#11190)
  • A process that calls themeTargets() more than once scans Core's component docs once. It reuses that scan while every folder and doc it read is unchanged, as the docs and search catalogs do. A Core reached through a symlink, as a project's node_modules reaches it, shares the scan of its real path. A one-shot astryx theme targets and the theme build's target check still scan once. Every command reports the same targets. (#10981)
Documentation
  • AppShell's guidance on naming its navigation landmarks now says to pass label to TopNav and aria-label to SideNav. SideNav has no label prop; it has a translated default name, and aria-label renames it. (#11151)
  • The calendars guide names every calendar by its CLDR name, such as Minguo, Dangi, Hijri, and Ethiopic, with its identifier beside it. (#11102)
  • The token tables in astryx docs say that their values are Core's defaults, which a theme replaces: the columns read "Core default", "Core default (light)" and "Core default (dark)". The Color topic also says that each theme defines its own values and that astryx theme list shows the themes that are available. (#11089)
  • Add hook documentation and interactive table cell truncation example block for useTruncation, demonstrating responsive string truncation and accessibility tooltips. (#10555)
  • InternationalizationProvider shows its examples in reading order: load a shipped locale, mirror the layout for right-to-left text (a new code example), override one string, then the calendar examples. Each live example is titled after its code example, so the two lists match. (#11094)
Other Changes
  • Internal: the module loader imports a user module through the same small module the doc importers use, which the CLI's own test project loads natively, so a theme build's doc reads no longer time out its tests on a busy machine. No change to any command's output. (#11119)
Contributors
Thanks to everyone who contributed to this release:

0.7.13

Experimental APIs
  • astryx discover lists the experimental TabBarMoreList component from @astryxdesign/lab. (#10619)
  • Icon sets: a project picks one main icon set and backup sets in order, and an icon no set has becomes a placeholder in the copied file. Only the experimental icon commands, projects that set experimental.iconSet, templates that declare icons, and the icon-set guide change. (#10959)
    • Main set and backups. astryx experimental icon use <main> --backup <set> (repeatable, order kept) writes experimental.iconSet as a list, the main set first; with no --backup it writes the plain string as before. The receipt adds backups, the installed sets the list leaves out (unlisted), and the command that adds them (next). experimental icon --list shows the order and each set's role and rank, and, when two or more sets are installed and none is the main set, the command to run. A CLI before 0.7.12 refuses the list form, and use warns when the project's CLI range admits one.
    • Copied templates follow the list. astryx template takes each icon from the first set in the list that has its meaning, never mixing sets within one icon, and reports the set used, a missing look (variant: {asked, used}), and each set used with its license (icons.sets).
    • No stray library imports. An icon no set in the list loses the template's original import. The copied file declares a small MissingIcon component once (a dashed square, 1em, in the current text color, hidden from screen readers unless a use gives it a label), and each place the icon was renders it, with a comment naming the meaning. It needs no new package. The output prints a note naming the meaning and both fixes (map it in the main set, or add a backup set), and the JSON lists it in icons.placeholder.
    • Doctor. With the opt-in, the icon-sets check fails when the list names a set that is not installed, withdrawn, or shipped by two packages, and when more than one set is installed and the list leaves one out. A new icon-placeholders check warns while copied code still uses the placeholder, naming each file and meaning; a commented-out or quoted copy does not count. Projects that have not opted in see no change.
    • Labeled template icons. Every icon a bundled template uses now declares its meaning, with 30 new icon definitions. integration check notes an icon a template imports but does not declare (template_icon_undeclared), in a package whose templates declare icons: an import from a module the package declares icons from, which the template renders as an element with no children or passes as a value. Any other import from that module, such as a type, a function it calls, or a provider with children, is listed as not checked. The note fails --strict --next and leaves --strict as it was. A generic renderer (a bare Icon, or one every use gives an icon prop) and an import that matches an icon by its name only are listed as not checked instead.
New Features
  • The CLI adds a BaseTypeaheadMenu block: a BaseTypeahead whose listbox menu shows information around the result list, and whose pick or filter button opens a dialog-role menu on the same layer. (#10625)
Fixes
  • dependency floors move to current releases: the build package needs autoprefixer 10.6.2, browserslist 4.29.5 and lightningcss 1.33.0; the CLI needs ignore 7.0.14, jscodeshift 17.4.0, linkedom 0.18.15, zod 4.6.7 and @stylexjs/babel-plugin 0.19.1; each theme needs lucide-react 1.66.0. Peer ranges do not change. (#10709)
Documentation
  • Add hook documentation and interactive sparkline example block for useDirection, detailing render-time direction handling and CSS logical properties best practices. (#10547)
  • InternationalizationProvider has a calendar example: the provider's calendar prop shows a Calendar and a DateInput in the Japanese or Buddhist calendar, and the value stays a Gregorian ISO date. Both calendars work without Temporal. (#10135)
Contributors
Thanks to everyone who contributed to this release:

0.7.12

Experimental APIs
  • discover lists the Lab ChatVirtualizer among the official @astryxdesign/lab components. (#5461)
  • astryx discover lists the experimental TabBar and TabBarItem components from @astryxdesign/lab. (#9700)
  • integration check and experimental icon new-set follow export const X = Y to where Y is declared: an icon-set theme map or icon export written that way is now checked and recorded. (#10471)
  • Icon sets: when a wrapped library ships no license file, integration check on an icon set, experimental icon new-set --from, and a refresh name the NOTICE file to add and where, and the icon-sets guide lists the file names that count. A refresh from a library root moves icons added one file at a time from that library to the root import, keeping their ids, exports, map entries, variants, and words, and the receipt lists them under moved. Each keeps that id and export on every later refresh, and refreshing again changes nothing. A refresh keeps an id you chose that is not a spelling of the library name (dismiss for XIcon), also for an icon that already reads the root; it renames only an id the current rule spells differently. A library icon whose id or name a moved icon already has is left out. An icon whose root export another icon of the set already reads stays on its own import, and the receipt says why. A variant from another file of the package, such as a solid look, stays on its own import, and every export the refresh does not write again stays in the generated module. A LICENSE directory counts as a license notice in neither the receipt nor the check. (#10458)
  • Icon sets: wrapping a large icon library that names its looks in its exports works in seconds and gives one icon per glyph. Only the experimental icon commands, the icon-set guide, and integration check on an icon set change. (#8013)
    • Large libraries. experimental icon new-set --from reads a library of 20,000 exports in about ten seconds instead of minutes, and in text mode says on stderr that it is reading and what it found. iconNewSet and iconAdd report reading progress for large modules through the shared logger (stderr, text mode only); called directly, they stay silent until logger.setSilent(false).
    • Libraries of looks. A library whose export names end in style, size and weight words (XOutline24WGHT500Icon), never direction words like Up and Down, gives one icon per glyph, named x (XIcon), in the look the set's default variant names, else the library's usual default; suggestions and add name icons by glyph, add --variant filled --all picks each glyph's filled look, a refresh keeps every icon an earlier release wrapped, and a refresh with a new --default-variant moves each glyph to that look. Every command that records the default variant takes it from the look each icon's export draws, refuses a look word the library does not have, and never adds a second export of an icon.
    • Variants on an existing set. experimental icon new-set <set> --variants outline,filled without --from declares variants (a set with icons keeps its default variant, or, with none declared, takes the look its icons draw; a set whose library's export names name no looks keeps it on a refresh too, refuses --variants that leave it out, and the refusal names the add --variant run that adds the other look), and --display-name and --description rewrite the descriptor, in place; add --variant names an undeclared variant with that command.
    • Commands that run as printed. Every command new-set, add and map print names the set, with --set where the command takes it; the commands add lists repeat --default and --id; --new-definition and new-definition take kebab-case as the definitions list shows it, and an unknown --definition suggests a name the next command takes.
    • Search. experimental icon star no longer offers start, a plural matches its singular, go home finds the icon mapped to home, and a letter or two never matches inside a word.
    • Checks. A set's own definitions pass integration check --strict, and the generated module and its declaration file pass after a formatter rewrites them.
    • Theme icons. Each themeIcons entry is sized to its box by CSS, so a component that writes its own size attributes still fills the theme's icon box.
  • astryx experimental render matches compilerOptions.paths keys and targets by TypeScript's rules, from the project's own tsconfig.json or jsconfig.json (a config it extends is not read). Newly, a * may sit anywhere in a key or a target ("theme-*-x", "./icons/icon-*"), and a key's targets are tried in order, so a module, stylesheet, image or JSON file under a later target is found; --reverse puts a file back under the target its sent path names (the one whose folders match the most of the path above the file, a target with text before its * included), else under the first target. Only bare specifiers are matched, an import whose targets do not exist resolves as a package, and a catch-all "*" key never turns a missing package into a path error. A module the page loads from outside its own files and outside node_modules (a sibling package's source, say) resolves a bare import through the same aliases first, as the page's own files and TypeScript do, so the page and that module load one copy of a package; an import no alias places resolves as a package, so an installed package that a prefix key also names ("@scope/*" and @scope/realpkg) still loads. --reverse of a rendered file that lost its embedded source on the way (and has no Astryx components to rebuild from) now fails with ERR_RENDER_SOURCE_DAMAGED, saying so, instead of ERR_RENDER_NOT_ASTRYX. (#8012)
  • Icon sets: an icon whose name would start with a digit once the library prefix comes off, such as a library's fa0, now keeps that prefix: it gets id fa-0 and is exported as Fa0Icon (fa500px becomes Fa500pxIcon). The CLI wrote 0Icon before, which is not a valid JavaScript name, so the generated module did not parse. An id you give that starts with a digit, with no prefix to keep, is refused with a message that asks for an id that starts with a letter. Only experimental icon new-set --from and experimental icon add change; a set they write now passes integration check. (#10895)
  • Icon sets: experimental icon add --variant <look> --from <module> --all now works for a library that ships each look as its own package, such as Font Awesome's solid and regular packages of icon data objects. Before, it found no icon to give the variant, because every icon came from another package. An icon gains the variant from the export of the same name and kind, and the receipt lists as missing the icons of that library that the look's package does not export. Wrapping such a library also no longer turns a pack export (fas, an object of the other exports) into an icon, so the shared fa prefix comes off the names again. A name that would then start with a digit keeps the prefix (fa0 becomes Fa0Icon), so the generated module still parses. Only the experimental icon commands and integration check on an icon set change. (#10896)
  • Icon sets: after you rename an icon-set package in package.json, the next experimental icon command that writes the data file (new-set on the existing set, with or without --from, add, map, or new-definition --icon, even one that changes nothing else) writes the new package name to the data file's module, and keeps any subpath (@acme/old-icons/outline becomes @acme/new-icons/outline). Before, the old name stayed, and integration check failed until you edited the file by hand. The receipt of each of these commands names the new and the old module (Updated module to "@acme/new-icons/outline" (was "@acme/old-icons/outline"), from the package name in package.json.), and map words each map entry from what it replaced, so an entry that did not change says so. Only the experimental icon commands and the icon-sets guide change. (#10897)
  • astryx experimental render draws recharts charts. A recharts chart draws only after its effects run, and a ResponsiveContainer measures its parent in a browser, so a rendered page showed an empty box for every chart. The render now draws each chart and ResponsiveContainer a page imports from recharts by name, after the server render, in a small document with no layout. A container starts at its own width and height, or at a width that follows its height, and the drawing scales to the width the page gives it. The chart-size warning counts the charts the render could not draw, and says when charts were drawn by themselves (when the page cannot be drawn again without a browser, or its effects change its charts or re-render the component that makes them). Charts show the data and props of the page's first render; a value a chart's parts read from a React context that an effect changes may show its later value. (#10382)
  • exportSearchIndex() and rankSearchIndex() from @astryxdesign/cli/api store and rank search's candidates. exportSearchIndex({cwd, package}) returns {version, candidates}: what search() ranks in a folder, as plain JSON (with package, only that package's entries). rankSearchIndex(query, indexes, {type, limit}) ranks stored indexes with search's own tree: an index made in a project answers as search(query) does there, with the same response; for an index made outside a project, theme results name theme add where search there names theme eject. A catalog that lists packages it must not load makes the index where loading is safe and ranks it per query. An index is ranked only by the CLI version that made it. Both are experimental (they may change in a patch release), and their docs are not search results, so search and build answer exactly as before. When they are promoted to stable, their docs join search. (#10375)
New Features
  • astryx discover lists the Lab DialogHeroHeaderShowcase template from @astryxdesign/lab. (#10109)
  • astryx discover lists the Lab DialogHeroHeader component from @astryxdesign/lab. (#10108)
  • BottomSheet: at rest, a sheet's content starts below the grab bar whatever its padding, so the first line is no longer drawn through the bar's fade. The block-start inset is never less than the bar's height (--spacing-6): the band under the bar is not padding a child escapes, so a lone Section starts below the bar too; scrolled content still passes beneath it. A sheet at the default padding starts its content 8 px lower, one with padding={0} starts it below the bar, and one whose only child is a Section starts that Section 24 px lower and grows by the same amount. Core's own padding={0} sheets (the touch date and time pickers, the DropdownMenu and ContextMenu sheets, and the PowerSearch and Tokenizer sheets) no longer reserve that band themselves, so the pickers, PowerSearch and Tokenizer look the same and a menu's first row sits 8 px lower. The CLI's table-filter and table-inbox page templates drop their own band too, so it is not doubled. (#8558)
  • ChatLayout keeps its composer on top of the software keyboard where the visual viewport shrinks for it, instead of leaving it underneath until the browser scrolls the whole page. In Chrome on Android the dock rides Gboard's measured slides up and down, in step with the keyboard. In Safari on iOS (in the browser and as a home-screen app) and in Firefox for Android, it moves above the keyboard once the browser reports it. Where a page sets interactive-widget=resizes-content, Chrome shrinks the page for the keyboard itself and the composer stays above it without moving. A conversation at its newest message stays there, and the rest of the transcript can still be scrolled above the composer. On a touch screen, in a top-level page, every way into the composer's text (a tap, the keyboard's previous and next buttons, Tab, the input's focus()) reaches it without the page scrolling; under a mouse or inside an iframe the browser's own focus applies. In a top-level page on a touch screen, the composer's wrapper (without the scroll-to-bottom button) is a group with no name. When the keyboard's Done ends typing, focus rests there (it is no tab stop), so the next tap or Tab starts from the composer; it shows the focus ring after keyboard input only. A tap that focuses the composer still raises its click once. Under a mouse or inside an iframe, the wrapper is a plain container. Under Reduce Motion the composer never travels with Gboard: it cross-fades to its place above the keyboard. Under a mouse, with no software keyboard, nothing changes. The browser-support guide's section on the on-screen keyboard covers ChatLayout's composer. (#8176)
  • astryx lists a create… factory documented as a hook, such as createReorderable, with the hooks. (#8139)
  • astryx docs also opens a docs-tree node by its bare name, or by a route that drops the prefix its name repeats, when exactly one node matches: astryx docs tokens-color and astryx docs tokens/color both open tokens/tokens-color. Two or more nodes answering one name still fail with the suggestions they always listed, and an experimental doc still opens only by its marked route. (#10387)
  • astryx docs --depth <levels> now names the docs below each namespace on the topic list, by the route that opens them, so one read learns every route instead of one read per namespace. Without --depth the list is unchanged, and the JSON keeps its shape: the new children sit inside each meta.namespaces entry. (#10393)
  • The official-packages discovery list now includes the Lab LineClamp component, so astryx can find and describe it. (#4259)
  • Tables can window fixed-height flat data: pass useTableRowsVirtualization({rowHeight, initialViewportHeight}) to Table.virtualization. Table keeps the complete data and row identity, mounts only the rows in its viewport plus a few overscan rows, keeps native table semantics with full-table row positions, keeps the focused row mounted, and falls back to rendering every row for content or geometry it cannot window. Tables that do not opt in are unchanged. (#8280)
  • Table plugins can now read where a row sits. Table passes each body row and cell transform an immutable TableRowContext (the row's key, its zero-based logicalIndex in the complete data, the row and header counts, and the row model). It passes the scroll-wrapper transform a TableRenderContext with a stable viewport reference. A plugin declares rowModel: 'flat' when its body transforms keep one row per data item. useTableSelection and useTableStickyColumns declare it. useTableRowIndex() without options now numbers rows from the context (passing data still numbers from that array), and rows that move re-render only for plugins that read the index. Read context values during the transform; a later read from a callback warns in development. The CLI's numbered-rows block no longer passes data. (#10171)
  • Replace the theme showcase's custom layout, text and icon styling with Astryx components. The embedded preview paints the theme's body behind card-token surfaces instead of a surface-colored card band. The new standalone top-navigation shell uses the theme's surface canvas; the embedded view stays shell-free. Make demo inputs, cart feedback, inventory filters and chat respond locally, with clearable filters and no payment submission. Keep the template id, gallery visibility and demo content. (#10404)
Fixes
  • On Android, text follows the reader's system font scale in every theme with no setup, in browsers that report env(preferred-text-scale) (verified on Chromium and on Chrome stable). The root Theme reads env(preferred-text-scale) and scales every font size by it, as it already follows Dynamic Type on iPhone. Before, the system font scale reached Astryx text only when the page added <meta name="text-scale" content="scale">. A page with content="scale" keeps working as it did: its root font size carries the scale, and the root Theme adds none. Browsers without either see no change. astryx docs typography/type-scale describes it. (#10727)
  • Comments, a codemod note and the grouped-table template's sample data no longer use internal-format identifiers. (#10958)
  • astryx swizzle --list no longer lists Core's shared folders (animator, gestures, i18n, internal, keyboard, motion, privateAttributes, __tests__) as components. A copy of gestures imports @astryxdesign/core/motion, which the core package does not export. (#10185)
  • astryx component prints a theme warning as one line: control and format characters in the configured astryx.theme value or the generated theme record print as �, so a newline or an escape sequence in a checkout cannot rewrite the terminal. (#10764)
  • astryx docs <topic> reads a topic authored as .doc.ts from an installed integration on every supported Node, and from a linked integration below Node 22.18. Topic and docs-tree files now load .ts through the same TypeScript loader as component docs, where a plain import failed under node_modules ("Stripping types is currently unsupported") and below Node 22.18 ("Unknown file extension .ts"). astryx search also reads an installed .doc.ts component doc, so it finds the component by its keywords, shows its description, and lists a family's members. .doc.mjs topics load as before. (#10763)
  • A long-running process that calls the CLI's API, such as a docs site's search route, now reads an edited CommonJS .doc.js file again in docs, search and template reads. It read the doc as first loaded. (#10760)
  • A command that reads a project module again after changing it, such as astryx integration add checking the manifest it just wrote, now reads the change for an ES module .js file in a package without a "type" field. It read the module as first loaded. (#10745)
  • Gothic: accent text and accent icons stay readable on a light media surface. They used Gothic's light accent there, near-white on a light band (1.14:1); now they follow the surface's dark accent (18.7:1 against a white surface). The CLI's Gothic theme template carries the same change. (#10852)
  • Icon sets: integration check now accepts a generated declaration file (*.generated.d.ts) whose long type arguments a formatter such as Prettier re-wrapped. Before, the re-wrapped line made the check report icon_generated_types_mismatch and fail. A changed declaration still fails the check. The experimental icon commands are unchanged. (#10898)
  • Neutral: an unselected SegmentedControl label meets 4.5:1 in dark mode on AppShell's surface. The track is translucent, so it lightens the surface under the label: [#9](https://github.com/meta/astryx/pull/9)e9e9e on [#3](https://github.com/meta/astryx/pull/3)c3c3c measured 4.11:1. The label now takes neutral.dark[80] (6.46:1), the same lift Neutral already gives secondary text on its selected rows and pills. Light mode is unchanged, and the CLI's Neutral theme template matches. (#10881)
  • astryx build: when an idea names a family only after its head ("a saml for a login") and the family's base template matches no other word, the variant that outranks the base now stays the start (login-sso, not login), so adding page templates no longer flips such ideas to the base. Ideas that name the family in their head ("saml login") start as before. (#10431)
  • astryx experimental render no longer dies silently with exit 139 when Node itself crashes while it renders a page. The page now renders in a separate process, so a crash (a crash signal, or a crash status on Windows) ends only that process, and the render fails with ERR_RENDER_FAILED and a message that names the Node version and path; a signal that stops it names them too. That process ends when the CLI ends, so a page that never finishes does not outlive a stopped CLI. Some Node builds crash in Intl.Segmenter, which components such as Avatar use to split text: on such a build the render runs the page once more without Intl.Segmenter and adds a node-crash warning that names the Node build and says the output may differ slightly (a joined emoji, a flag, or a letter with a separate accent mark in initials), so pages with Avatar render again. (#10915)
  • astryx search puts the results that fit the whole query higher. The first result stays the same. At the default limit, and at any limit of 10 or more, the set of results stays the same. A smaller --limit shows the top of the new order, so it can show a different result. Below the first result, inside each group of equally strong matches, a result whose docs fit the query much worse than the others in its group moves after them. A result whose name spells two or more of the query's words never moves down; it can still move up. The fit uses the same word-meaning weights astryx build uses to pick blocks, so a new component or template is placed from its own docs. A query that is an entry's whole name keeps its answer. (#10926)
  • Every import in an astryx swizzle copy now names a file the copy holds or a path the owner package exports. Before, the copy sent every import that left the component folder to the package's folder entry, which does not export the internal helpers most components use, so Button, Dialog, Table and about 100 other copies failed to type-check or bundle. Now the copy imports what the package exports from the package, carries every internal module it needs beside it in the package's folder layout, and copies the nested folders it imports (such as Table's plugins/). Test helpers and notes are no longer copied. A helper an earlier swizzle wrote is reused when it is the same and is never replaced by a copy that carries it, even with --overwrite: a different one stays, and the new copy writes its own under a version-suffixed name. Swizzling the component whose folder holds that helper treats it as one of that component's own files, which --overwrite replaces. A private attribute owner module and the style modules it imports are the exception, as before: a changed copy fails the command without --overwrite and is replaced with it. Fixes #3506. (#10197)
  • A swizzled component whose source imports another Astryx package's internal module, such as a Lab component that uses Core's gesture primitives, no longer imports that private path, except a StyleX module that package exports, which the copy keeps importing by that path because its identity is its path. Swizzle carries every other such module, and what it reaches, into the copy under a folder named after its package (for example components/astryx/core/internal/touch.ts); that package's public names are still imported from the package. (#10595)
  • astryx swizzle reports the npm packages a copy imports, such as d3-scale for a chart, with the version range the owner package declares, so the copy builds once you install them. The swizzle.copy receipt lists them in dependencies, and the text output names them to install. Node's built-in modules and the owner package itself are not listed. (#10502)
  • astryx swizzle writes an astryx-swizzle.json marker into an output folder it owns (one the copy creates, an empty one, or one it marked before), naming each package the folder's copies came from and its version. @astryxdesign/build's Babel, PostCSS and Vite integrations, and withAstryx() under webpack, compile the copies under that folder below astryx-theme, so a theme's component overrides reach a swizzled component as they reach the package component. For a folder that already holds other files it writes no marker and says what it found and how to add the marker by hand; the swizzle.copy receipt reports this in a new optional marker field. Under Turbopack and with the stock StyleX plugins, a copy's styles still land above the theme. The marker is not listed among the copy's files. (#10483)
  • The table-filter template's link-style header actions set minHeight: 0 with their auto height, so no minimum holds them taller than their text. (#10588)
  • astryx template <name> puts the template a typo slips from first in its suggestions: a name one or two slips away (a letter added, dropped or changed, or two letters swapped, as in AppShellCotnentOnly or dasbhoard) ranks just below the templates that carry every typed word. The suggestion list is never longer than before. (#10712)
  • In Safari on iPhone, text follows the reader's text size (Dynamic Type) in every theme, branded included. Where the browser exposes that size through font: -apple-system-body, as Safari on iPhone does, the theme's font sizes scale with the size the reader picked in Settings (Display & Text Size, then Larger Text), each size on the curve of the iOS text style it plays: body text like Body, heading-1 like Title 1, display text like Large Title, with every role kept in order. A semantic size a theme fixes at a length, such as the 0.75rem supporting text of Butter, Stone and Y2K, scales on the curve of the step it reads by default. At the default size every font size is the theme's own; the family, spacing, line-height ratios and the root font size never change, text inputs keep their 16px floor on iOS, and browsers without the keyword see no change. There is no option, prop or document attribute: the root Theme reads the reader's size from a hidden element. astryx docs typography/type-scale describes it. (#10416)
  • Matcha: light-mode secondary text is slightly darker (Neutral Light 30), so it meets 4.5:1 on the body (5.11:1, was 3.83:1), the surface and the card. (#10932) [fix] Y2K: light-mode secondary text is slightly darker (Neutral Light 35), so it meets 4.5:1 on the Periwinkle body (5.14:1, was 4.25:1). The CLI's Matcha and Y2K theme templates match.
  • The Butter, Stone and Y2K themes set supporting text (--text-supporting-size) in rem instead of a fixed 12px, so it grows when a reader raises the browser's default font size, like the rest of the text. At the default size it is still 12px. The CLI's copies of these themes match. (#10320)
Documentation
  • A new Course Detail page template: a long-form sales page for a single offering in two columns — the long read (a preview poster with a fact row, an about block with skill chips, a module syllabus whose sections collapse module by module, an instructor card, reviews with a scored-aspects panel, and a FAQ) beside a sticky enroll rail (the price with a compare-at, a self-paced or cohort start picker, and a weekly-pace slider that computes a finish date). Copy it with astryx template course-detail <path>. (#9753)
  • The File Explorer page template scrolls its columns with StackItem and HStack isScrollable instead of custom overflow and flex styles, and names each column after the folder it lists while the column scrolls. Its chevrons now mirror in right-to-left, and a detail pane scrolled to its end keeps its bottom padding. (#10421)
  • Hook docs for useCalendarConstraints, so astryx hook useCalendarConstraints and astryx search return it, and a useCalendarConstraints — Hotel Booking Range example block: a booking range picker that enforces min/max dates, disables closed Mondays, and caps reservations at 7 nights once check-in is selected. Copy it with astryx template useCalendarConstraintsHookUsage <path>. (#10151)
  • Hook docs for useCalendarNavigation, so astryx hook useCalendarNavigation and astryx search return it, and a useCalendarNavigation — Month Pager example block: a month-by-month calendar with Previous/Next controls, localized month-year header, and cross-month arrow key navigation using pendingFocus. Copy it with astryx template useCalendarNavigationHookUsage <path>. (#10154)
  • Hook docs for useLinkify, so astryx hook useLinkify and astryx search return it, and a useLinkify — Links in a Comment Thread example block: plain-text comments where the URL and email become Links and a custom [#123](https://github.com/meta/astryx/pull/123) issue-reference pattern shows the patterns option, while a comment without matches stays plain. (#9969)
  • Add usePowerSearchConfig hook docs and a filtered directory table example block (#10660)
  • Add useTableColumnSettingsState hook docs and a column visibility picker example block (#10652)
  • A useInteractiveRole — One Tile, Four Roles example block for the existing hook docs: a polymorphic Tile rendered four ways — href link, onClick button, Popover-trigger context button, inert content — showing the resolution order in one place. (#9972)
  • Fix the useStreamingText — Streaming Response example block: it passed isStreaming as false, so the streaming reveal it exists to show never ran. The block is now a chat-style reply card with a Regenerate button that streams the response in bursts — the hook reveals it steadily while streaming and snaps to the full text when it ends. (#9975)
  • RichTextView, RichTextEditorToolbar and RichTextEditorAutoLinkPlugin each ship a doc file, so astryx component, astryx discover and the docs list their props, defaults and usage. (#10407)
  • Tab's docs show how to give a tab help text: anchor a Tooltip on the Tab through its ref, so the description lands on the tab, and put a decorative info Icon in endContent. endContent is documented as non-interactive: a button, link, or InfoTip inside it would nest a control inside the tab's button. (#10734)
  • The grouped table page template groups its rows with useTableGroupedRows instead of hand-rendered header rows and a hand-written colgroup. Its columns now have headers, each group's toggle is a button that reports whether its group is expanded, and the row menu's Move to project arrow mirrors in right-to-left. (#10423)
  • The Tailwind guide (astryx docs styling-libraries/tailwind) adds a recipe for an app that already uses Tailwind: keep the app's own @import "tailwindcss", put the @layer line above it, and add the Astryx stylesheets after it. It explains why the @layer line must come before the Tailwind import: below it, the Astryx reset outranks every utility class, and nothing reports it. The Core README's Next.js + Tailwind section points to it. (#10532)
  • The useInputStatusIcon — Coupon Code Status example block's field applies inputWrapperStyles.textField. A field copied from it now shows its focus look at once when the primary pointer is coarse, as Core's text fields do. (#10649)
Other Changes
  • Internal: doctor.mjs and template.mjs are formatted with Prettier. No change to any command's output. (#10988)
  • Internal: the icon-set export reader reuses the shared top-level helper, and a source comment on look refreshes is shorter. No change to any command's output. (#10449)
  • Internal: the doc importers import each doc file through one small module that the CLI's own test project loads natively, so its tests no longer time out on a busy machine. No change to any command's output. (#10740)
Contributors
Thanks to everyone who contributed to this release: