What's New
Release notes and changelog for all packages.0.7.17
Experimental APIs
astryx experimental theme editor howoffers a font asked for on a part as its preset's whole stack ("monospace numbers in tables" givesui-monospace, "SF Mono", Menlo, Consolas, monospace), so systems without its first family show the next one of its kind. It no longer offersui-monospacealone, which only Apple systems draw.astryx experimental themepictures (--png) say when this machine has no font of the kind a stack names, for example headings set to the serif preset on a system with no serif font, which the picture shows in a sans-serif font. The font dial's help no longer says system presets always show.- The
astryx experimental themefont dial's help namesroundedas Nunito, an open font that loads once its package is installed, no longer beside the system presets. It also says exactly when a picture names a missing font: a serif, monospace or cursive stack drawn in a font of another kind. astryx experimental theme editor: a whole-theme token the base theme draws past on a part (neutral's neutral badge fills with its own gray, not--color-neutral) is no longer reported as reaching it.setsays that part does not use the token and gives the command that does;how <token>lists those parts undernotIn; and a value question about the part answers what it draws there, the theme's own setting on it first.astryx experimental theme editor: the part data now knows the context menu (and its dividers): each part is right-clicked when a press opens nothing and it holds a layer, as one drawn in its own place is, sohowreads what a context menu draws instead of saying it is unknown.astryx experimental theme editor: a role color too dark to stand out on the dark page still draws dark mode at the documented shade 70, and the set result now offers the shade nearest it that passes as a one-line dark-mode choice.howfor a deeper or darker role color includes a dark-mode line that stands out on the dark page, so dark mode goes the way the color asked instead of turning paler.astryx discoverlists the icon sets your discover sources offer even where icon features are off (no icon-set package installed and noexperimental.iconSet), so an app can compare packs before it picks one. A pack shows in the Available list (iconSets), in a search, and on itsdiscover <package>/<set>page, with the catalog's display name, description, license and icon count. When the catalog lists the set's definitions, the page's text says how many of the CLI's icon definitions it maps (definitions: 152/180, asexperimental icon --listprints it); the definitions themselves are listed only where icon features are on. Each listed set is marked[experimental]in text and carriesexperimental: truein JSON (a package entry names its experimentaliconSetsinexperimentalFields). The page gives the project's install command, thenastryx experimental icon use <package>/<set>. Installed sets, their pages and--type icon-setstill need icon features on,astryx search's discover line never points at an icon set while they are off, icon-set fields on other kinds are ignored, and a catalog with no icon set gives the same output as before. Discover catalogs may give an icon set'slicense.- Doctor's new
icon-importscheck names each icon import that no longer matches the app's icon sets after the list changes or a set is uninstalled: an icon from a set the list leaves out, or from a backup when an earlier set draws the same meaning, warns with the icon of the list that replaces it; an icon import or re-export of an npm package that is not installed, not declared, and not mapped by apathsorbaseUrlentry in the app's tsconfig or jsconfig fails, since it breaks the build, even when that package is the main set itself. The check runs where icon features are on and a main set is decided. astryx experimental theme editor set <theme> --color-border <color>: the emphasized border (input and selector frames) follows a border only where that makes it stronger on the surface, never fainter, and the result now says it follows;shownames it as following your--color-border, not as a change in the theme's own source.astryx experimental theme editor: secondary text set exactly for the whole theme (in one mode or both) no longer turns off the readable shade on the parts that lift it (selected items and rows, a dropzone, numbered citations). Where the exact color reads on what those parts sit on it is used as written; where it does not, they take the gray nearest it that does, or, with no color dial, the base theme's own lift.- A run of one
astryx experimentalcommand loads only that command, asastryx <command>already does.astryx experimental exportandastryx experimental importno longer load the theme editor first, so each run starts about 0.2 seconds sooner.astryx experimentalalone, its help, and an unknown word still load every command, so they print the same answers. astryx experimental theme editor set <theme> accent <color>keeps the color you gave as the link and accent text color wherever it reads at 4.5:1 on what that text sits on, in each mode its fill is your exact color; only where it does not do links move, to the nearest shade that reads, and the result says so with the ratio. Text on the fill stays white or near-black by contrast (button and badge labels are normal-size text, which needs 4.5:1, so white on iOS blue #007aff, at 4.02:1, is not picked), and the note now names how to keep the other one exactly.astryx experimental theme editor howreads every way an amount is said ("a quarter bigger", "half again", "2x", "×2", "x0", "4 times", "by a factor of 2", "+50%", "-25%", "50 percent", "½") as a factor of what is there now, never as a length and never with an extra dial step; keeps fractions of a pixel; scales a part's line height and opacity the asked way ("50% more transparent" lowers the opacity and leaves the fill); answers whole-theme radius and border width amounts with exact token values (a whole-theme spacing or text amount it can only step says so); says when a part has no width to scale instead of giving a fixed cap; scales an own side padding with the rest; keeps the state and variant of a "2px rounder on hover" move and of a padding step; reads a corner percent with an amount ("50% of now", "20% bigger") as an exact radius, never a CSS percent; says when a corner amount can only step; and reads "no inner spacing", "zero padding" and "no gap" as zero of that thing, in the state asked.astryx experimental theme editor how: amounts read the way they are said. Zero, none and no set that property to 0 or none in any position ("card corners zero", "zero border", "opacity zero", "no letter spacing", "remove the top padding"), and a padding side reads its own value now. One amount reader takes "up 20%", "increase by 50%", "2/3", "two thirds", "three quarters", "twice as small", "a third again" and a lone "½" as a share of now; a bare percent radius is refused with the command that scales the radius instead. "Two steps bigger" gives two dial steps, "2 spacing units" is twice the spacing unit token, a size such as "24x16px" on padding is that exact padding, and "+4px", "-2px" or "4px more" on padding, gap, radius or text size is the value now plus or minus that length. See-through amounts set opacity ("half transparent", "10% transparent", "50% opacity"), "more opaque" raises it, and "5% gray" is gray at 5% alpha. Color amounts apply to text and hover colors; warmer and cooler move the hue, not the lightness; lighter and darker change the color of borders, dividers and links, and keep the alpha of rgb(), hsl() and oklch() colors. Small, secondary and supporting text and fine print change the supporting text size; "h1 800" is a weight; "h2 through h4" changes each level; "h1 800 and the other headings 600" sets every other level; "h1 twice as big as body text" and "h3 the same size as h2" take the other size times the amount; "and the active one blue" keeps that state. Thinner text is a lighter weight, a sharper shadow halves the blur of the part's shadow and a softer one doubles it, a thinner scrollbar says there is no scrollbar part, the overlay's lighter or darker changes only its alpha, and wider no longer sets a made-up 720px width.how paddingLeft,how borderRadiusand other camelCase names look up that property.astryx experimental theme compile:--checkof an editor theme also checks its app copy insrc/themes/<theme>/and fails withERR_THEME_STALE, saying why, when the copy is kept back, missing a file, gone, or not the current build. Each theme's copy follows its own build, so a later theme failing no longer leaves an earlier one's copy behind. The copy's files are not theme sources: compiling its descriptor, a copy build file orsrc/astryx-themes.tsnames the theme to compile, the copy's source from a subfolder names the app root, and an--outinto the copy folder is refused. A copy left with only its build outputs is still the editor's, a copy file that is gone is written back by the nextset, and a folder the copy could not be made in is named. The compile help says it writes and checks the app copy.astryx experimental theme compile: a successful compile of an editor theme always writes its app copy from what it just built, a hand edit of<theme>.theme.tsincluded, with the copy's font stylesheet from the fonts the theme loads now (a font package installed or removed since; asetthat changes nothing refreshes it too).--checkreads the copy as a checkout writes it (CRLF line endings pass), compares it only once the theme's outputs are current (a hand-edited theme output is named by the outputs check), and a stale copy keeps the documented check result:upToDate: false, codeERR_THEME_STALEandappCopyStalesaying why. The copy's source and folder are no compile targets, an--outat the copy folder (any case, with or without a slash) is refused and suggests the same compile without--out, and a refused compile writes no copy. The help says so.astryx experimental theme: every command that builds or checks an editor theme says when its app copy insrc/themes/<theme>/is behind:compilewarns,compile --checkfails while the copy is kept back or gone, and asetthat changes nothing still carriesappCopyStale. A link or a folder of yours at a copy file name stops the copy like a file of yours does, and a copy that cannot be written says why (not writable, disk full, a file where the folder goes). A copy whose descriptor was deleted is still the editor's and is written back. Compiling the copy's source takes the theme's lock and writes the copy again; with the copy gone it nameseditor show. Fonts the copy's font stylesheet loads are not called unloaded. The editor and compile help say the copy rule.astryx experimental theme editor: the app copy insrc/themes/<theme>/is written around a file of yours at another name (a note, a swap file); only a file of yours at one of the copy's names, or a link on the way to it, stops it, and then every change's result andwiringsay the copy was not updated and why. The copy's<theme>.fonts.cssis always there (a comment only when the theme loads no font stylesheet), so the app theme module's import of it holds when fonts or the base change;compilewrites the whole copy, that file included.newrefuses a name the theme commands skip (a--b,b-) and suggests the cleaned one. The package commands give true answers for an editor theme:ejectsays its source is yours already, and a path (themes/<theme>) is answered with the command by name.- The in-app theme preview's top bar draws the theme's name with Core's
TopNavHeading, as an app's top bar does, so a setting on the header (such as its text color) shows in the preview as it does in the app. astryx experimental theme editor: asks that name parts by reference or in two states read as Core draws them. "The disabled one" after an element in a place ("the hovered item of menus … and the disabled one") is that element; "the others" are the part's other variants, or the part not in the state named; states said together read by their kind, a condition among them (checked, selected, disabled) meaning all at once and moment states alone (hovered, pressed) meaning each, with the other reading offered as a second line; a selected table row hovered sets the selected wash's token for hover; a switch's "on color" is its checked look; tighter table rows lower the cells' block padding one spacing step. A border asked of a list inside an overlay's surface (a typeahead's) points to the overlay's edge, andsetrefuses a border's color or width on a part that draws no border (a divider), offering the token its line reads.astryx experimental theme editor's pictures and contrast checks take a toast's text side by Core's own rule for the fill the toast draws: the theme's text where it reads at 3:1, else the on-color that reads better; a see-through fill is composited onto the page first, and a gradient falls back from the inverted surface, as the app does. A problem there comes with acolorline on the toast, which set takes. A transparent part on a lightbox's dark island is measured on that island. Parts drawn open keep the custom properties their inline styles set (a dialog's maximum size, a popover's gap to its trigger), and a plain element in a doc example (the Overlay's media) draws.astryx experimental theme editor set … surfaces: a panel whose outer frame paints nothing (the banner) gets the dial's line and shadow on the part inside that paints its rounded fill, sosurfaces outlinedno longer draws a square border around the banner's rounded corners, and a border setting on the banner reaches that line.hownever reads "Windows" named with a version ("Windows 11 accent #0067c0") as the containers.astryx experimental theme editor: the "thick borders on everything" answer and a whole-theme--border-widthalso reach a framed control (a segmented control), the parts that draw a box only when selected (nav items, segments), on that state, and the indicator lines (a tab's underline), at the border width.astryx experimental theme editor how: a size ask with a bound that the part is already past the way the words ask ("rounder but at most 16px" on 42px corners) writes nothing and says so, never a move the other way; a direction beside a bound on a property with no scale of the theme's own (height) goes to the bound; "the body text … but at most 16px" is the base text size. A theme color with a way ("the accent color but lighter") is that color made that way in each mode. "The page color" as a gradient stop is the color the page is painted with, and the page is not changed. A role color made darker or lighter on a dark-only theme moves each of its tokens that way, its text included. "The same as" after a color property compares that color. "What color is the page" gives the page's color in each mode, and its pointer is the token that paints it.astryx experimental theme editornames words the sample page's pictures break across two lines inside the word (a table word at a larger text size, "roadma" then "p"), measured in the page by the browser that takes the picture, as it names text cut short: a note, and a problem with the line that keeps the word whole when the browser measured one, else none.astryx experimental theme editor: a light-only or dark-only theme's build exports its one mode beside the theme (export const colorModes = ["light"];), and its app copy re-exports it, sotheme addwires the theme in that mode. Older CLIs and Core ignore the extra export.astryx experimental theme: every build names the pictures it removed, soeditor showand the preview commands say so too when they build a theme again. A picture run whose browser fails part way says which pictures it took and which it did not. A render that fails on two copies of React points at the package manager's listing of them instead ofdoctor.show --sectionoffers a section only within a typo of what was typed, else the whole sheet;preview add --topoffers the typed number read exactly or brought into range, else the default;preview add --templateoffers a default page (overview, components, colors) within a typo. A base theme whose fonts come from a remote stylesheet (Google Fonts) gets a note that the previews and their pictures show the next font, and how to install a copy they load. The sheet's template pages render (they bind their file's default export), and a part Core re-exports under a name of its own (ContextMenuItem) gets its module and a cell; a component no Core module exports gets no empty cell.astryx experimental theme editor: one built-value check for a theme's own token values runs before every build (set,undo,show, the preview) and incompile, so a value one refuses the other never writes. A[light, dark]pair on a token that is not a color is refused however the file gives it (an import, a const, a spread), naming the file and line that hold it. Typography weights are judged as the tokens they build. A private variable (--_*) and a key that is no token name (color) are refused with their line. A pair in the theme file is shown by its light and dark values in notes.undoof a token the theme's own source sets names that file and line.astryx experimental theme editor:newreads a built-in theme typed with another word (theme neutral,neutral stone) as the base, never as the neutral color dial, and a base or setting typed with its own quotes ('base neutral',"accent" red,'"base": "neutral"','padding: 8px') as that setting, never as words of the name. A settingnewtakes no option for points at the parts it is written on (how '8px padding'), in place of asetlinesetitself refuses.undoby a held value with a scope typed ranks the settings by how much of that scope they share, soundo t red --on toggle-buttonleads with a toggle-button setting rather than a whole-theme one.astryx experimental theme editorcontrast-checks the button style (buttons softandoutline) like any other change: the primary button's text on the fill it draws, or on the page and surface where it draws none, in each mode, with the nearest readable color as its line, instead of a "not checked" note.astryx experimental theme editor set <theme> padding '5px 0' --on dropdown-menu(or any part whose padding Core reads insidecalc(), where one length is all that works) now offers the sides it means. Before, it offered a pointer tohowfor two lengths, and for three or four lengths (or two variables) one line with the first value only, such aspadding 2px, which dropped the other lengths. Now it offerspadding-block 5pxandpadding-inline 0for two lengths,padding-top,padding-inlineandpadding-bottomfor three, and each side for four, each with the length you typed for it. A repair gate fix lets such a refusal offer three or four side lines together.astryx experimental theme editor: the cached part data is keyed by a fingerprint of the code that builds it (the census source and every file it imports), beside the installed Core, so any change to that code builds it again; there is no version number to bump by hand.astryx experimental theme editor:- The part data reads overlays drawn open: a tooltip, a popover, a hover card, and the lists a menu's button or a selector's field opens, which render on the server as markers alone, so
how tooltipnames what it paints and the menus group is checked. - A fill set on a part says which fills Core gives its variants and states it now covers (a checked box's accent, a primary button's), with the line that changes only the fill at rest and the lines that fill one variant or state; a later color change says where the part's own fill keeps it from reaching.
corners morefrom round steps to half as round again before pill, andcorners lessfrom pill back.- A border color the theme sets is held to 3:1 against what it sits on in each mode.
- The part data reads overlays drawn open: a tooltip, a popover, a hover card, and the lists a menu's button or a selector's field opens, which render on the server as markers alone, so
astryx experimental theme editornames more of what a change leaves unchecked or unreached: a part's text color for a state (a selected nav item's) is measured on the fill the part draws in that state, with the nearest readable color as its line; a color the base theme writes as its own accent rather than the accent token (butter's blue links and outline buttons) is listed under missed once the accent moves, with a line that points it at the accent; and a fill made from a status token the theme's status color does not reach (an error toast's red after the danger color is set) is listed, with a line that gives it the theme's status color.- A change lists every custom property whose built value moved, in the JSON and the text:
changedTokenskeeps the theme's own tokens, the page included, and a newchangedPartTokenslists the tokens the built stylesheet sets on parts (a readable text color on a selected row), each by its rule and mode, read from the stylesheet before and after the change. A dial that moves many tokens at once (vibrancy, a font) lists them all. astryx experimental theme editor: one check for the token values a theme's own source gives, run byshow,set,undoandcompile, each refusing with the same message and writing nothing. A[light, dark]pair holds exactly two values in quotes (one, none or three is refused). Values from an imported module or written as an expression ('ban' + 'ana', a template) are checked as a build evaluates them, naming the line. A secondtokenskey is refused, naming both lines (JavaScript keeps only the last). A family list in one pair of quotes is refused in the file assetrefuses it (the browser reads it as one family by that whole name). Thetypographyfields are checked: a family is one family name (the rest go infallbacks), the scale's ratio is above 1 and at most 4, its base a positive size.astryx experimental theme:- Custom properties that read each other are refused at their line: a token and a local token reading one another, and a part's own custom property reading itself.
- A pseudo-class after
::search-text(:current) or::scroll-marker-groupis accepted. A pseudo-element inside:is(),:where(),:not()or:has(), a pseudo-class after::highlight(), and:window-inactiveafter any highlight but::selectionare refused. A pseudo-element near a known one (::befor) is refused as that one misspelled; one missing from the CLI's selector data and near none (::column,::scroll-button()) is noted as possibly newer than the CLI, and built. - A misspelled vendor property (
-webkit-line-clmap,WebkitApperance) is refused, with the vendor property it is near. - A value read from another file through array or nested destructuring (
const [first] = arr,const {a: {b}} = cs) is blamed on that file and line. - A null value is warned at its line and the theme keeps working, while a boolean, NaN, an object or an array, which mean nothing in CSS, are refused. The warning says what it builds: a null property leaves the base theme's value; a null token is kept by the browser as the token's value, so most properties that read it act as if they were not set (text keeps the surrounding color, a background goes transparent) and a font family reading it falls back to the browser's default font.
astryx experimental theme editor how: a color dial made lighter or darker steps from the color it grows its shades from, its saved color, else its token where that is a color of its own. "make the neutral color darker" no longer offersneutral '[#000000](https://github.com/meta/astryx/pull/000000)'(a gray seed grows the same shades, so it changed nothing) nor an exact--color-neutralthat turned every see-through neutral fill opaque; it says why and what to name instead. An exact-token alternative keeps the token's own strength.astryx experimental theme editor set: a color set with no--modein a one-mode theme (dark-only) is saved for that mode, as it is built, so setting the theme back to both modes keeps it in its mode instead of painting the other mode with it, and a color saved for the other mode (the half a toast or a lightbox reads) is kept. An undo with no--moderemoves that color.astryx experimental theme compile: the app copy guard reads paths as the build does, so an--outwritten with backslashes or through a link into an editor theme's copy is refused, and a copy file named with backslashes is answered with the theme to compile. A file of yours in the copy folder, without the editor's mark, compiles like any theme source. Refusals run from a subfolder suggest the compile from the app root. The note on fonts named but not loaded follows the font stylesheet this compile writes, and the copy's font file no longer says the system has a font no package loads. A check held up by a file of yours names it and never sends you to a command that does not move it.astryx experimental theme: the editor reads which theme a source defines from the export a build of it loads, so a helper theme exported beside the real one is refused before anything is written, and a name given by a const or a//inside a string no longer counts as damage. Font notes, the previews and the app copy load fonts for the families the theme builds, from one list.compilerefuses an--outin the theme's own folder (other than its default stylesheet) before writing anything; an--outelsewhere says that the theme's folder and its app copy were not written or checked (appCopySkipped). A pointer to compile from the app root leaves off an--outthe root cannot reach, and a family refusal from a subfolder suggests a compile that runs. Suggested commands stay bare in JSON (astryx …), as the text output starts them the way the project runs the CLI. The compile doc says what compiles.astryx experimental theme: the editor judges a theme's source by the theme a build of it loads, its name and the theme it extends after every spread and repeated key, so a spread or a secondextendsthat replaces the settings is refused, a spread const or a namespace import of the settings is accepted, and a helper theme read first is named with how to make the build read the theme.compiletakes an--outas the theme's default stylesheet only when it is that same file, refusing a name that differs only in case on a case-sensitive disk and a folder form of the stylesheet before anything is written; builds a source named through a folder link under its own path; says in JSON what the app copy write did (appCopy,appCopyStale); names the Fontsource package for an editor theme's fonts. Every suggested compile passes the same checks before it is shown. Fonts follow every family the build writes, a part's own font included. A module that imports a file beside the theme keeps the app copy as it was and says why. A change of mode on a theme the app lists namestheme add.astryx experimental theme compile: a compile or--checkof an editor theme whose source no longer imports or extends its settings, or names another theme, is refused with the same messagesetgives, so it never writes another theme's files or drops every setting. The app copy's font stylesheet imports the installed@fontsourcepackage of every family the built theme uses, the theme's own source included, and compile's note on fonts named but not loaded follows it. A theme build counts the families the theme's own font stylesheet beside its source loads (the app copy's), so a build of the copy's source no longer names them as unloaded. A blank or whitespace-only--outis refused.astryx experimental theme editor how: a part word matches only as a word of its own, never as one half of a hyphenated compound, so "field-service app: large bold text, thick borders" is the whole theme's ask, not the inputs'.astryx experimental theme editor: the contrast check reads gradients, andhowreads side nav section headings as the sections.- Text on a gradient background is measured against each of its color stops, the worst one counting; a background with an image, or a stop with no fixed color, is listed as not checked.
howreads "sidebar section headings" as the side nav's sections, whose title is drawn inside them, and says which inner parts an inherited text property also reaches.how <part>says what the part is, from its component's doc.
astryx experimental theme editor: the contrast check measures what draws the text. A toast's text on Core's media surface reads the on-dark or on-light color, so a low one is a problem with a fix that sets it; a color given as a theme token (var(--token)) is measured as that token's value in each mode; and text on different parts is a problem for each part, so following one fix line no longer turns up the others as new.astryx experimental theme editorfixes contrast problems at their source: a whole-theme text color too faint in many places gets one line on that token, the nearest color that reads everywhere it was too faint, instead of one line per part; a pale status or accent fill gets the nearest darker color that stands out from the page as its line; and a failure the base theme draws itself is said byshow, not after every change.astryx experimental theme editor: every contrast problem is listed in the JSON (newProblems,openProblems,problems); the text shows the first eight and counts the rest. A change's new problems are the ones the settings before it, read as the change reads them, did not have, so a base or part saved in other letters no longer loses the check or lists old problems as new. A fix line sets what draws the text: a plaincolorthat wins over a token, else the text token, scoped to the variant the text is drawn in, so following it clears the problem; text written straight in a part with its owncoloris measured against the part's fill.showsays a saved base in other letters reads as the base; an entry with a thing and no value gets itsundoline; a dial name in other letters (Corners,MODE) is the dial; a theme typo on a step back with nothing to undo offersshow; andnew's set repair for a theme it did not make follows itsnewline as the next step.astryx experimental theme editorcontrast checks judge what the page draws, and every fix line fixes its problem without making another:- A fix line keeps the scope of the change it answers: after a setting with
--only, its line carries--only, so following it changes the part named alone. - The text typed in an input (its value, or its placeholder) is measured on the input's fill like any other text, with a fix line.
- Text that sits on a part whose variants draw different grounds (a heading on the app's header) is measured on each variant's ground, and its fix line names that variant, so a fix for one leaves the others readable. A new problem on another ground is named as new.
- A base theme's own text color on a part (butter's nav item) is what is measured, before a text token set on the part around it; a line that would change nothing on the page is not offered, and a problem no single line can fix (the same text on grounds that need opposite colors) shows with no line.
show'smissedlist offers only lines set takes: a part whose filled variants set cannot name is left out, never given a question.
- A fix line keeps the scope of the change it answers: after a setting with
astryx experimental theme editor: the source, descriptor and font stylesheet of a theme's app copy (src/themes/<theme>/) name the exact command that writes them in their first comment,astryx experimental theme editor show <theme>, so a missing or stale copy is fixed with that command; the built.css,.jsand.d.tskeep the build's header.astryx experimental theme editor set <theme> corners <value>now gives--radius-chatback to the container radius (var(--radius-container), Core's own default), so chat surfaces (the composer, its drawer, message bubbles) follow the theme's corners instead of keeping the chat radius the base theme pins (28px on most bundled themes).astryx experimental theme editor:corners roundedis offered theroundrung first, as the English word says, then Tailwind's 4px: on most bases 4px alone is sharper than the corners already are.astryx experimental theme: a font family name is read as CSS reads it, so an escaped name (Gill\ Sans,"\5FAE\8F6F\96C5\9ED1") is a family, never a font file. A family the theme holds in its own property and reads withvar()counts as a family it builds: the app copy loads its installed package and compile names it until then.compilegives the noteshowgives when the theme's own type tokens do not show on phones, and that note's fix for a weight is a rule for the same screens, which keeps it. The full report of an editor theme wires its app copy (theme add), not its editor folder.astryx experimental theme editor: the sample card's buttons wrap to a second row when a theme's buttons are wider than the card (butter's and matcha's padding, a bolder weight, roomier spacing or a larger text size), so the preview never cuts their labels short. With--png, text the sample page's pictures still draw cut short (a label that ends in an ellipsis or runs past the edge of a box that clips it, such as badges at a large text size) is measured in the page by the browser that takes the picture and named inset's andshow's results, as a note and as a problem. The problem's fix line isflex-shrink 0on the part, offered only when the browser measured it drawing every label whole; otherwise it says that line does not. A theme whose pictures cut nothing short says nothing.astryx experimental theme editor: a settings entry whose mode is written in other words (Dark,night,Light,day) is read as dark or light, and one whose source is written in other letters (Dial) or missing is read from the thing (a dial, a--token, a part property). A note says how each was read, and the next change saves it that way, so no command is blocked. An entry whose mode or source means nothing is refused with the undo that removes only that entry first, and the step back, which loses the last change, second. When a theme name is typed as a path (./t,themes/t), theset,undoandcompilewith the theme's name is checked by that command before it is offered, with every repair in the one line; an--outoutside the working folder is dropped, and the reason says why.astryx experimental theme editor how: "the today date in the date picker" says why nothing is written in one line (the date picker's calendar is the plain Calendar, drawn in the layer it opens, so a change there reaches every calendar) and names the line that changes every calendar's today day instead.setwith a CSS property and no--on, given a value labeled with a part ('card: #eeeeee'), offers that value on that part.astryx experimental theme editor: heading colors, the page background, gradients per mode, and background values with many variables.color … --on heading(also per level with--when level:N) is written as the text color tokens the heading's color prop reads, on headings only, so it shows;howanswers "headings in the accent color" with it.- The page behind your parts is painted by
app-shell:--on page(orbody) is refused with theapp-shellcommand, andhow "page background"offers--color-background-bodyfor a color andbackground … --on app-shellfor a color or a gradient. Setting--color-background-bodyno longer says it changes nothing where Core's own page styles read it. - A gradient background can differ between light and dark:
background '<gradient>' --mode darkpaints each of its colors in that mode only, beside the other mode's layers. - A background value with more than three variables (
color-mix()withvar()and a stop position, layered dots) is read as CSS, as the same value with plain colors is.
astryx experimental theme editornotes a destructive button a person cannot tell from the primary one (a pastel pink accent beside the soft salmon destructive fill: their fills close in OKLab), with the line that draws the destructive button in the theme's danger color. It is a note, not a problem: it fails no contrast.astryx experimental theme editor: what it is given is read as meant and checked.- A dial typed as a flag (
set <theme> --corners round) is refused as a dial typed with dashes and offered as the dial (set <theme> corners round), never an empty token list. - A token value your
<theme>.theme.tsgives thatsetrefuses ('--radius-page': 'banana') is checked by the same rules:show,setandcompilerefuse it, naming the token and its line, before anything is built. - The theme typed as its module name (
brandTheme) is the themebrand, never a second theme. - A light and a dark color on a part's color (
background 'light: #fff; dark: [#000](https://github.com/meta/astryx/pull/000)' --on card) is written as that property'slight-dark()pair. - A JSON object of settings passed to
setgives one set line per entry. - A font stack with escaped quotes (
\"Inter\", sans-serif) is read as the stack. - A state a part lists in camelCase (toggle-button's
isPressed) is taken in any spelling, andpressedsuggests it. - A
modeorbaseentry inside the settings list is named byshowas doing nothing there, with theundothat removes it. - A pasted line with two declarations (
accent: red; text-size: 18) sets the first and says the second was not set, with its own set line.
- A dial typed as a flag (
astryx experimental theme editor: a dial whose number is in pixels takes that number typed with its unit, in any letters and with a space before it, soset t text-size 24pxsets 24 asset t text-size 24does; undo,new --text-sizeand a saved20pxread it the same way. A size past the dial's range is refused naming the value as typed.astryx experimental theme editor: the part data records what a divider's line paints (its color per variant and its thickness) as the divider's own, sohowmakes a divider fainter, thinner or darker through the color and width its line reads, and thinner or thicker steps from the thickness it shows now.astryx experimental theme editor how: an icon read as the element of a place ("the chevron in selects", "the close icon in dialogs") takes its color, never a box behind it; a part said right before its separators ("the dropdown separators", "the context menu separators") owns them; an element after, before or next to a part's text ("the icon after the button text") is that part's.astryx experimental theme editor:- An element named in, of or after a part ("the checked indicator in checkboxes", "the indicator in selects", "the knob of switches", "the tabs' indicator", "the hovered item in menus in cards", "today's date in the calendar", "the highlighted option in the selector") is the part that place draws it as: the place itself by its name, a part named after it, a lexicon phrase said owner first, a part drawn inside it, or the one whose own state the words name, never the place or every element in it. "The buttons' icons" are the icon tokens on the buttons.
- An element its place has no part of its own for ("the close button of toasts", "the hovered item in the context menu", "the today date in the date picker", whose calendar the part data draws closed) writes nothing, and the answer says why.
- A state read from the part and not said ("the dot in radios") is let go when the element has none.
- "The checked and disabled checkbox" is the box in both states at once, in the part's own order;
--state isPressed+hoveron a toggle button is taken (Core marks isPressed with aria-pressed); "highlighted" names the highlighted state. - What a line inside a part draws is each part on its element (a dropdown menu's own divider draws its separators), and a part whose paint is a line takes the divider answers: "the menu separators red" is
--color-borderon the menu's own divider, those separators only. PART_DATA_VERSION 24. - A token a variant never reads is refused with a line that keeps the state and the mode asked.
astryx experimental theme editor: the input cleanup follows through. Quotes are mapped only where they delimit a value (curly quotes of one kind in any shape, such as „Inter“ or ‚Inter‘, «», ‹›, full-width quotes and backticks around a font name become straight ones, and a curly quote left unpaired is the straight one it stands for), and a quoted CSS string keeps what it holds, curly quotes, no-break spaces and a;included; a saved value is checked the same way, and quotes around a value are named as such. An entry pasted from JSON ("accent": "#e11d48",{"accent": "#e11d48"}) or with copy debris (a trailing comma, a stray quote or bracket, a leading=or:, a second declaration after a;outside quotes) is read as the value; a quoted dial value suggests that value; a dash-like character inside a token name is its hyphen;textSizeandtext_sizeare text-size. A font stack is read as families: a trailing comma is dropped, a stack wrapped in one more pair of quotes is unwrapped, and an empty family is refused.--modeis cleaned like a value, and a near typo keeps--modein the suggestion. A saved dial value with stray spaces, quotes, other letters or a pastedcorners: pillis offered cleaned, read by the same input cleanup as typed values; a theme folder holding only empty folders counts as empty fornew; a mistyped theme name in set or undo (T,themes/t,./t) suggests the same command with the theme's name.astryx experimental theme editor how: an exact amount ("half", "double", "a quarter", "a third", "3 times", "25% bigger") of a part's font size, line height, letter spacing, opacity, width or border width is that factor of what the part has now, never a fixed step; "3 times bigger" is an amount, never a 3px value; "double the border width" doubles it (no double-line style, no width cap); "half as round" scales the radius there now; a quarter of a padding or gap with nothing to read is a step down, said to be a step; a group's own name ("checks") is read as that group; an amount with a state ("on hover") scales that state's value and keeps the state; a dialog's header is the dialog header, not the app's top bar (likewise a card's or a dialog's footer); and the part "everything except cards" leaves out keeps the value it has now.astryx experimental theme editor: input readers keep what was typed.- A family the editor does not know that is near a generic or a preset (
Inder,Monaspace,Serifa) is offered the near name and the family as typed in quotes, which keeps it as written; never only another font. - A comma between two bare numbers that a property pairs with a slash (
aspect-ratio 16,9) separates them:16 / 9, never16.9. - A saved entry whose thing differs in case or spacing, or whose value is a number, and a saved font value set repairs (
Inter 16px), are offered set's repair beside the undo. - A base reads in any of its names (
neutral-theme,neutralTheme,neutral theme, its package) in set, new and the settings file alike. - A list item that is only weight, style or size words (
Inter, bold) is no family: refused with the families and the weight or size line. - A JSON entry's string quotes are JSON's, for a font list too (
{"font": "Inter, serif"}).
- A family the editor does not know that is near a generic or a preset (
astryx experimental theme editorandcompile: the families a part'sfontshorthand in your<theme>.theme.tsnames last get the family checkfontFamilygets (a comma missing before a generic family, a quoted generic), refused with the file and line.astryx experimental theme editor: a weight word at the end of a font family's name is part of the name (Arial Black,Archivo Black,Segoe UI Semiboldare taken as typed) unless the whole name is no family the editor knows and the name without the word is (Inter ExtraBoldis Inter and a weight); a weight number (Inter 600) is never part of a name. The Segoe UI weights Windows ships as families of their own are on the system font list.astryx experimental theme …: settings reach the build, and fonts load as the theme shows them.- A theme source that spreads the
defineThemeresult and replaces itscomponents({...defineTheme(…), components: {}}) is refused by name, as one that replaces its tokens is: a part setting would be saved and never built. Give your own components insidedefineTheme({…, components: {…}})instead. - Italic text (
font-style: italic, oritalicin afontshorthand) loads the installed package's italic stylesheets beside the upright ones (400-italic.css, a variable package'swght-italic.css), so the browser no longer draws a slanted copy. - Noto Sans, Noto Serif and Noto Sans Mono are named system fonts of Android, ChromeOS and Linux, and Cantarell, Ubuntu and Ubuntu Mono system fonts of Linux, so a system font stack that names them is not told it needs a package.
- A heading weight given with no type scale is offered
editor set <theme> headings <weight>, which changes only the heading weight. The hint no longer says to add a type scale, which would also resize all text. A weight number outside 1 to 1000 is no longer echoed as the example.
- A theme source that spreads the
astryx experimental theme …: the settings file and pasted forms are read as typed input. A saved setting whoseon,whenorstateis not text ("when": 5,"on": {}), or whose part is empty, no longer makes every command fail: it is refused as a damaged setting with an undo line that removes it. A set of headings replaces a saved headings entry whose axis names no half, so later commands work. A saved base writtenNone(in any letters) is no base, and the file's own field names in other letters (Like,Settings,Mode) are those fields. A pasted entry's field spelled as its flag ("--on": "card") is that field, and a pasted change line with the→arrow, a label before its colon, or a label and colon with no old value keeps the label as the mode. An empty pasted object points to the dials and the help.undo t 'accent red'reads the setting and its value as set does. A swapped setting and value whose setting is misspelled (set t pill cornres) gets the swap line.astryx experimental theme editor …: for a setting the settings file lists twice by hand, undo accepts either value it holds (undo t accent redorblue), removes every entry, and its result names each value removed (alsoRemovedin--json); a value it does not hold is refused naming the one the build reads.shownotes a field the settings file writes twice (likeandLike), as a change does. A token name whose word is a part the editor knows (--color-text-link) is no longer repaired by spelling to another token (--color-text-pink).astryx experimental theme editor …: a saved twin of a setting in other letters (accentandAccent,--color-accentand--Color-Accent,background-colorandBackground-Coloron a part) is that setting listed twice, which a set or undo of it fixes, instead of a refusal sayingAccentis no dial. A field a saved setting writes several ways, none of them the editor's (Onand--on,thingandsetting), is read once from the first, with a note, and the next change writes it once. A saved field the editor does not read (modes) is named, with the field it is a typo of. An entry pasted in the saved form without a value (undo t '{"thing":"padding","on":"card"}') is read by its thing.astryx experimental theme editor: a radio's circle (a part with a checked state, a square box and corners at 50%) is no corner. The corners dial on its group leaves it, in the build as inshow; the dial on the radio alone is refused (it changes nothing you see) with the line that does set its shape (set <theme> border-radius 0 --on radio-indicator --only);howoffers that line for "make radios square" and answers "rounder checkboxes" with the checkbox alone.astryx experimental theme editor how: "focus ring color like the links" (or "the same as", "match") sets the focus ring's color from that part's own color token, theme-wide unless a part is named before it, instead of a ring width on that part. An amount of padding on a part with no padding to take it of says the answer is one step, not an exact amount.astryx experimental theme editor: a family whose last word the editor knows as itself (Inter Tight) is no weight typo and is kept; a misspelled style word (Inter Bold Itallic) is answered as the exact words are; any weight number after a known family (Inter 650,Inter 6OO) is read as a weight; and a value holdingNaNorundefinedis refused at set, naming the value, never left to fail the build.astryx experimental theme editor set … font: a number after a family the editor knows is read as CSS reads it, a weight from 1 to 1000 (Inter 450.5,Inter 50) and any other number no family (Inter 1500), never saved as a family of that name; a word with another first letter is no typo of a weight word (Inter Night,Inter Rightare kept); and a font role in other letters (--on Body) is answered as that role, never as the app shell.astryx experimental theme editor set <theme> font: a family no package loads is named with the install line of the Fontsource package its name maps to (such as@fontsource/press-start-2pfor Press Start 2P); once installed, the previews and the app copy load it like any font package.astryx experimental theme editor set … font: a weight or style word typed with a typo after a family the editor knows (Georgia Blod,Inter semibld,Courier New Itallic) is read as that word and refused with the family and weight lines and the name kept as typed, never saved as a family of that name. A typo of a font preset inside a list (Robto, sans-serif) is read as the preset, as it is alone.astryx experimental theme editor: the font dial reads every weight or style word after a family, each through the one typo limit (Inter Bold Itallic,Inter Tihn), and offers the family and headings lines for them as for the exact words. Anewrefused for its name keeps the repair of a font the font readers refuse (--font robotofor--font Robto). The note on a family near a system font with a weight word (Arail Bold) names lines set takes: the family, and the headings weight.astryx experimental theme editor: fonts Apple ships on iPhone and iPad as well as the Mac (Apple Color Emoji, Helvetica Neue, PingFang, Hiragino Sans, Avenir Next, Futura and others), and-apple-system, are noted as shipping only on Apple platforms (macOS, iOS and iPadOS), not only on macOS. Mac-only fonts (Monaco, Lucida Grande, Geneva,BlinkMacSystemFontand others) are still noted as macOS only. A comma before three digits on a millisecond time (transition-duration '1,000ms') is a thousands mark, as on a pixel length, so the repair is1000ms, not1.000ms. On rem, em and seconds it stays a decimal point (1,125remis1.125rem).astryx experimental theme: a font family maps to its Fontsource package as Fontsource names it: a<Name> Variablefamily to@fontsource-variable/<name>, which loads it once installed, and other characters dropped (Mrs. Sheppardsis@fontsource/mrs-sheppards). No package is suggested for a font a system ships on any platform (such as Microsoft YaHei or PingFang SC) or a name Fontsource cannot publish. An installed font package loads every weight the theme uses (a stylesheet per weight, as Fontsource ships them), in the app copy and the previews. The font dial takes a CSS-escaped family, as tokens do.compile --checknames a missing output in its check result.astryx experimental theme:editor show'smissedlist frames only what draws a box: a part with no filled box at rest in any variant (a ghost toggle button, a menu row) is borderless on purpose, and with the border width at zero nothing is missed for want of a border.preview app's font note names only weight sheets a Fontsource package can have: a weight between two hundreds (650) is drawn from the two around it.preview apprefuses a theme that imports a Sass, Less or Stylus file, which the new app does not build, naming the import, before writing anything.preview appnames an entry called node_modules or a version-control folder as left out whether it is a folder, a file or a link, and the note on a link says to copy what it leads to.
astryx experimental theme editor: a color or timing function typed with commas and no spaces (rgb(255,0,0);,hsl(210,50%,40%) !important,cubic-bezier(0,0,1,1);) keeps its repair line: a comma is read as a number mark only outside parentheses.font 'Inter ExtraBold'offersfont Interandheadings heavy, the rung nearest the weight in any form the weight table reads.astryx experimental theme editor: a hand-edited settings entry the editor refuses is offered only commands that unlock the theme. Aheadingsvalue saved with no axis is its weight half, soset <theme> headings <weight>orundo <theme> headingsreplaces or removes it; amodeorbaseentry put in the settings list is removed byundo <theme> mode(orbase), and nosetline is offered for it (those set the theme's own mode and base).astryx experimental theme editor: one reader takes every settings file and undo step. A null or other non-object entry gets the file refusal, never a crash, and the step back it names works. A damaged mode or base is read as meant by a change and recorded that way in the undo step, so undo works and the history is kept;like: "none"is no base. The folder names the theme: a missing or changednamein the file is the folder's. A headings value under the wrong half, an unknown half, or a half on another dial is refused with the undo that works, and a half listed twice offersset <theme> headings <word>lines that work. A dial listed twice by hand: set names every entry it replaces. A part in other letters or misspelt with--onlygets the command on that part,--onlykept. A did-you-mean follows the one typo rule (nothing for one to three letters). The theme-name rule, dashes included, is stated from one text in every refusal and innew's help.moreorlessat a dial's last step is refused with the other way. A built-in theme that is not installed is offered with its install line first. A value saved in another form (corners in rem, a fractional text-size) leaves the build current forcompile --check.preview <word>leads with a subcommand the word is a typo of, and offers a theme's pages only for a theme here.astryx experimental theme editor: text of a part that sits in the app's top bar is checked over the header's background. A part with a see-through background of its own (a segmented control's track, a ghost button, a top nav item) shows the header through it, so a dark header now warns when those labels do not read on it, including the light/dark/system switch the in-app preview puts in its top bar, which looks the same in an app.astryx experimental theme editor howholds its answers to what the theme shows now:- a bound already passed the way the words ask ("input borders thinner but at least 2px" at 1px, "the corners rounder but at most 4px", "borders thicker but no more than 0px", "the text bigger but no bigger than 12px", "the line height bigger but at most 1.2", "card padding smaller but no less than 64px") changes nothing and says so, never moving the value the other way; a part's border width is read from the token its border reads, and a way beside a bound on a length the part does not have ("cards wider but at most 300px") writes nothing;
- "headings tighter" is the headings dial's letter spacing, one rung from where it is, and "but no tighter than -0.01em" holds it there instead of changing the whole theme's spacing;
- "buttons 4px taller" reads the part's height, and "8px wider" its inline padding, half on each side;
- "selected rows lighter" steps the token Core paints a selected row with, in the mode named;
- "the header the same color as the sidebar" takes the page color a part with no fill of its own shows;
- "more colorful" and "less saturated" on a one-mode theme answer with the first vibrancy that moves the accents it shows the way asked;
- a value question on a one-mode theme tells the mode it shows, and says a mode it never shows has no value;
- "the accent color but lighter", "the danger color but darker" (with or without a comma before "but") make that color lighter or darker in each mode on a fill or a border, as on text;
- "the sidebar the page color but darker", "the header the card color but darker": the color of the part named after another is read and stepped, never changed itself.
- An experimental theme command with more than three examples opens its
--helpwith "Start here:" and its first three examples, before the options, so the first step is visible without reading every option. The full "Examples:" section stays after the options, as in every command's help. astryx experimental theme editor hownow reads these asks the way they are said:- Amounts with a softening word go the right way: "three times as soft" is a third of now and "half as soft" is twice as strong. "Corners half as small" makes them twice the size.
- "Exactly 36px high" is a height of 36px.
- "…and the text bigger" changes the theme's text, not the part named before it.
- A border color on a part keeps only the colors Core gives a status or focus. It no longer pins every variant back to its old color, so the new color shows on every variant.
- A part made more transparent or fainter moves from what it shows now: a disabled button's 0.5 opacity goes lower, never higher. Each variant's fill fades from its own color, in the state asked, and the part never gets a line it does not draw.
astryx experimental theme editor howchecks every command it suggests against the question: the command must make the kind of change the words ask for (a color for a color ask, a radius for a corner ask, padding or a size for a size ask, a border width, a weight, an opacity or a shadow), move the way they say from the value there now, and reach none or 0 for a removal. A command that does not is left out, and the answer says plainly what it could not work out; a value you typed is always taken as given.astryx experimental theme editor howsays what it writes. The words an answer repeats no longer end on a bare "when" once a state is read, and part names take their plural ("switches", never "switchs"); a keep said first ("keep the switches and the background …") ends at a whole verb. A color said as how something looks now ("too bright blue", "is still gray") is never written as the value, and a color said against the one it replaces ("navy, not bright blue") is one ask with no line about the other. Two parts listed with a word describing the second ("the info banner and draft badge") share the ask. A near color off a pure one ("never pure white") takes the theme's own neutral. A one-line look keeps its page, text and font ("green text on black, monospace"), and "text on black" reads the color under the text as the page.astryx experimental theme editor how:- An app's own pasted CSS variables (
--brand-primary,--brand-bg…) are read by the role their name ends in. "<color> text on a <color> page" sets the text and the page separately. - "luxury fashion brand: black and ivory" no longer reads black as the accent. On a dark-only theme, the page color takes no mode.
- Glass words ("frosted glass", "glass cards") set
surfaces glass. "tight dense spacing" gives tight spacing. "gridlines" are table cell borders. "big buttons" makes the buttons bigger. - "bottom border 1px #49454f" sets only the bottom side. "1px border rgba(…)" keeps the width. "dialogs with a 1px border" gives the dialog an edge of its own.
- "bigger, 17px" uses 17px, while "like 1 or 2 px" stays an example. "badges uppercase bold" runs both changes in turn.
- When a typed fill would leave a part's text below 4.5:1, a line beside it gives the text a color that reads in that mode.
- An app's own pasted CSS variables (
astryx experimental theme editor how --helplists the kinds of ask a question in plain words can be, each with examples it answers with commands (examples labeled "Asks how understands": a dial, a part's property by an amount or a value, a direction, a comparison, everything except some parts, a prohibition, one mode, a removal, several changes, a question about a value). A question it cannot answer points to that list, and--helpis the first of its next commands.astryx experimental theme editor how: borders made more or half as transparent change their color, never their width; two theme colors joined before one way ("the accent and danger darker") each take it; a ring said without focus ("cards: 1px ring #e5e7eb") is a ring at rest, a box-shadow in front of the part's own shadow (which stays), while a focus ring stays the focus ring; "the toggle group's buttons" are toggle buttons, never switches, and "the date picker's days" are the calendar's days; and an unknown word right before a part or after its possessive ("the zorp card", "the button's foo icon") is said and nothing is written.astryx experimental theme editor howreads a clause that only states a bound on a part, such as "never make buttons rounder than 12px", as a limit on the asks said with it, before or after them. The bound never becomes an ask of its own, and it never gives its part to those asks. Each answer that would build the part past the bound holds it there: it sets the part's own token after the answer's steps and says so. An answer that already keeps the part within the bound says that too.astryx experimental theme editor how: "inline", "block", "horizontal" and "vertical" name a padding side only beside the padding they qualify ("inline padding", "padding-inline", "padding 8px vertical"), never as a word of a part's name, so "inline code padding 4px" and "block quote padding 8px" set every side of that part.astryx experimental theme editor hownow:- moves only the control height of the size named when one is ("make the small buttons 4px taller"), on the part;
- reads a possessive owner's own element ("the dropdown menu's items") as that element, never the owner;
- treats a later "the shadows softer" or "the corners rounder" as a change to the theme's shadows or corners, never to the part named before.
astryx experimental theme editor how: a color bound ("darker but never darker than #1e40af") holds every color an answer writes, a color dial's seed included, and a see-through tint is held by its own color with its transparency kept, never turned into the opaque bound color. A part named on, inside or in a container ("links on cards") has its token set on that container, so it changes there only; one that cannot be kept there says so instead of changing it everywhere. "Outline buttons red" gives the outline look with the main button in red, never a border on every filled button. "All text 50% transparent" and "the text half transparent" set the theme's text colors at that opacity. A part's padding is read on its own pieces only (a table's cells, never a command palette inside a dialog), for value questions and comparisons alike.astryx experimental theme editor how:- "the buttons the color of the links" fills the buttons with the link color, instead of turning their text the accent color.
- A part's fainter or muted text, said with an owner ("the card's muted text") or a place, is that part's secondary text. "the card's fainter text lighter" changes how light that text is, not its transparency.
- "the row hovered and selected" means the row in both states at once; neither state is dropped.
astryx experimental theme editor how:- "the card's fainter text red" colors the cards' secondary text. A color after an ask on a part's text applies to that text ("the card text bigger and red"), and "fainter and red" gives a faded red.
- A word for a look before a part ("the borderless buttons", "the text-only buttons") means the button variants drawn that way, not a border to remove.
- "the destructive button the primary button color" uses the primary button's fill.
- "the dialog title red" colors only the title, not the subtitle.
- "a third darker", "darker by a third" and "half as dark" are read as the amount said, and "a third as strong" shadows are labeled softer.
- "the input's error border" means the error version of the input.
astryx experimental theme editor hownow decides one way, for every clause in an ask, which part it changes, in which state, and in which mode:- Part: a clause that names no part changes the part before it only when it adds to that part. That covers "with a 2px border", the part's own colon list ("cards: white background, 1px border"), "and darker", a state of the part ("; when focused a 2px ring"), and the part's own text color ("buttons blue, white text"). A font, text size, spacing or "surfaces" clause, a new sentence, or a comma item with its own look ("big buttons, thick borders") changes the whole theme. A page's text is the theme's text.
- State: "when off" on a switch changes its resting look and keeps the checked one, instead of changing every state.
- Mode: "in dark mode:" at the start of a sentence covers every clause in it. A mode said at the end of a run covers the run. Light/dark pairs never reach across a sentence.
- Light and dark colors: on a theme with both modes, a color that one mode can't carry is not written to that mode. This applies to a light fill whose dark-mode text would not read on it (cards, a button variant, a banner, a selected row), a dark card, and a light border. A color word said for dark mode ("subtle gray in dark mode") becomes that color's dark tone. Each answer says so.
- Wording fixes:
- "green text on a black page" now sets the page black and the text green.
- "muted text" and link colors that the dark page can't read go to light mode.
- "navy buttons" leaves alone the variants whose text would vanish.
- "softer corners" now means rounder.
- Show's missed list: a suggestion from show's missed list never contradicts the ask, and it comes after the ask's own answer.
astryx experimental theme editor howanswers more consistently:- No rounding anywhere: "no rounding anywhere", "square corners everywhere" and "… badges and switches too" also square the parts drawn as pills (
--radius-full 0px), and the answer names those parts. - A part and an aspect with no change ("toast background") say what to look at instead of "No match".
- Thick borders on everything: "thick black borders on everything" sets the shared border width and both border colors (inputs draw the emphasized one). It also adds a border to the surfaces that draw none (dialogs, popovers, menus). "thick borders" moves the width one pixel up.
- Status and focus colors: a border color written on a part keeps the colors Core gives it by status and focus (an error input's red border, the focus border).
- No rounding anywhere: "no rounding anywhere", "square corners everywhere" and "… badges and switches too" also square the parts drawn as pills (
astryx experimental theme editor how:- What a color is read on is the background, not the thing changed: "the warning color darker so it reads on the page" darkens the warning color until it stands out 3:1 against the page.
- A page color's second line also paints the main panel drawn over the page. Asking for the page color alone leaves the main panel as it was.
- "table header text uppercase 12px" keeps the 12px as the text size.
- "when inputs are focused, a 2px ring" is the inputs' focus ring.
- "only a bottom border" removes the other sides. "A slightly darker bottom edge" darkens that side's color only.
- "all text at least 7:1" checks the main, secondary and accent text.
- "large text" and "small text" make the text larger or smaller. "grayscale" and "no color" set vibrancy to 0.
- In a look typed as one line, "deep green" is a deep green, and a quiet color like sand becomes the neutral. "A theme that works in dark mode" no longer limits the colors to dark mode. "The app should open in dark mode" points to
<Theme mode="dark">. - A purpose ("so readers see which page they are on") is never read as a part. "Make text more readable" makes the text larger. "Headings a bit lighter" moves one weight step. A color named before a part ("the brown content area") describes how it looks now.
astryx experimental theme editor how: a color word is the theme's own shade where the theme has a family for it. Grey (gray, neutral) is a shade of the theme's grays, which every theme has, and another hue a shade of the palette family of that name; the shade is the one nearest the word's usual color, in each mode. A hue the theme has no family for, or a word with a shade before it ("light grey"), keeps its usual color.astryx experimental theme editor how: "2 steps more", "3 steps rounder" and "2 spacing units more" are that many steps (never a 2px or 3px value, never a "step" part); "avatars 24x24px" sets their width and height; a warmer or cooler accent moves only its hue (and says so when the accent is a gray), never the neutral grays; "headings 2-4" and "h2 to h4" change only those levels, each from its own size; variant words after except ("except transparent ones", "except success ones") keep that variant's own fill, never an overlay; a semi-transparent background is the part's own fill (never an overlay) mixed with transparent; "primary button text the same color as the secondary button text" takes that variant's own color; "bigger than 4px" goes past the bound from the value now, or says the part is already past it; and the answer check measures a part's color in the variant a command writes.astryx experimental theme editor howjudges a dial step by what it does, never by its own word: "more washed out colors" answersvibrancy lessagain. A typed value waives the way only for what it writes; every other value is still measured the way asked.- On a theme that draws both modes,
astryx experimental theme editor hownow sets a clearly dark card or surface color ("cards #0f1011", "dark cards") for dark mode only, so light mode never gets a dark card under dark text. If the same ask also gives that part its own text, as in "a navy header with white text", the look applies in every mode. A clearly light whole-theme border color ("borders #e3e8ee") is set for light mode only, so dark mode keeps its own border. Each answer says so and shows how to set the other mode too. - Fixes in
astryx experimental theme editor howfor themes that draw both light and dark modes, and for some common wordings:- Page and surface colors: a clearly light page or surface color (typed or named, such as "cream background" or "white cards") is set for light mode only, and a clearly dark one for dark mode only. The other mode keeps its own color, so its text stays readable. The answer says so and shows how to set the other mode too. A one-mode theme, or an ask that says "in both modes" or "everywhere", sets it for both.
- A part hidden by a new fill: when a part inside the one being filled would end up nearly the same color as the new fill (a primary button in a navy header), the answer names it.
- Link colors: a link color one mode's page would make unreadable (a dark blue on the dark page) is set for the other mode only, and the answer says so.
- Prohibitions: "never use pure black for button text" moves the button's text off black where it is black, instead of writing black.
- Later clauses: "make everything more compact", "text color #303030", "; 14px text", ", larger text", "; roomier spacing" and "; main text #f7f8f8" said after an ask about one part change the whole theme, not that part. A page's text is the theme's text, never the page.
- Trailing modes: a mode said at the end of a run of clauses on one part ("… white with a 1px border and a small shadow in light mode") applies to the whole run. In "black with white text in light mode and white with black text in dark mode", each half keeps its own mode and its own fill.
- Size words: a size word before the thing changed ("a small shadow", "large padding") sets the amount. It no longer picks the part's size variant.
- Show's missed list: a fill or text color the ask gives now comes before a line from show's missed list.
- Fixes in
astryx experimental theme editor how:- Status text weight: a status part's text weight ("the error banner's text bold") is set under that status.
- A part inside another part: "the dialog buttons" and "the toast buttons" mean the buttons inside that part. A part kept to a place ("menu items in the dialog", "tabs in the card") writes nothing and says why, unless a token on the place holds the change.
- One size named: "the medium buttons 36px tall" sets only that size's own control height. If the part data shows no control height for the size named, nothing is written. An icon's size is reported as unreachable, and the button is left untouched.
- More sizes and heights: "The small buttons taller" steps that size's own height. "The selectors 4px taller" moves each size's height. A height on the inputs ("24px tall") is set through the heights the inputs read, so they can shrink, while a text area keeps its rows. Parts inside another part ("inputs in cards") are kept to that part or not written at all.
- Borders: a thicker radio or checkbox border no longer offers one color for every state.
astryx experimental theme editor howchecks that a write shows what the question names. A state, a mode, a typed color, a removal, an except, or the thing to change (a shadow, a border, corners, padding, an on-color) that is said in a clause but missing from every step means the clause was not read. Nothing is written, and the answer says what was read and what was not. For example, "card shadows at 30% opacity" no longer fades the whole card, and "on-accent text black" no longer changes the main text color. Other readings:- Excepts said first: "except cards, …", "other than …" and "apart from …" before the ask are read as excepts.
- Lists with articles: "the blue, the green and the red ones" names each item.
- Removals: "remove X from A and Y from B" removes both.
- Kept states: a kept state keeps what Core draws there ("tabs blue except the selected one").
- States on part anatomy: a state goes to a part of the part's own anatomy only, never to sample content.
- Examples: a "for one, add --when" example stays in the answer's words. It is never listed as a step.
- One-word removals: "borderless", "un-outlined" and "shadowless" are removals.
- "Ones" in a list: "primary buttons and the ghost ones" names both.
- Mode pairs: "the accent darker in dark mode and lighter in light mode" answers both halves.
- Keeps said as unchanged: "…, buttons unchanged" is a keep.
setreads an option written after--with the reason and the line without--.undoreads an unquoted list of settings ("undo t accent, corners and spacing") the same as a quoted one.astryx experimental theme editor howkeeps excepts apart truly:- Excepts on another axis: an except on another axis ("buttons blue except the small ones") says it cannot be kept apart. Before, it said there was nothing to keep, and the excepted buttons changed anyway.
- Comma-led excepts: an except set off by commas is kept, as one with no part named is.
- Excepts after a list: a part-less except after a list reaches every part of the list.
- Kept parts of a group: a part of a group kept from a one-mode or status step is pinned in each status and mode of that step.
Other readings:- Mode pairs: a mode pair is one subject wherever its part is said ("the text darker in dark mode and lighter in light mode on cards").
- Text already at its limit: text that is already as light or as dark as it goes says so, instead of answering "no match".
- Heading levels: "keep h1" is a keep.
- Neither/nor: "neither a border nor a shadow" reads its articles.
- Removals: "from menus and from tooltips" takes the thing of the item before it.
- Lists of parts: every ask after a list of parts reaches each part.
- A second ask with only its value: "rounder and red" and "bold and red" are two asks on the same part.
- Neither/nor with parts as the subject: "neither cards nor dialogs should have shadows" removes the shadow from each part, and "… should be rounded" squares each one.
- Excepting an item of a list: an except naming one item of a list leaves that item out of the change.
- Modes said first: "in dark mode …, in light mode darker" answers both halves.
- Indicators: "indicators" are the check and radio indicators.
- "Every" in removals: "remove every shadow" reads as "all shadows".
astryx experimental theme editor hownow judges a kept look by what it draws. In "make the inputs bolder but keep the error inputs as they are", the error inputs had no weight rule of their own. Nowhowwrites back the weight they inherit and answers, instead of refusing. A kept variant that draws no border in any of its looks ("remove the border from cards except the muted ones") is kept without writing a border back on it. A word between a part and what changes that names no part, state, variant, aspect, color or known modifier ("the card zorp border") now gets "no part or word called zorp", and nothing is written.astryx experimental theme editor howguards its answers, so a phrasing it was never taught gives a named refusal instead of a wrong write. Guards:- Direction: an ask that makes something fainter, less visible or more see-through, or removes it, never adds or strengthens a border, outline, ring or shadow anywhere. A way asked of a line never adds one to a look Core draws without one. Each such step is left out and named.
- Keeps: every kept scope is held after the whole in-order sequence, and that sequence runs the except with its keeps.
- A compound except keeps that variant in that state only.
- An except's mode or state stays with its own clause.
- Several excepts, each with its own mode, are each kept in that mode.
- Questions: a question with no clause that asks for a change never writes.
- Unknown parts: an unknown part is said, never read as the whole theme or given the part said before it.
Readers the guards point to:- Fainter borders: a fainter border is its color at a lower alpha. A part that draws no border says so.
- See-through text: see-through text is the text colors at a lower alpha, never the page.
- Focus rings: a see-through focus ring is its color at a lower alpha.
- Table row dividers: thicker row dividers are the width token the cells read, set on the row.
- Blur: "blurrier" shadows have more blur, not more strength.
- Removal lists: the items in the middle of a removal list keep its thing.
- Links in a place: links in a place take the link token set on that place.
- Outline buttons in a color: outline buttons in a color get no fill, with that color as their border and text.
- A held theme color: a bound holds a theme color's dial and keeps a tint's alpha.
astryx experimental theme editor howreads every shadow color through the one shared color reader, so themes that write 8-digit hex shadow colors (butter, chocolate, gothic, matcha, stone, y2k) get an answer to "make shadows darker", "make shadows lighter" and "the shadows are too strong", each color's alpha scaled in the form it was written.astryx experimental theme editor howchecks a kept look against what it drew before, wherever Core wrote it (beside the variant and size), and compares a color token by name. A status except on inputs ("make inputs blue but keep the error border", "remove the border from inputs except error inputs") now answers on every base instead of being refused. An input that has no error look of its own takes no pin. In an except or a keep, "invalid" is the error status.astryx experimental theme editor howreads "like" and "as" as a comparison only in comparison forms ("as round as buttons", "the same padding as cards", "rounded like buttons", "like the dialogs are"): "make components like dialogs and drawers rounder" changes those parts, and "use red as the button background" sets that value. A lighter or darker color role steps its dark half the same way from its own value, and the answer check holds colors (text and borders for contrast in dark mode) and sizes to the asked way in both modes. "A light tint of the accent" is the accent mixed with transparent, never the full accent.astryx experimental theme editor howreads more of each ask:- Links in a container: "links on cards", in a mode pair too, sets the token a link reads on the card, never app-wide. Before, one half of the pair changed card text instead of links.
- Lookups: every lookup is a command that runs.
Other readings:- Removals: in "the shadow from dialogs and popovers", the items after the last "from" join it.
- "Give neither … a thing": "give neither the cards nor the popovers a border" removes the border from both.
- Compound excepts: "except the disabled secondary ones" keeps that variant in that state only.
- An ask after an except: "taller except the large ones and bolder" answers both asks, for every part of the ask.
- Lists matched to a reference: "the header and the sidebar the same color as the page" matches each item to the page.
- An except said before its ask: "all text except headings red" reads as one ask with its except.
- Steps that change nothing: a step that changes nothing is left out of an in-order sequence and named there. The rest still runs.
- Step counts: "2 steps rounder" stays two steps in the sequence.
- Keeps after a comma: "…, keep h1 and h2" is a keep.
- Shadow excepts: "remove every shadow except on cards" keeps the shadow tokens on the card, so elevated cards keep their shadow.
- A color in a keep: "keep disabled ones gray" names the look they keep, not a variant.
- Excepts in one mode: "except in dark mode" stays with its own clause, and "except the dialog in dark mode" leaves the dialog out in dark mode only.
- Prohibitions of a look: "never use rounded corners on buttons" before an ask keeps the buttons.
- Tone words for text: "card text dark in light mode and light in dark mode" reads dark and light as colors.
astryx experimental theme editor howreads a whole look typed as one line ("a calm, Linear-like dark theme with a violet accent", "cream background, terracotta accent, serif headings", "a high-contrast compact enterprise theme in navy"):- Each part it understands gets its own line: the theme's mode, a named color for the accent or the page, density, contrast and fonts. A color on its own ("navy") is the accent.
- Words that no setting covers ("calm", "Linear-like") are listed as not used.
- Design color names are understood (terracotta, sage, rust, mustard and others). A blue-gray is a gray with a little blue in it.
- A complaint describes how a part looks now ("the error toast is too bright red; make it calmer"). "calmer" makes a color less saturated. "the main content area" names the page's main panel.
- A status color on one part ("the info banner navy") also offers that status color for the whole theme.
- "sharper corners, almost square" gives small corners.
- "the accent text #0033aa" sets the accent text color, not the main text.
- "a rounded font" is a typeface and leaves corners alone. A color typed with "off-white" wins over it.
- "light only", "dark only" and "no dark mode" set the theme's mode.
- "a right-to-left app" explains that Core mirrors itself once the app sets
dir="rtl", and changes nothing.
astryx experimental theme editor how: "<part> match the theme" answers with the linesshowlists for that part under missed (what the theme's own changes should have reached on it), each checked as set checks it, and says so when nothing was missed. A color named like another part's ("grey like the dialogs", "the same grey as the page") is that part's color, read from it, and the other part is never changed. "Hard", "no blur" and "flat" shadows keep their offsets with no blur, never no shadow.astryx experimental theme editor howmeasures more of its answer: every variant and state a touched part shows (and only the mode a one-mode theme shows), the base theme's own rules for a variant, a kept variant in every state, and a painted background whichever way it is written; the plain answer of a clause with an exception is held to the exception too. A part whose variants read colors of their own ("button text darker", "buttons lighter") gets one step per variant from its own color, in each mode. It also answers: headings smaller (each level's own size when the type dial would change weights), "the text 2px bigger", "the card border 1px thicker", sizes written "48px by 48px", heading ranges for any property ("headings 1 through 3 bolder") and an excepted level ("all headings red except h1", which keeps h1 as it is), a heading level past 6 (said), "the dialog the same color as the page" (the page's own color; the page is not changed), "no shadow and no border on dialogs" (both on that part), "0 steps more" (nothing), "everywhere except", a backdrop more see-through (a lower alpha), a dialog shadow darker, lighter or with no blur from the shadow it has, "remove the card background" (transparent), "thicker borders" from the width there now, a token pointing at another token, a dark-only theme's accent from its dark value, "rounder cards without shadows", "slightly lighter than black", and value questions about a part's font, shadow, opacity and fill, in the variant and mode they name.astryx experimental theme editor howmeasures its answer before it gives it: each suggested command is built in memory with the theme (the same buildsetmakes; nothing is written), and the values the touched parts show, in light and dark, must change the kind of thing the question asks, the way it asks (a lighter fill is lighter in both modes, while text and borders step for contrast, so in dark mode they go the other way; a removal reaches none), while parts it excepts, compares against or forbids show the same values. A command that does not is left out, and the answer says plainly why. It also reads "besides", "save for", "but keep X as they are", "X excepted" and "without changing X" as except; "as well as" as and; "compared to" and "versus" as comparisons; "don't let X get smaller" and "never round the inputs" as keeping X; "X shouldn't be so small" as an ask; "remove the padding and border" as two removals; "black on secondary buttons" as text; "less sharp" and "less thick" as their opposites; value questions about space, gap, shadow, background and font size, and a question followed by an ask; a setting pasted with a colon as its lookup; "heading text lighter"; "the focus ring lighter" as its color; and a lighter or darker accent in both modes.astryx experimental theme editor howandsethandle one-mode and scoped asks more exactly.- Shadows per mode: a part's shadow given for one mode keeps every layer the part shows. Their colors stay in the other mode and go transparent in this one, and the new layers' colors show in this mode only. Each mode paints exactly what it did, or what was asked.
setstill takes--modeonly for colors. - Core's shadow layers: a part whose shadow Core builds from layers of its own (a card's selection ring and elevation) keeps those layers under a theme's shadow, so a card shadow, or a shadow of none, never drops the ring.
- One-mode removals:
- "remove card borders in dark mode" makes the border color transparent in dark mode.
- "no shadows in dark mode" makes the shared shadows transparent in dark mode only.
- A border width in one mode is refused, with the reason and the border-color line that does work.
- Mode words:
- Mode words name a mode, never a direction: "darker in light mode" is darker.
- A mode word that scopes another ask ("more colorful in dark mode") never changes the theme's modes.
- See-through colors: a see-through role color, such as a 10% wash, stays see-through when it gets lighter or darker. A border made lighter or darker in a named mode reads that mode's page.
- Role words:
- "the accent text" is the accent text token, never the main text.
- "labels on accent buttons" are the accent-filled variant's labels.
- Corners by a length: a corner step in px starts from the radius the part shows. It passes
set, and a pill stays a pill. - Gradients: a gradient of one named color uses that color.
- Keeps and excepts:
- "…but keep the inputs" keeps the inputs.
- An except list keeps every variant, state and heading level it names ("except primary and ghost buttons", "except hovered or disabled", "except h2 and h3").
- Headings: headings made bigger never grow the body text, and headings by a px amount move each level.
- Comparisons with the page:
- "darker than the page" keeps each card variant apart.
- "as dark as the page" takes the page's color.
- No undo of a removal: a removal the theme already has is never undone.
- Swaps: a swap of two role colors swaps each mode, and a named mode swaps only its own colors.
- Shadows per mode: a part's shadow given for one mode keeps every layer the part shows. Their colors stay in the other mode and go transparent in this one, and the new layers' colors show in this mode only. Each mode paints exactly what it did, or what was asked.
- Fixes in
astryx experimental theme editor how, mostly for themes that draw both light and dark modes:- Page color words: a page color given as a word ("make it gray", "make the page pink") becomes that color at each mode's own page lightness. Before, one mid-tone page was used for both modes, under text that could not be read on it.
- Borders: a light border on a part keeps that part's own dark-mode border color (an input's emphasized border), instead of the theme's faint line.
- Unchecked and unselected:
- "when off", "unchecked" and "unselected" keep the checked or selected look as it draws (a switch's accent), instead of writing the off look back onto it.
- If the ask says the selected look itself ("selected tab text white, unselected tabs gray"), each look is written as said.
- Reading the ask:
- The color a complaint names ("the pink page background is a bit much, …") is how the part looks now, never a value.
- "X instead of outlined" takes that part's own outline away, never every border.
- "table header row" means the header cells.
- A ban on black text after a page clause is about the text.
- A state with a value ("primary hover #4338ca") no longer passes its state to the next clause.
- A token list item said subject first ("text #111827") is the theme's.
- Button variants: when a fill like "navy buttons" goes to some button variants only, the destructive button keeps its red, and the answer says so.
- Color words for dark mode: only a color word the ask actually says ("subtle gray in dark mode") is swapped for its dark tone. A color computed from a direction ("make the card background darker") is never swapped.
- Links: a link color under 2.5:1 on one mode's page is set for the other mode only ("dark red links").
astryx experimental theme editor howreads a motion effect apart from a speed:- Effects: "fade in tooltips" and "slide in dialogs" now say what the part does now, read from Core's own animations and transitions (the tooltip fades in already). Nothing is written: the editor sets how long motion takes, not which effect a part uses.
- Speed: "faster" and "slower" step the motion the part has (a tooltip's animation) from the time it takes now.
astryx experimental theme editor howreads a negated word as what it says:- Negated words: "un-rounded", "non-rounded" and "unrounded" buttons are square, and "un-bold" headings are regular. "border-less" and "shadow-less" are removals, with or without the hyphen.
Other readings:- Comparisons: "as round as the accent" names nothing with a shape, so it is refused with that reason.
- Removals: a list of any length gives each item its own "from", so every item is removed.
- Kept sizes: "bigger except the small ones" keeps the small size only. When a keep would take the whole change back, the answer says so instead of reporting it as done.
- Mode pairs: the main text gets both halves of "darker in dark mode and lighter in light mode", as do typed colors per mode.
- Heading levels: "every heading except h1 smaller" leaves h1's own size token out.
- Titles: "dialog heading text" colors the dialog's own title.
- Neither/nor: "neither rounded nor bordered" negates both words.
- Fully rounded: "fully rounded" is the roundest rung.
- Keeps said first: "keeping cards, …" and "keep the accent, …" said first are keeps.
- Except answers: an except answer names the whole ask it belongs to.
- Mode splits: the second half of a mode split keeps the part phrase and its state ("selected tabs red in light mode and blue in dark mode").
- Color words: "dark gray in light mode" is a color, not a mode.
- Excepts in one mode: an except holds in a one-mode answer too.
- Ghost buttons: a hovered or pressed ghost button steps its own wash, never the primary's fill.
- Check marks: "check mark" is the mark drawn inside the box, colored with its text color.
- In
astryx experimental theme editor how, a plain fill color asked of a part that has colored or status variants now changes only its neutral variants. "white cards" changes the default, transparent and muted cards, and "blue tags" changes the neutral badge. Each colored or status variant (the blue card, the success badge) keeps its own color. The answer names those variants and gives a line to change each one too. A color that is worked out from another color, an answer that already keeps a variant apart, and a part whose variants are roles (a button's primary, secondary and ghost) are unchanged. astryx experimental theme editor howreads more phrasings through one shared grammar:- Keeping a part as it is: "keep cards as they are", "leave inputs alone" and "don't touch the dialogs" all use one keep grammar, whether they come beside an ask or alone.
- Density words: cramped, airy, dense and the other density words come from one table that every density reading uses.
- A fill's color after "with": "selected table rows tinted with the accent at low strength" gives the selected state's accent wash.
set vibrancynow counts a color by whether its shades change. A warm or cool gray (neutral #78716c) takes vibrancy steps. A pure gray is refused, and the message names the color and says why.astryx experimental theme editor howreads each ask through its shared readers and holds every answer to what the theme shows.- Fills: a fill of one color is written as
background-color, so Core's hover and press tint stays. - Keeps and excepts: one reader takes every way of keeping something as it is, in any position, and joins them into the ask's one except list. That covers "…, but keep cards as they are", "keep the dialogs as they are and …", "…, not the primary ones" and a second keep.
- A button group cannot be kept apart from the buttons in it, and the answer says so.
- A removed border kept when focused keeps its whole border.
- The shared border width is kept as the token on the part.
- Amounts and bounds:
- A decimal comma is a decimal ("1,5 times").
- An amount with a bound is held to the bound ("8px more but at most 20px").
- "Don't make X rounder than 8px" is that bound.
- Removals: "the X and Y of cards" stays on the cards, and "cards, buttons or inputs" names each part.
- Asks with no change: a swap is done exactly or not at all. A part and an aspect alone ("card corners") write nothing.
- Modes: "at night" and "night mode" are dark mode. A one-mode shadow on a part moves only that mode. A part that shows no shadow at rest takes a one-mode shadow. The
--moderefusal for a shadow now says that its color can still differ by mode, through light-dark(). - Colors and constraints:
- "Never use pure white" moves only what is pure white.
- "With readable text" pairs a label that reads on the fill in each mode.
- Vibrancy is measured on the accent wash too.
- A typed color wins over a color word: a typed shadow color, and a typed color for text on the accent.
- "A lighter purple" is that hue's light shade.
- Named dial rungs: "make corners small", "spacing compact" and "text size large" are those rungs.
- Comparisons and measured values:
- "4px less round than buttons" is answered.
- A value Core writes from several tokens (a card's padding) is measured whole.
- A px amount on a part starts from the radius the part is built with.
- Variant pairs need two real variants.
- No editor theme yet:
howstarts from, and measures against, the theme the app shows now.
- Fills: a fill of one color is written as
astryx experimental theme editor how:- A one-line look written as a list ("clean and trustworthy like a bank: blue and gray, lots of data on screen") takes each piece a setting reads and names the words none reads. "lots of data on screen" means compact spacing. "dark purple theme" sets dark mode and a purple accent. "at night" means dark by default, and "easy to read" means larger text. "pastel pink" is a light pink, "deeper blue" is a dark blue, and "red only for alerts" sets the danger color. "dark mode first" works like "dark by default".
- "make the blue a bit darker" changes the theme color with that hue.
- "buttons medium weight" sets a weight, not the medium size. "headings semibold, not bold" is one ask. "large bold headings" and "bigger, bolder headings" also make headings bigger. "table headers uppercase 11px" keeps the 11px. "use the system font" sets the font.
- A border asked for one mode on a part that draws its own shadow becomes a border whose color is transparent in the other mode.
astryx experimental theme editor set: a page background on the app shell keeps a background a setting gives the main content area, whichever was set first.astryx experimental theme editor howreads every list through one list grammar:- Variants and states: a list of any part's variants or states names each item, whether it comes before the part ("blue, teal and red cards"), before "ones", with an Oxford comma, or after "when" ("orange when hovered or pressed"). A variant name in a list is never read as a color to paint.
- Parts: a list of parts ("buttons, cards and inputs rounder") gives each part the ask.
- Excepts and keeps said first: an except before the ask ("make everything except buttons rounder") and a keep said first ("without changing buttons, make everything rounder") are read as excepts of the ask. The change alone is no longer offered next to an except answer.
Other readings:- Parts: A corners step on a group leaves out the members already at that end (checkboxes rounder leaves out the radios, which are fully round already). "Card titles" and "dialog titles" color their heading. A state that only a part's items take ("side nav selected items") goes to the items. "Outlined in <color>" is a border color. "Padded" is a spacing word, and "less padded" or "less roomy" is tighter. "Drop-down" reads as "dropdown".
- Corners: on a pill base, a kept variant keeps the base's pill.
- Modes: "in dark mode only" scopes the ask to dark mode, and never makes the theme dark-only.
- Shadows: asks how cannot measure get a true reason. A softer shadow on a part the editor has not seen drawn is refused. A one-mode card shadow change says the card draws no shadow of its own at rest.
astryx experimental theme editor howreads more of each ask the way it is said:- Unknown part names: a word that names no part, in the part's place ("the zorp padding", "from the blorp"), is named in the answer, never changed for the whole theme.
- Status excepts: an except by status ("except error inputs") keeps that status's border on each input that draws one. An input that draws no border of its own is left without one.
- Fainter text on a part: a part's text made more transparent, less visible or fainter is its text color at a lower alpha, never the part's opacity. A toast's text uses the on-dark and on-light colors its surface gives it.
- Danger badges: "danger badge" is the badge's error variant.
- Separators: "separator" is the divider.
- Keeping the focus ring: "and keep the focus ring" is a keep.
- Outline buttons on hover: "outline buttons blue on hover" colors the main button's outline in that state.
- Tokens: "tokens square" changes the tokens.
- Text on a part: in "the text on primary buttons 4.5:1", the buttons hold the text; they are not the background it is measured against.
astryx experimental theme editor how:- An "all of it, in order" answer leaves out any step that would change nothing on its own. Writing such a step would lock that setting in place, so a later dial change would not reach it.
- "no heavy shadows" removes the shadows without also saying nothing was written. "Heavy" before shadows or borders is about their strength, not the font weight.
- Asking for a text color a part already has says it is already that color, instead of giving an unrelated reason.
astryx experimental theme editor howreads a see-through color's alpha with the one shared color reader, so anrgba(),hsla()or#rgbaoverlay gets more transparent or more opaque as asked, and the check measures it the same way. After a removal, a noun with an adjective ("rounded corners") is an ask of its own: "no shadow and rounded corners on cards" removes the card's shadow and gives it round corners.astryx experimental theme editor howanswers from what the theme shows on bases with rules of their own. An except keeps what the part shows: a whole-theme corner change pins the corner token on the part (a button group keeps its square joins), each heading level or variant with its own value keeps it, and a kept hover keeps its fill under Core's tint. A one-mode theme answers only for the mode it shows and never adds a mode. A gradient takes the colors named, in order. A text-size step starts from the base's body size, a variant's own literal fill is stepped from, and "more colorful" keeps each mode's accent hue. "Darker than the page" holds the page as a bound in each mode. "Remove the card border and shadow" removes both, "no bigger than 4px" is a target, a part's own tokens and its base rules count in the measured check, lighter or darker text with a mode named is read the same way by the answer and the check, a shadow typed for one mode goes into light-dark(), a length typed with no way is never a spacing step, and a color clause after an ask ("focus outline on text inputs, pink #db2777") is that ask's color.astryx experimental theme editor howreads more questions through its shared readers:- Lists: a two-item list of variants or states before a single ask names each one for that ask: "primary and ghost buttons rounder", "hovered and pressed buttons orange", in an except list too. "except disabled buttons" keeps that state. An except covers the whole ask before it. A prohibition said before the ask ("never round the inputs; make everything rounder", "don't make cards rounder, make everything rounder") is read the same as one said after it.
- One-mode shadows:
- A one-mode shadow on a part reads the shared shadows to their layers.
- It refuses with the true reason when the other mode is unknown, or when nothing of the part's own is there to remove.
- Ringed parts: a resting shadow, or its removal, is not offered on a part that draws its hover and focus rings in its box-shadow, in either mode.
- One-mode lines: a line the part already draws (a border, one side of it, an outline) takes its color by mode. When
set --moderefuses such a line, it now names working steps instead of ones that repaint the other mode. - Accent colors: on a theme whose modes show a color in different hues, or that shows only dark mode, a lighter, darker, warmer or cooler accent moves each mode's colors from their own values.
- Swaps: swapping two role colors also swaps their text, icon, wash and label colors in every mode.
- Corners: comparisons read the radius each part is built with (stone's pill buttons). A button group's corners step by a px amount.
- Gradients: gradients named by theme colors ("from the accent to the danger color") use those colors.
- Hyphens: a part or phrase written with hyphens or underscores ("focus-ring", "table_row") reads the same as with spaces.
- Other readings:
- A text-only part's color is its text color ("the top nav heading white").
- "What color is the header" answers its fill.
- "Bigger but no more than 20px" takes one step of the theme's scale, held to the bound.
- "Everything serif except headings" keeps the headings' font.
- "The hover tint stronger" changes the shared hover wash, not the page.
- "The body text 1px bigger" steps the text size.
box-shadow noneon a card now also removes Core's elevation shadow. The selection ring stays.astryx experimental theme editor howreads a second item after a removal as a removal only when it carries its own removal word or is a plain removable noun ("no shadows and borders"); a noun with a comparative or an adjective is an ask of its own: "no shadow and rounder corners on cards" removes the card's shadow and makes its corners rounder, and "no border and bigger padding on cards" gives more padding, never none; the removal stays on the part named.astryx experimental theme editor hownow writes nothing for an element named in a place it cannot be kept to ("the dialog's buttons rounder") and says why, instead of changing every such part. An answer that does hold in the place, such as a color token set on the card for "the card's links", still answers. A place's own element that Core draws on its own is answered on that element. "The controls 40px tall" and "all controls taller by 4px" move every control height together for the whole theme, each size by the same amount.- Fixes to
astryx experimental theme editor how:- A possessive owner of several words ("the dropdown menu's separators") is read as where the change goes, and the menu is never painted. A part's own divider ("the menu separators") is Core's divider, so the answer changes every divider and says so, instead of refusing.
- A height change in pixels ("4px shorter", "2px taller") moves each control-height token the part reads, on that part only, so every size keeps its own height. A height value on inputs ("40px tall") is a minimum height only, since a text area takes its height from its rows.
- An error or warning border made thicker keeps the color it reads under that status.
- A later clause about a role color or a dial ("… and the accent darker") changes that color or dial. It never takes the part named in the clause before.
astryx experimental theme editor how:- "the cards rounder and the gizmo red" says there is no "gizmo" instead of painting the cards.
- "the buttons the same color as the links" uses the links' text color.
- "the dividers the card border color" uses the card's border color and leaves alone the divider color that already matches.
- "the muted text in cards fainter" fades only the cards' secondary text.
- "the table row dividers thicker and blue" changes the color and explains why the width stays.
- "never redder than #ff0000" is said to be unenforceable (only darker and lighter limits are held) instead of removing the cards' fill.
- "how round are the cards now?" reports a radius set on the cards themselves.
astryx experimental theme editor how:- A color named after another part uses that part's color in the status or variant you name: "the color of the error banner", "the same color as the success banner", "the color of the danger buttons". The other part is no longer changed, and the reference doesn't decide what changes: "cards the button color" fills the cards.
- "the buttons as round as the inputs" says they already match instead of offering a line that set refuses.
- Value questions read a base theme's own colors and any of a part's own options: "what color are error toasts?".
- "the card text 25% of its opacity", "a third fainter" and "transparent by 40%" are read as amounts on the text or border color.
- "the secondary text on cards lighter" changes the cards' secondary text.
- "them" refers to the parts named just before it.
- "remove the shadow from everything" no longer reads "remove" as a part name.
- A mode with a typo is read wherever a mode is named, including before a comma and in "(drak)".
- "the open select" uses its open state.
- "the active toggle button darker" changes the toggle in that state.
- Keeping a status or a focus ring as it is works per input type and in one mode.
astryx experimental theme editor how:- A fraction is read the way it's said, before or after the direction and in words or figures: "two thirds fainter", "fainter by a third", "1/3 fainter", "a fifth fainter", "a third more transparent". A fill made "20% more transparent" keeps 80% of its color.
- A color named after another part with its status or variant ("the error banner color", "the success badge color", "the color of the muted card", "the color of the destructive button") uses that version's color and changes the subject in full.
- A base theme's own style for a variant counts first: butter's transparent secondary button shows as transparent. A transparent fill used as a color gives the color it draws next (its outline).
astryx experimental theme editor howreads more asks the way they are meant:- A bound limits the asks of its own kind said with it. "never rounder than 8px; make the buttons and cards rounder" holds the buttons and cards and leaves the rest of the theme alone. "the cards bolder, but never rounder than 8px" still makes the cards bold. A size bound holds each heading size it would pass, and a part already past a bound is left as it is.
- A color bound said by its color alone ("darker in dark mode, at most #000000") keeps the ask's mode. A held color keeps its own hue. A color setting past the bound in one mode is written only for the other mode.
- A contrast ratio "on muted cards" or "on the muted background" is measured against that background.
- Amounts are read as typed: "20% fainter" (80% of the border's strength), "the card background more transparent" (its fill, not the whole card), and "the text 80% opaque".
- Questions answered from what the theme reads: a status banner's background, the focus ring's width or color, and how thick dividers are.
- Typed tokens with a direction ("--color-accent and --color-error darker") move each token from its own value.
- "the page rounder" and "the page font Georgia" change the whole theme, not the page background.
- "the emphasized border", "the muted text" and similar names change that border or text token.
- "dividers thicker and red" does both.
- "radio circles red" colors the radio's circle.
- "transitions faster" and "animations 1,500 ms" change motion.
astryx experimental theme editor howreads more asks as meant:- "the card text 30% fainter" lowers it by 30%.
- "twice as short", "half as tall" and "twice as tall" change each height the part reads by that amount, instead of one spacing step.
- "expanded" means the part's expanded state, and "pressed" a toggle button's pressed state (a button's press is still its active state).
- "what is the height of buttons?" and "how tall are the buttons?" are answered.
- "the button corners twice as tight" changes only the corners.
- An exact border width ("half as thick") leaves the borderless styles borderless, as "thinner" does.
- A mode with a typo that keeps its letters is read wherever a mode is named: "in drak mode", "ligth theme", "(drak)", "[dark only]".
- Typed tokens each with their own direction ("--color-accent darker and --color-error darker") work.
astryx experimental theme editor how:- A text part colored like a filled part uses the fill it shows: "the headings the color of the danger buttons", "the links the same color as the danger buttons". A named paint like "the error inputs' border" uses that paint.
- "the transparent buttons" means the button variant drawn with no fill, not a fill to remove.
- A role the part doesn't have ("the success toasts", "the selector's primary variant") gets a "no such type/variant" answer instead of changing every one.
- "transparent by a quarter" and "a quarter more transparent" on a part keep three quarters, and "the text fainter" works theme-wide.
- The focus ring of one variant stays on that variant.
- Two exceptions joined by "and" ("except the disabled ones and the error ones") keep each one.
astryx experimental theme editor how: a part's value "equal to" (or "identical to") another part's takes that part's value, as "the same as" does, and says so when that part has none to read. "Make the text 4.5:1 against the page" moves the text until it measures that ratio against the page, which is never changed (links too); text that measures it already is kept. "Never taller than 40px" is a ceiling, like "no taller than". A color bound ("darker but not darker than #1e3a8a") holds every color the answer writes, mode by mode, or says the part is past it already; it is never read as the color asked for. A table's lines and padding are read on its cells: a border ratio sets the token they read on the table, and "how dense is the table" answers with their padding. "What is the shadow" lists the shared shadow steps.astryx experimental theme editor how: after a contrast ratio, the part named after "on" is what it is measured against and is never changed ("the input border 3:1 contrast on the card"). A status banner's text steps its own status's text color, as its background does. A part that reads a value from several tokens (a heading's weight, one per level) answers each value. The page is the whole theme for a dial ("the page density compact"), and its colors are its body colors, so "equal to the page background" and "as light as the page" read them. "As dark as dialogs" takes the dialog's fill. Striped table rows step the color Core paints the stripes with. "Outline buttons thicker" keeps the width change beside the outline look. A length bound on the corners dial ("never more than 8px") holds every radius the dial writes.astryx experimental theme editor howreads every removal lead ("no", "without", "remove the", "drop", "get rid of" …) from one shared list: "without shadows and rounder corners on cards" removes the card's shadow and makes its corners rounder, never every shadow in the theme, and "remove the border and bigger padding on cards" gives the cards more padding. A typed mode word such as "constructor" is never read as a mode.astryx experimental theme editor howreads a removal in a clause from the same shared list of removal leads as its rewrites ("strip", "nix", "scrap", "without the" included): "strip shadows from cards" removes the card's shadow, "nix the shadow and rounder corners on cards" removes only the card's shadow and makes its corners rounder, and "no shadows and borders on cards" removes both, as the "without" form does.astryx experimental theme editor how: "make the table row dividers thicker" writes nothing and explains why. The cells draw the row line at a width Core sets per render, so any width the editor could write would also thicken the borders of the controls inside the row (checkboxes, buttons).astryx experimental theme editor how: table row stripes are answered with the stripe itself where Core marks it on each body row (--when parity:oddorparity:even). "zebra rows", "striped tables", "alternate row shading" and "shade every other row" (the stripes' names are read from the doc of the prop that turns them on) stripe every data-driven table on Core's own (even) stripe with the theme's stripe color; an ask naming a stripe ("odd rows #f9f9f9") sets that stripe and clears Core's other stripe on striped tables; "no stripes on even rows" takes that stripe away. Before, "zebra rows" and "striped tables" said set had no condition for every other row, "alternate row shading" and "shade every other row" were not read as a fill, and "odd rows <color>" colored every row.set --whennamesparity:odd/parity:even, with a zebra-rows example.astryx experimental theme editor howreads a mode phrase as no way for the shadows: "make shadows darker in light mode" makes the light-mode shadows stronger. A light-only theme asked about dark mode (or a dark-only theme about light mode) is told it has only one mode, whatever form the shadow answer takes.astryx experimental theme editor howscales a named mode of a shadow written as one value by giving it a light-dark() pair, so "make shadows darker in dark mode" on themes such as chocolate or gothic changes the dark shadows and keeps the light ones. A shadow answer that would look the same as now (a color already at full strength) is not offered.astryx experimental theme editor howreads each ask through one shared reader and holds every answer to what the theme shows. A kept variant or state is pinned from the base theme's own rule (a kept hover keeps Core's tint, as a variant's fill is its background color). A color word before a part names that variant ("make blue cards rounder") or is refused when the part has none ("red buttons"). One removal-list reader takes "take away the card's border and shadow", "remove the card border, shadow and background" and "remove the dialog's shadow and the card border". "dark-mode" is "dark mode". "at most", "no more than" and "a maximum of" are limits, and a limit already met changes nothing. A button's radius is written as its corner token, so button groups keep their square joins. A one-mode shadow on a part that draws a shadow in the other mode (a card's selection ring) is refused. A part given a role color keeps a readable label in every variant. Vibrancy is measured on the accent colors the theme shows. State excepts ("except disabled", "keep disabled ones as they are") go through one state reader; an except set cannot keep, or a text size that differs by screen, is said, and the plain answer is not offered. A step aimed only at an excepted variant is left out. "Darker than the page" steps past the page in each mode; a page reference is never written. A link that reads a shared text color keeps it. "letter-spaced" is letter spacing, and "side nav section headings" is the side nav heading. A refusal's own command is offered when it does what was asked, and--atwithout a picture names a command that runs.astryx experimental theme editor howreads mode phrases, bounds, shadow strength and prohibitions each through one shared reader, and holds every answer to the measured check: "darker … in light mode" gets darker; "weaker" shadows get softer; "at least 2px", "under 40px" and "no bigger than 12px" hold the bound from the value now; "…, in dark mode" and "light mode #eee, dark mode #222" scope each value; "but leave inputs alone", "don't touch inputs" and "keep their hover the same" keep that part or state; kept parts are checked in every variant and level; a token typed with a part stays on that part; "blue card background" is the color, not the blue variant; page gradients keep the colors named; thinner borders step down from the width now; and value questions that name a mode read that mode.astryx experimental theme editor how: padding side words are read with the part's name taken out, so "code block padding" and "top nav padding" set every side of that part. "Card padding bigger (or smaller) than button padding" gives a step past (or under) the button's padding, never a copy of it. A dimension pair such as "16 x 16" is a size, never an amount.astryx experimental theme editor how: a part kept from a spacing change keeps its gap, padding and height ("more compact except buttons"; its own padding shorthand is not yet held, so "bigger padding except cards" says it cannot), and one kept from a border change keeps its border width ("all borders thicker except on inputs"); whole-theme shadows move from each shared shadow's own layers, in both modes or only the one named ("make shadows darker in dark mode"); a part's own gradient and its own two-mode fill step each color; a shadow by a percent scales its colors; an example value has the kind the property takes; and the answer check holds a shadow's strength and a color's see-through to the way asked.astryx experimental theme editor how: "the current page in pagination" (and "… of the pagination") changes pagination's current button, no longer the page background. The words before "in" or "of" name a part of what follows and its state, and "current" is the state Core paints for the page you are on.astryx experimental theme editor howsteps a part's text in a state, such as "make the disabled button text lighter", from each variant's own color. Each step is scoped to its variant and that state, so every variant moves the way asked. Before, one variant's color was written on all of them, and the secondary and ghost buttons moved the opposite way.astryx experimental theme editor how: a warning, error or success banner made darker or lighter steps its own status's colors, never the info blue. "Less visible" and "half as visible" borders are fainter, by the share named. "Less blurry" shadows are sharper (blur halved), never fainter. Questions about the shadows, the text weight, the background or how strong the borders are read the theme's value and change nothing. "Make the color of the text darker" is about the text. "The danger color brighter" makes it lighter. "The text 50% more transparent" scales the theme's text colors. "The page less dense" is the spacing dial. "The h3 size 20px" sets that heading level's size.astryx experimental theme editor how: a value question answered from a part's inner parts ("how dense is the table", read on its cells) names the change on the part that holds the value ("table-cell padding 12px") and looks that part up.- Fixes in
astryx experimental theme editor how:- Radio and checkbox borders: a thicker border keeps its resting color, not the hover tint.
- Possessives:
- A possessive owner's own element is that element, with a state said between them kept ("the menu's hovered items").
- The owner's first word can name the element ("the toggle group's buttons").
- Possessives before something the parts have name the parts themselves ("the cards' and buttons' borders").
- An element the owner does not have is reported, and nothing is written.
- Heights: a height in a decimal unit ("2.5rem high") is that height. A negative height is refused.
astryx experimental theme editor howreads "twice as thin", "twice as small", "twice as narrow", "twice as short" and "twice as tight" as half of now in that direction, and keeps what the words change. "Make dividers twice as thin" halves the divider's line and "the padding twice as tight" gives less room; before, the first had no answer and the second gave more room.astryx experimental theme editor hownow:- reads "twice as soft", "twice as faint" and "twice as subtle" as half of now, so shadows get softer, not stronger;
- reads an owner named with a possessive ("the menus' separators") as where the change goes, the same as "separators in menus", and never paints the owner;
- sets a divider's thickness on the variant asked for ("the strong divider thicker"), not on every divider.
astryx experimental theme editor hownow answers "no part or word called zorp" and writes nothing when an unknown word comes before a place ("make the zorp in cards red"). This is the same answer it gives for an unknown word between a part and what changes.astryx experimental theme editor how:- A value question is about the part the question names: "what color is the card title?" answers with the heading's color. "What color is the card's secondary text?" or "…the muted text?" answers with the secondary text color.
- A color named after a version of a part that has no fill of its own (the ghost button) no longer uses the main button's fill.
- "the buttons as tall as the small inputs" uses the small size, or says the small size has no height the editor can read. It no longer compares the default size.
- "2 times fainter" halves the text's strength.
- "everything rounder except the headings" works: headings have no corners, so they stay as they are.
- More fixes in
astryx experimental theme editor howfor colors asked of parts with variants, states and modes:- Button fills: when the ask gives a whole look, a fill and its text ("gold buttons with black text"), the destructive button keeps its red, and the answer says so. A bare color that every button's text reads on still reaches every button.
- Button text: a text color asked of every button ("buttons with white text") skips the variants whose own fill would hide it (a ghost button drawn on the page), and the answer says so.
- Grays on surfaces: a gray on a surface (a table's header cells, inputs, a card, a dialog's header) is the theme's own gray step in light mode and its mirrored step in dark mode, instead of one gray for both. A control's fill, such as a button's, is still the gray asked.
- Text on a ground: "the text on the gradient white" changes the text only. It no longer also writes the page background.
- Toggle buttons: "toggle buttons" now means Core's toggle button, not a switch.
astryx experimental theme editor: a value ending in an old browser hack's escape (padding '8px\9',--spacing-4 '8px\9',box-shadow 'none\0') is refused, and the value without the escape is offered (set … padding 8px). Before, it was written, and browsers dropped it: a card's padding went to 0, and every use of such a token broke.astryx experimental theme: a process that runs several editor commands (an API caller) reads the app as it is now: a font package removed since an earlier command is no longer counted as installed, and an app copy folder that was not writable and is now no longer blockscompile --checkwith the old reason. The lockscompiletakes for a run are released when the run ends, however it ends, andnewrefuses an option given a value before it starts, as the other editor commands do.astryx experimental theme editor set: a fill or text color that a part's own element never declares, which an element inside it paints from a token (a keyboard key's chip, a radio list item's label text), is refused, since the inner element paints over it, and the token set on the part is offered instead.howreads "keyboard keys", "key chips" and "shortcut keys" as Kbd, never a badge.astryx experimental theme editorreads input it prints or saves, pasted or read back, as it reads typed input:- A setting pasted back as the editor prints it (
padding = 8 px on card) or as a declaration (z-index: 1,000) gets the repair its typed form gets (set t padding 8px --on card), and the editor's own change line (corners pill -> round,--radius-element: 0.5rem -> 0px) sets the value it changed to. - A pasted entry without its braces (
"thing": "corners", "value": "pill"), one that names its setting undersetting, and one whoseonlysays no ("no","false","0") are read as that entry; anonlythat reads as neither yes nor no is refused. - A saved token or property entry whose mode is
both, empty or a typo gets set's reading of that mode beside the undo, and a token saved asvar(--color-accent)is that token. - A setting name of more than one word is quoted in the lines offered, so a scope typo beside it keeps its repair; a setting and value in the other order beside a scope typo get both repairs.
new --accent 'light blue'offerslightblue, never a line without the color;new --font -apple-systemreads the dash-led word as the font.
- A setting pasted back as the editor prints it (
astryx experimental theme editor: the input reader reads numbers, labels and font lists one way on every path.- A comma between digits is a decimal point (
1,125remis 1.125rem,1,250sis 1.25s); only on a weight, whose numbers are whole hundreds, is a comma before three digits a thousands mark (1,000). - Two numbers are never joined into one (
12 16pxis no 1216px); only a unit split off by a space (16 px) is read with its number. - A minus sign is never read away:
-8pxfor a size, a padding or a duration getshow, never8px, and-700on a weight is no weight 1. - Another CSS property's declaration is no setting's value on any setting (
corners 'margin: 24px',text-size 'width: 20px'); a pasted property is read only when the setting is what it sets (border-radiusfor corners, a color property for a color dial, a property that reads the token). - One reader for a family list on the font dial, a family token and a part's
font-family: a weight or a size in the list, alone or after a family (Inter, 600,Inter 600, sans-serif,Inter extra-bold), is refused with the families and the headings weight (a weight word that is part of a family's name, as inArial Black, sans-serif, stays part of it), and a quoted generic ('sans-serif') is offered unquoted; a part'sfont-familyreads a missing comma before a generic as the dial does. - Values a property's grammar pairs with a slash (
aspect-ratio 16 9,grid-row 2 4) are offered as the pair (16 / 9), never the first number. - A mode label in any spelling (
dark mode: red,darkmode: red,mode dark: red) is that mode's label: the offer is--mode dark. - A base or mode in the settings file one slip off (
neutrl,light,lightonly) is read as meant, assetreads it; one that reads as nothing is refused with the line that sets it, never dropped by an unrelated change. - A pasted object whose entries all fail points to
howfor each entry, neverhow settings.
- A comma between digits is a decimal point (
astryx experimental theme editor: the input reader covers more pasted shapes, and a repair still offers only the value typed (cleaned) or a documented reading of it, never a stock value.- A label on a part's property or a type token is read like a label on a dial:
padding 'hover: 4px' --on buttonoffers--state hover,'dark: red'offers--mode dark,'card: 4px'offers--on card, and the property's own label (background-color: red) is the value. A label naming another setting ('accent: red') offers that setting on tokens and part properties too, and never sets the font to it. - A label that is a flag's own name (
state: hover,part: card,variant: primary,mode: dark) says what that flag does instead of naming unrelated parts. One labeled entry in JSON ({"color": "#e11d48"}) is read like its CSS form, and a value pasted with a token's label ('--color-accent: #e11d48') is no longer taken for an unknown option. - An object of several settings written with single quotes or without braces gets one line per setting.
- A saved
red / bluecolor offers itslight-dark()pair; a saved vibrancy with no color to saturate offers only its undo. - A whole font stack in one pair of quotes (
"Inter, serif"), families split by|,;or/, and a comma missing before any generic family (Inter, Georgia serif,georgia serif) are offered as the list meant.font: Inter, serifandfontFamily:labels are read.\u0020in a family and\x2022in content are read as CSS reads its escapes. density roomyoffersspacing roomy, and words for more or less room map that way. Corners and spacing words with nothing near, and size tokens with nothing readable, offerhowinstead of a stock rung or the token's default.- A calc() whose units cannot combine (
8 + 2px,0.5rem * 1px, with each var() at its fallback) is refused. --mode nightordayon a color dial offers the one-mode line, never the both-modes one.- A hex color a digit short is refused as it is, without making a digit up;
navy blueoffersnavy, and0xe11d48offers#e11d48.
- A label on a part's property or a type token is read like a label on a dial:
astryx experimental theme editor: an--onnaming several parts ('button, text-input',button/text-input,'button and text-input', or spaces) is refused with one command per part named, never a group that one word of the list names. A flag's label after the value ('red mode: dark','red state: hover','red variant: primary','red part: card') is read like the same label before it, and offers--mode dark,--state hover,--when variant:primaryor--on card. A flag typed inside the quoted value ('red --mode dark','4px --state hover','pill --on button') is lifted out into the command offered. No repair on a part property offers a reset the input did not hold (0,none,1,auto,normal). A background with one layer too many or an empty one offers the layers typed (url(a.png), red), and a bare number onbackgroundis no longer offered as a px position.border-radius roundoffers9999px,opacity halfoffers0.5,content Hioffers the text quoted,font-weight heavyits number andtext-transform capsuppercase; other words (padding large,box-shadow soft) point tohow, and2 spacing unitsis no longer read as2px. A number or size given as a font family (--font-family-body 700) is refused as a weight or size, never quoted into a family.A word with a negation (not round,rounded-none,not bold,no caps,not red) is never offered the word it negates: corners offerssquare(and readsrounded-fullandrounded-[12px]), the rest point tohow.astryx experimental theme editor set: aradiusorroundedvalue with its unit is offered as that size on corners (radius 1remgivescorners 16px), and one corners cannot read getshow corners; a text size written as constant math (calc(16px + 2px)) is worked out, and a bare number with no unit (text-size 1.5,corners 0.5) getshowinstead of a guessed size; a color-mix share written as percentage math (calc(50% * 1)) is read; two color names run together (navyblue) offer the first;on button: pill, a flag's value and the value in one (state=hover 4px), andlight: red dark: bluewithout a comma are read; a font list in single quotes (['Inter', 'serif']) is read; in a light-only or dark-only theme the theme's own mode label is the value, and the other mode's label is refused naming the mode the theme does not show;cursor hand, which no current browser applies, is refused withpointer.astryx experimental theme editorreads more input as typed:- A comma between two whole numbers of a ratio is the pair (
aspect-ratio 16,9is16 / 9); one that looks like a decimal (1,78,2,35) is the decimal. - An unquoted
newkeeps the name typed and keeps the words after a setting's value in that value (new z7 --mode Dark Only,new --font Open Sans --like neutral my-theme). - A part typo that lands on a part or group name keeps that name (
--on tabelis table). - A pasted saved entry with a key the editor does not write (
comment,id) is read as its one setting, and the key is named as left out. - A headings half offered beside a damaged headings entry is labeled as a step after the undo.
new --likereads a path to an installed base package as that base, echoes an unread value as typed, and labels the line on no base "build on no theme".- A dial name saved in a typed form (
text size) is read as that dial. showandcompilegive saved damage the same lines as a change: the undo and set's repair.
- A comma between two whole numbers of a ratio is the pair (
astryx experimental theme editorreads input the same way everywhere:- A damaged saved mode or base gets one repair from every command (show and compile offer the install and the base the file names, or every mode, as a change does).
- A comma between digits is read by the setting's domain: a decimal comma for
aspect-ratio 1,78(1.78), corners, vibrancy and a spacing scale; a thousands mark in a pixel length (1,200pxis 1200px). - A setting pasted as
show --jsonorset --jsonprints it (withpartsornote), or as a one-entry list, is read as one setting. undo t corners paddinggives one undo for each setting it names.- A command line built from a mistyped or empty option is checked by its command before it is offered, and an empty option that narrows a change (
--on,--mode, …) is never dropped from it. newreads a comma value as a light and dark pair for a color dial only, keeps its other repairs when its base is misspelled, keeps the base for a name that reads as one (new Neutral), names a path by its last part, offers each mode it cannot tell, and labels a base install as a step before its line.- A saved state in other letters (
Hover,:hover) and a dial saved for one mode are read as the editor reads them. - A part typo is matched against the part words too (
--on sidebris the side nav). - A comma
rgb()/hsl()CSS does not take (hsl(0, 100, 50)) is refused with the syntax CSS reads (hsl(0 100 50)). - An unknown word before a colon in a value (
colr: red) is never taken off and offered as the value.
astryx experimental theme editor:set <theme> base <name>with a built-in base that is not installed names its install line, then the same set and the set to no base, in whatever letters the base was typed. Inhow, "a thin border" and "a thick border" name a width (1px and 2px); only "thinner" and "thicker" step from the width the part shows now.astryx experimental theme editor show's line for an inverted surface lost in the page works with every Core: it gives the surface as the color it is, and turns the text of each part drawn on it that reads a token (a tooltip's) to the theme's text color.astryx experimental theme editor set … font: families the editor knows written with no comma between them (Georgia Verdana) are refused with the list ('Georgia, Verdana') and the name kept as typed in quotes, as the browser reads one family named that. A typo of a family with a weight or style word after it is read by the same font rule as the typo alone:Georiga Boldis refused with georgia andheadings bold;Arail Black, near a font a system ships only, is kept as typed with the note.astryx experimental theme editormeasures a button color that also paints the toast's close button on the toast's own fill, and says plainly that no setting keeps the toast's buttons apart, with the nearest button color that reads on every toast fill and on the page when one does. Text on a pane the theme painted (a side nav's fill) is measured on that pane, and the same text shown on another pane that holds it unpainted (the mobile nav drawer) is fixed by painting that pane like the other, not by recoloring the text everywhere. Text drawn on a fill its part draws only in a state (a selected item) is fixed with a line for that state, whichsetaccepts and which ends the problem. An inverted surface whose theme counterpart looks the same as the base's (the same side, nearly the same lightness) is no longer listed under missed. A radius setting on a part whose radius your own theme source sets now says the source wins there, as a padding setting does. Where the base theme's own border is a hairline, a theme's border token is a problem only when it draws nothing on the page at all.astryx experimental theme editor set: what a whole-theme change leaves out (leftOutin JSON) comes right under the status line, each part with its own runnable line. A border width names, and the "thick borders on everything" answer reaches, every part that draws a fixed line of its own (a secondary button's edge) or frames a surface (a banner) beside the containers, menus and overlays; only rules count as dividers, never the edge of a cornered box such as a list row or a button.astryx experimental theme editor: a line offered when the theme is left out keeps every option typed (--on,--state,--mode,--only,--like,--section), so following it changes what was asked, never the whole theme.undoreads the words after the thing as one value, typed unquoted assettakes it (undo t padding 4px 8px --on card). With the theme left out,undoreads the scope in every spelling it takes with the theme typed (--state focusVisible,--on Card,--mode Dark) and offers the undo on the theme that holds it. A token typed where the theme goes (show --color-accent) is never a theme to make. A settings file whose list is written"Settings"is a theme that exists tonew, never made again; written beside"settings", the two are read as one list, the editor's entry winning where both set one thing, and the change says so.astryx experimental theme editor: a whole-theme change names the parts it leaves out, with the line that reaches them:set corners squarenames the parts drawn as pills (badge, switch, calendar day…), which--radius-full 0pxsquares;set --border-widthnames the surfaces it does not reach (dialog, popover, menus, tooltip, toast…) and the dividers it thickens. The "thick borders on everything" answer gives a border to every surface the shared border width does not widen, the overlays that draw a fixed line of their own included, and keeps each divider at its own width.astryx experimental theme editor: a list value with one item misspelled, for a dial that takes each word alone (set t headings 'blod tight'), gets a line for each word, as each word alone does; andundoreads three or more bare words as a list of settings only when every word names a setting, soundo t font Inter Tightis a setting and its value again.astryx experimental theme editor: a setting listed twice by hand now changes the last entry, the one the build reads, so "keep pill" saves and builds pill. A damaged mode or base written in other letters or as a package name (Dark-Only,Neutral,@astryxdesign/theme-neutral) is fixed first by the suggestions, and a change to another setting cleans it to the value meant instead of resetting it. A stored vibrancy of0.5is offered as 50.newcleans each flag value the waysetdoes, so--font '«Georgia»'saves"Georgia".--on "text inputs"and--on "dialog header"name text-input and dialog-header, and--when Variant:Primaryorvariant=primarygets the corrected command. An app copy the editor wrote, left without itsthemes/<name>/folder, is named as the editor's withnew <name>to make it again. Names copied from the app (tTheme,tTheme.ts,brand.theme.ts,themes//t,BrandDark,Brand Dark) reach the theme they name, andnewsays when it is here already. The note after Ctrl-C says whatundoornewsaved, with the project's own CLI command. An undo of padding in the other form (a side or the shorthand) suggests the undo that matches what is saved.astryx experimental theme: a font role the theme builds as one family with no fallback at all (headings set toLoraalone: an exact font token, or a heading family with no fallbacks of its own in the theme's source, which Core builds as just that family) is noted byset,showandcompile: that text has no font while the family loads or if it is missing, with the way to give it a list: the setting run again with a list, or the fallbacks to add in the theme's source.astryx experimental theme editor: the pictures to open are named where they are read. A change with--pngsays in itsseeline to open preview.png (the sample page) and sheet-overlays.png (every menu, tooltip, popover and list, drawn open); without--pngit still names the pages.show --pngsays it on its first line and its last (look, also in the JSON), so a head or a tail of the output keeps it.astryx experimental theme editor set: a page background set on the app shell no longer makes the main content area see-through over a background a setting gives it, whichever was set first.how's page-color line for the main panel now changes what the panel draws.astryx experimental theme editor:newreads more of what is typed after the name as settings, never name words: the base in the key forms (like=neutral,like: neutral), a value before its dial (red accent), a quoted pair or list ('accent red, corners pill'), a dial word with no value, and a word typed after an option's value that no reading takes (--accent red fookeeps--accent red;--corners pill padding 8pxkeeps--corners pilland offersset … padding 8px). Settings typed where the name goes (new 'accent: red') stay on the free name offered, and two bases in one--like(neutral,stone) give the first built-in one.like, the wordshowprints for the base, points toset <theme> base/undo <theme> base. The theme typed as an option (set --theme t accent red) getsset t accent red, and a line set does not read is never offered as working. A theme with a setting pasted on (show t=accent) and a list of values where the theme goes (show 'Inter, Arial') get a look at the theme, never a new one. A whole command pasted as one word (set 'set t accent red') is read as that command. An undo by a held value with a scope typed (undo t 8px --on cards) leads with the setting in that scope.astryx experimental theme editor howmeasures more asks the way they are meant:- "make input borders 3:1 contrast" gives the part's border color the least change that measures that ratio against the page and the part's own fill (or the part after "against"), in each mode: its own ink at a higher strength, else a deeper shade of it. It no longer restates the border the part already draws;
- "make the card text 50% more transparent" scales the text colors on the card from their own alpha, instead of fading the whole card; a part's border or fill, each variant on its own, and "all shadows" take the same relative change;
- "what is the corner radius", "what is the spacing", "what font is used", "what is the border width", "what color is the danger" answer with the theme's value in each mode it shows, and "what is the heading font" answers with the heading's font;
- "make links the color of the text", "make badges the color of the danger" take that theme color;
- "make card shadows lighter" says the card draws no shadow of its own at rest, instead of a false reason;
- "a gradient from #ff0000 to transparent" keeps the typed transparent stop instead of ending in a lighter shade;
- "what is the hover background of ghost buttons" reads the state it names: the fill at rest, with the hover or press wash Core draws over it;
- "borders 30% more transparent", "the shadow 20% more opaque", "the accent 50% more transparent" change those colors' own alpha (never the border width);
- "body font weight 450" writes 450; "how dense is it" and "what is the density" answer with the spacing instead of changing it; "shadows sharper" halves the shared shadows' blur instead of softening them; "the borders on cards heavier" makes the borders wider with no false line.
astryx experimental theme editorcontrast checks measure a part with a fill of its own on Core's media surface (a button on an overlay's dark island) with the text color that surface gives it, so a glossy light button whose label turns white there is listed as a problem, with a fix that sets the button's own color (its variant), which reaches it on the surface and reads on its fill everywhere. A label on its part's own fill is measured on the fill its variant draws.astryx experimental theme editor's lines for text on Core's media surfaces end the problems they name: a part drawn with its default props is measured and fixed as the variant Core draws it as; text on a lightbox's own on-color bar takes that on-color on the lightbox, whichsetaccepts; a light overlay that turns the lightbox's text and its bar opposite ways is offered the overlay back; and a text token refused on a lightbox points to the on-color that reaches it. A link of yours at a page's name (the sample page, the sheets) or at the record of pictures is left alone and named, asshow --helpsays, instead of refusing the command.astryx experimental theme editor's contrast checks measure a part inside Core's media surface (a button on a lightbox's dark island) as that surface draws it, in its own scheme whatever the page's mode: an untouched base ships no problem there, and a light-only color on the page's part makes none. A problem there is listed once, and its fix is a color in the surface's scheme, which reaches it; when the part lets the surface's ground through and the same text on the page needs the other color, no line is offered, so following the fixes never cycles.astryx experimental theme editor showdraws the parts it shows open as a desktop window of the pictures' own size lays them out: a width or height media query is answered for that window, so AlertDialog's buttons sit side by side in the open states picture instead of in its phone layout.astryx experimental theme editor show'smissedlist names what keeps the base's look beside the theme's own, and each line changes the built theme:- A tooltip or toast still on the base's dark inverted surface once the theme's own surfaces changed (a grey Win98-like theme) is listed, with a line that gives it the theme's surface in each mode the theme draws and readable text on it.
- A soft shadow beside square corners or a theme border (a popover's, a menu's, a dialog's) is listed, with a line that takes its blur away.
- A status fill (a banner's, a badge's status variants) is listed only where its dial builds a color of its own (the theme's vibrancy moved); at the base's vibrancy the dial gives the base's own color back.
how's answer for a part on that list (how "make the tooltips match the theme") leads with the same line.
astryx experimental theme editorreports what a theme's own changes did not reach where it applies:newwith a color or dial counts and names the parts it missed assetdoes (missed,missedParts, and the newmissedOnin JSON), every change names the parts it missed rather than only counting them, and a base theme square by design is no longer told its soft shadows sit beside square corners it did not choose.show --section <family>pictures that family first, with its parts drawn open after it, not the overlays.astryx experimental theme editorgives a missed part one line where one setting reaches it: a toast's text picks its own side from its fill, so its surface alone is the line. Where a line takes two settings (a tooltip's surface, then its text), the problem the first step leaves says that the next step of that line clears it, and names the step. An error toast's line for the danger color takes the text that reads on the new red where the toast's own pick would not, so following it makes no problem.astryx experimental theme editor:showandsetcount the missed list as misses on parts (a part can miss two ways, its border and its shadow), andshow's line under the six it lists counts the rest as misses, apart from the parts whose fill or text color is only still the base's. The JSON of a change addsmissedParts.- The sheet, the preview and the pictures draw an auto media surface inside a part with a fill of its own (a toast with a light background) on the side the app's measurement picks, so its text reads as it does in the app.
- Text drawn in a disabled color (an inactive segment) is held to no 4.5:1 contrast, and no fix whitens it.
set's note on a border width offers the framesshow's missed list has: only parts that draw a box, scoped to the variants that do, and none at a width of zero.
astryx experimental theme editor: a mistyped part (nmber-input) is read as the whole part name it is a typo of, never a group one word of it names, and a did-you-mean follows the one typo limit (a name that only holds the typed word inside it is none). A boolean option written with a value (--only=true,--png=false,--only false) gets the same reading in set, undo, new, how and show: the option takes no value, with the command that works. A dial and its value in the other order (set t round corners) lead with the set in the right order, and a theme typed last is offered first only in a line that works. undo names every entry of a setting listed twice by hand that it removes. A bad entry beside a good one of the same setting is named as listed twice, so its keep line keeps the good one, and a keep line whose value set refuses is not offered. A dial word saved in other letters (Pill) is that word, and a headings word saved under the other half is filed under its own.onlyon a setting that is no group member is refused with the undo of that entry. show writes a deleted palette.config.json again. A settings file that cannot be read is made again on the base it was built on, andnew --likereads a base in any case.astryx experimental theme editor set: a page or text color typed as a CSS property with no part (set t background '[#0](https://github.com/meta/astryx/pull/0)f172a') is offered for the mode it reads in first (--color-background-body '[#0](https://github.com/meta/astryx/pull/0)f172a' --mode dark), with the both-modes line after it, so the suggestion does not leave the other mode unreadable; a color that reads in both modes is offered once, as before. The words people write for a dial reach it: a name with-coloror-colourafter it (primary-color,brand-color), a plural (shadows), andshadows none/dark-mode true/light-mode true, which name the dial and the value that does it (surfaces flat,mode dark-only).astryx experimental theme editor: a color for one mode on a part is written in the part's block for that mode.- In the other mode the theme writes nothing there, so what Core and the base theme give the part in context stays as it was: the current page in Pagination, a text field's error, warning and success borders.
- A one-mode color in a state is accepted on a part that has no color of its own in that state; the other mode keeps Core's.
- A one-mode gradient goes into the part's block for that mode as its image layers (and a color layer as that mode's color), so the other mode keeps Core's own images, such as a button's hover tint.
- A one-mode background on an app shell region leaves the page background painting it in the other mode.
- A one-mode color in a state is accepted on every member of a group, and an exception kept in a state (inputs darker except when focused) keeps that state's own fill in each mode.
- The part data records a background a part inherits (
inherit) as no paint of its own. - The result lists each property a change writes inside a mode block, under its path (
@dark :hover).
astryx experimental theme editor:- A border in one mode on a part that draws none is a ring at its edge (an inset box-shadow) that takes no room, so the other mode keeps its size; where the part draws a shadow of its own, the answer says why it cannot.
- Outlined buttons in one mode keep the outline dial beside the one-mode colors, and say the dial is the same in both modes.
- A divider's line is reached per variant: its color (the strong divider's own token), its thickness by the amount said, and its removal. A fill on the divider's own element, or a token its variant does not read, is refused with the line that reaches it.
- A token family follows a source written as one
light-dark()value or a token reference. - A variant's low-contrast text is listed once, with a fix scoped to that variant.
- A part's border is no longer colored through parts inside it that draw no line (a toast's ghost buttons); a part with no border made thicker takes its own height.
- A state shadow that keeps Core's ring keeps each status's own ring there.
- Pieces named after a part's catalog name ("the checkbox check", "the select arrow") are those parts.
astryx experimental theme editor: one-mode colors per variant, the spacing dial around kept steps, and padding amounts from the base theme.- A one-mode color on a part whose variants each have their own is written to each variant as the property it names (a card's
border-colorstays a border color), with each variant's own other half: an earlier setting for the other mode or for both modes, else what the variant shows unset.--modeon a color longhand such asbackground-colororborder-coloris accepted this way. - A hover set as
background-colorstays on every variant after a later one-modebackground, and a one-mode background after a plain one applies to every variant in both modes. - A whole-part state setting that your own
<theme>.theme.tssets on the same state is not repeated on the variants, so it does not show anywhere, as the result says. - The spacing dial keeps spacing steps in order around an exact step the theme keeps, reads a kept control size written as a token,
clamp(),min()ormax(), and keeps a part's own exact control size in order under a whole-theme dial. howpadding amounts read the base theme's own block and inline padding on a part ("double the button padding" on butter gives1rem 2rem).
- A one-mode color on a part whose variants each have their own is written to each variant as the property it names (a card's
astryx experimental theme editor: one-mode colors, kept sizes and own padding sides.- In a
light-onlyordark-onlytheme, a color you set (a token or a part's color) fills only that mode's half; the other half keeps the base theme's, so a lightbox, an overlay or a toast Core draws in the other mode stays readable. A setting saved for the theme's mode keeps its half when the theme turns one-mode. mode bothafter a one-mode theme says to take out amodegiven to the app's<Theme>for it.- The spacing dial keeps control sizes in order around an exact size the theme keeps (
--size-element-md 34pxwithspacing tightgives a larger size above 34px). - A padding your own
<theme>.theme.tssets on some sides of a part wins on those sides; the editor's padding still applies on the other sides, on every part, and the result says so. A physical side stays physical and a logical side logical, in each text direction: with your ownpaddingLeft, the editor's left is never written; with your ownpaddingInlineStart, the editor'spadding-leftshows only right to left (where the start is the right). A variant your own source pads wins over an editor padding on the part's plain rule, whatever sides that sets.
- In a
astryx experimental theme editor: amodeorbaseentry a hand edit put in the settings list, where it does nothing, is listed byshowonly under a "misplaced" note, never as a setting; every change names it the same way, and every refusal leads with theundothat removes it.astryx experimental theme editor: one-mode gradients and tokens keep the other mode, the page background in every AppShell, and heading colors and types.- A gradient for one mode is written as background images (typed as
backgroundtoo), so the other mode keeps its own background color; each mode's layers are kept by mode as they are written, so a fade totransparentis never lost. A gradient holding alight-dark()stop takes no--mode. - A token set on a part for one mode (a heading color included, and any color in a one-mode theme) keeps the token's own value in the other mode.
- A one-mode
backgroundno longer removes the other mode's one-modebackground-color. - A background on
app-shellshows in every AppShell variant: the shell's header and side nav take the same background (they stay opaque when content scrolls under them), its main content area is see-through, and the result says so. - A heading color that names a text color token (
var(--color-text-secondary)) is accepted; heading--when type:takes Heading's own types (display-1 to display-3). howoffers a gradient for one mode asbackground-image … --mode, and a one-mode color under a part's own gradient says it does not show.
- A gradient for one mode is written as background images (typed as
astryx experimental theme editor: one-mode colors in a variant or a state, gradient layers with a color, keywords with a mode, and the corners dial on parts with their own radius.- A one-mode color in a variant or a state (a heading level, a hover) keeps the theme's own value around it in the other mode: the variant's resting color, then the part's, then the whole theme's, as the theme finally has it. A later brand color reaches the other mode.
- In a one-mode background, a color written beside a gradient (
#f00 linear-gradient(…)) is that mode's background color, and the gradient its image. - A CSS-wide keyword (
unset,inherit) takes no--mode; the offered command sets it for both modes. - The corners dial reaches parts whose base theme gives them a radius of their own, and a corners step on a part starts from the radius the part shows.
- A one-mode color on a part says that, in the other mode, it overrides what Core or the base theme gives the part in context.
howlists the margins a part reads among its spacing, assetreads them.
astryx experimental theme editor: a mode word typed with a typo that keeps its letters (drak,darkk,ligth) is that mode wherever a person types one, by one reader: a pasted label in ahowquestion (drak: cards [#1](https://github.com/meta/astryx/pull/1)c1c1echanges the dark cards only) or in asetvalue ('drak: #eeeeee'offers the--mode darkline) and the--modeflag. A word of its own (right, tight, bark) is never read as a mode.astryx experimental theme editor: a setting for one color mode that reaches the whole theme reads as one scope, "accent = red (whole theme, light mode only)", never "(whole theme) [light only]", which reads as two scopes at odds. A setting on a part keeps its mode mark as before.astryx experimental theme editor: a one-mode write changes only its mode.- A token set for one mode keeps its other half as what that mode shows: Core's own reference when the base theme's value follows it (a focus ring that follows the accent), so it keeps following the theme's tokens.
- A one-mode page background on the app shell makes the main content area see-through, and a gradient fixed, in its mode only.
- A one-mode background shorthand replaces longhands set for its mode only; a longhand set for both modes stays.
- A light-only or dark-only theme keeps the other mode's settings for the regions Core draws in that mode (a toast, a lightbox), says so, and takes
--modefor that mode; its own mode needs no--mode. - A color on a link is refused for the token its color prop reads (
--color-text-accentfor a default link), set on the link.
astryx experimental theme editor set: defineTheme's motion knobs typed as a setting (motion,tempo,character) say the editor sets motion through the duration and ease tokens, and point tohow "faster motion"andhow "slower motion", the slower first for a tempo above 1.astryx experimental theme editor setandundo:--whentakes several conditions, one per prop (a ghost small button:--when variant:ghost --when size:sm, or--when variant:ghost+size:sm), written as one rule for parts that have all of them, as Core'sprop:value+prop:valuekeys are. Each is checked as one alone is, the same prop twice is refused, and the conditions are saved in one order, so an undo finds them whatever order they were typed in.astryx experimental theme editor newreads a setting typed after the name in the pair form with its key in quotes ('"like": "neutral"','"accent": "red"') or swapped (red=accent,stone=like), never as words of the name; the base word is never a value (neutral=likeis--like neutral, never a gray tint). The name typed as an option (--theme t2,--name t2,--theme=t2) is that name, and the refusal says the option is none of new's.astryx experimental theme editor undo <theme> <word>with no setting named never leads with a plain step back, which can take back another change than the one typed: a value one setting holds gets that setting's undo, a value several hold gets each one's, a word nothing holds gets a look at the theme (show), and onlyallorlastoffers the step back.astryx experimental theme editor: a settings entry'sonlywritten as text ("false","true") is read as what it says, with a note, and any other value that is not true is refused with the undo that removes that entry, soshowand the build never disagree. A theme typed after the setting (set --color-accent '[#123457](https://github.com/meta/astryx/pull/123457)' t) is refused with the samesetorundowith the theme first, never anewof the setting's name.undo <theme> vibrancysays the default vibrancy applies now.newwith several bad dial flags suggests one command that fixes or drops each of them;new --basepoints to--like;shownames a show that works and its help for an option it does not take. The name rule lists every reserved name it refuses (com0-com9, lpt0-lpt9, and com¹-com³, lpt¹-lpt³). corners takes a rem (saved in px), and a bare number gets the px line. Dial words are read in any case (ROOMY, MORE, BOTH).set t 'corners pill'is read as the thing and its value. With no theme named in an app with one theme, show and undo name that theme. The compile line in the result works from the folder the command ran in.astryx experimental theme editor: names, damaged themes and stops.- A theme name typed as a path (
themes/brand,./t,t/) names the theme it ends in, and says when that theme is here already; a typo of a theme name offers the nearest theme by spelling first (brand-drakisbrand-dark, notbrand), and a camelCase name is the dashed one (brandDarkisbrand-dark,themeParkistheme-park), never a new theme. - A refusal names a command that works:
undoon a theme whose settings cannot be read and that has no history namesnew <theme>, notshow; a damaged mode or base no longer sends each fix to the other (changing or removing a setting puts the field back to its default and says so); a settings entry with no thing or no source is damagenewkeeps aside, as the refusal says. - A folder holding only
desktop.iniis empty, like one holding onlyThumbs.dbor.DS_Store. - An
undothat switches the theme between one mode and both names the app's<Theme mode>to add or take out, asset modedoes;undo --helpsays--moderemoves a setting saved for one mode in a one-mode theme. - Stopped (Ctrl-C) while the checks and pictures run after a change, the editor says the change is saved and built and that
showruns the rest.
- A theme name typed as a path (
astryx experimental theme editorandcompilename the real problem and the real place:- when a build of
<theme>.theme.tsreads another export named for the theme (a default export beside<theme>Theme), the refusal says the build reads that export, not the one that extends the settings, instead of asking to put back what is already there; - a value Core refuses inside a rule it derives from the typography is no longer reported as a value of the file; Core's refusal of a local token's name is named at its line;
- an editor theme that lost
<theme>.settings.jsonis refused bycompileandcompile --checkas the editor commands refuse it, with the line that makes it again; - a refused value in a part block imported from a file beside the theme (
components: parts,parts.button), or in a theme the source re-exports (export * from './impl'), names that file and line.
- when a build of
astryx experimental theme editor:hownames the same states for a state a part lacks (a selected table row) assetandhow <part>do: the statessettakes there.astryx experimental theme editor:setwith the theme left out and a value of several words (set padding '4px 8px' --on card,set shadow '0 1px 2px red' --on card) offers the set on the one theme here when set's check passes it, every option kept, never a theme named after the setting.undonever offers to make a theme from the word: a typo of a setting the theme holds (undo acent), a value it holds (undo red,undo t red), or a setting with its value in one word (undo 'corners pill') gets that setting's undo, and a step back says which change it takes back;show 'corners pill'looks at the theme. A value with commas typed unquoted, assettakes it (undo t font Inter, Arial), is that setting's value, never a list.newreads a setting typed after the name (new t2 accent red,corners=pill,corners: pill; accent: red, a pasted JSON object) as its option, never part of the name, and a token typed for the name (new --color-accent) is never the name offered. An option typed before a nested group (theme --mode dark editor set …) goes after the command it names; an option whose value is a subcommand's name keeps it; and options with no subcommand at all (preview --theme t) name the subcommands that take them, never their value as a subcommand.astryx experimental theme editor undoof a property the theme sets in another form of the same family on that part names it:undo t background --on app-shell-headerwithbackground-colorset says "settings for background: background-color = #111827 on app-shell-header" and offers that undo, as it already did for padding and its sides.astryx experimental theme editor: a negated state (--state unpressed,--state 'not pressed',--state unchecked) is read as the part at rest. The refusal offers the same line with no--state, instead of the state the word denies (--state isPressed), which saved the pressed look when the rest look was asked for.astryx experimental theme editor: a typo of a CSS keyword that starts with no- or not- (cursor not-alowed,background-repeat no-repat) is offered the keyword, as any typo is; a real negation (cursor 'not pointer') is still never offered the word it negates.astryx experimental theme editor set <theme> neutral <color>now reaches the inverted surface tooltips and toasts draw on. As Core makes it from a neutral scale, it is the card surface of the other mode, from the neutral color's own shades and inside the ramp, so it carries the color in both modes (in dark, the shade next to white rather than white itself). The on-dark and on-light text takes the neutral shades the official theme maps them to. Before, a green-on-black theme kept Core's own pure white tooltip and toast.astryx experimental theme editor newchecks its color flags as setting those dials does: a pale accent that does not stand out from the page (or any other contrast check a color dial fails) is listed in its problems.astryx experimental theme: a file, folder or link of yours at the open states page's name (sheet-overlays.html) is never written over by--png; the picture is not taken, andset --pngandshow --pngalike say why. The open states picture shows each overlay at the height of what it holds, up to a window's height, and a dropdown menu's submenu opens with rows.preview app --themerefuses a theme image reached through a link that leads out of the theme folder, notes images of this app's public/ folder the new app lacks, adds each package the theme's own source imports at this project's version (refusing one this project does not have), and adds no font package for a fallback face or a family the base's fonts stylesheet already loads. A preview page file that is not a regular file is named so, with what fixes it, and its page stays so the same remove runs again. Beside--template, a description is offered only when it relates to a page.astryx experimental theme editor:--pngtakes sheet-overlays.png beside preview.png, onshowand on every change: every menu, tooltip, popover and list drawn open, in each mode the theme has. The sample page shows none open and the full sheet is too tall to read whole, so the result ofnewnames it in its look-at-it line. A change without--pngremoves it with the other pictures, and namesshow --png, which takes it again. A typeahead, whose doc requires a search source, is rendered with a sample one in the catalog the part data is read from, so its list (typeahead-dropdown) is recorded andhowreads it.astryx experimental theme: an option typed before a group's real subcommand (preview --theme t list,editor --mode light set t …) is read as that: the refusal names the option and the subcommand, offers the command with the options the subcommand takes moved after it, and says which options it takes none of. An option's value is never reported as an unknown subcommand, and the line offered is the subcommand typed, never another one.astryx experimental theme editorsets a list's highlighted option through--state highlightedon its row (selector-option-row,multi-selector-option,typeahead-option), and reads a value labeled with that state.astryx experimental theme editor: every dash form of an option (a hyphen before a dash, minus signs) is read as the option, never glued into a value. A dial name with a space for its dash ("text size") is the dial. A set with no thing points to the settings it takes. A typo as near two values offers each (tightr: tight and tighter). A family spelled near a system font the build knows (arail,Menol) is kept as typed, with a note naming that font.undo t headings wdieremoves the half its reading names. show, and undo with no history, on a damaged saved value offer its undo and set's repair beside it; a saved base in other letters or with a typo of a base that is not installed reads as that base, with its install first, in show as in a change. An entry saved in a form set reads when typed ({"corners": "pill"},"corners pill") is read as that setting. An undo names the change now on top, which the next undo takes back.astryx experimental theme: an option or words a command does not take are answered one way by every editor and preview command: the options it takes are named, its help is offered, and the same command without them only where that is safe to run (show; never a preview remove, which would then remove the whole preview). A color set on a part whose color comes from its color prop offers the token of the prop's default as its doc gives it (a link: accent), else the token of each color the part reads (Text's color depends on its type).astryx experimental theme editor: everynewa refusal offers is checked asnewchecks its options before it is offered (a value never typed, such as a stock font, is not offered; a flag new refuses is left out and named; a line still refused is not offered), and a change of another dial is named for after the theme is made.newwith no name offers a free name; a built-in theme among the extra words (new t3 like neutral,new neutral t3) is the base. set, undo, new, how and show read their options one way: in other letters, with one dash or a typed dash, or one slip off (--On,-only,--olny) they are named and the command offered with them. A token typed after its value andset t neutral baselead with the set in the right order; a repair never adds a part that was not typed; a swapped line that needs an install leads with the install. A base that reads as nothing is set back to the base the theme was built on, never to none. A font dial word on a part's font-family gives the family stack it stands for. A theme whose settings files are both gone but whose history or source the editor wrote is made again on its base, and undo then steps back. A part saved in other letters or as a one-item list is that part. undo of a misspelt setting leads with the one of the scope typed, andundo <setting> <theme>gives the reason with the theme first.astryx experimental theme: an editor theme whose icon registry is a module in its own folder (as compile advises) now loads in the editor's checks, and its app copy carries that module, soshowandsetcheck it andcompile --checkpasses. A theme source whose tokens replace the settings' (a spread ofdefineTheme's result with atokensfield of its own) is refused by name instead of every change being saved and never built. A source name cut short (themes/t/t,themes/t/t.theme.) or a theme folder in other letters is offered the theme source. An empty--outis refused like a blank one. A weight given in a part'sfontshorthand is loaded, and weights are judged per family, so no font gets a gap note for a weight only another family uses. The stabletheme buildof an editor theme says it does not write (or check) the theme's app copy, and names the compile that does. A copy's compile with--outin the theme's own folder offers only a line compile takes, once.astryx experimental theme editor: the refusal of a theme's own token values no longer ends a reason with two periods.astryx experimental theme editor how: a padding or gap amount ("50% bigger", "20% smaller", "double", "150%") is an exact value from the one the part has now (its own setting, else its rule or the token it reads, each side of an unequal padding scaled), never a CSS percent padding; and with no amount, a part with an exact padding gets a step of that padding (said to be a step), since the spacing dial does not move an exact padding.astryx experimental theme editor: per-variant colors in one mode, hover on every variant, later longhands, nested cards and kept sizes.- A one-mode color (
--mode, or any color in alight-onlyordark-onlytheme) on a part whose variants each have their own (a button or card background, a badge's text) goes to each variant's own rule, with the other mode's half exactly what that variant showed there (the base theme's value, else Core's; transparent stays transparent), so the other mode is unchanged for every variant; a variant's own hover still shows. - A whole-part hover background (
--state hover) reaches every variant, including ones the base theme gives their own hover or resting color. - A longhand set after a shorthand wins even where the base theme holds that longhand (
padding-inlineafterpadding,border-colorafterborder). - A plain card inside a variant card keeps the card padding the editor gives it, in each text direction, and a variant's own padding (from the settings or your own source) no longer leaks into it; a variant your own source pads keeps its padding after an unequal editor padding on the plain card.
- The spacing dial keeps every exact control size the theme keeps (in px, rem or calc, from your own source, or set on the part) in order, on a part too; a size with no room between two kept ones takes the smaller one's size, and the result says so.
--moderefused on a border names the variant in the per-mode color step; a gradient is offered as written for both modes.- With your own source setting one corner, the corners note says the dial shows on the other corners after the undo.
- A one-mode color (
astryx experimental theme editor: a page background onapp-shellalso paints the shell's header and side nav, so they stay opaque when content scrolls under a sticky header; a page gradient is fixed to the viewport on the shell and those regions so they line up.howgives the page background one example value per mode, so text stays readable in dark mode.astryx experimental theme editor set <theme> --color-background-body <color>no longer moves the neutral color's other surfaces. A mid-tone page such as teal used to turn cards, popovers, menus and dialogs near-black in light mode (with dark text on them), because the neutral shades followed the written page color instead of the page the base theme's surfaces were made for. The written page color is now that one color, in light-only and two-mode themes alike.astryx experimental theme: the editor knows its pages and pictures by their exact names (and its pictures record), so a file or link of yours named like one (sheet-mockup.png,preview-v.html) no longer blocks a change;preview app --themecopies such a file, and leaves a link out and names it (it never reads through a link). A link at a picture's exact name, to a file or to nothing, is never written through or replaced: only that picture is skipped and named, and the others are taken.preview addat a workspace root names the app to run it from, as the other commands do. A--sectionrefusal keeps--png; an option written last with no value offers the command without it (never a usage line), except where leaving it out would widen a removal; an empty--templateofferspreview additself; a template typo offers only a page that can be added now.preview app --themenames an open font it cannot install, with the package that would load it. The sheet says when a template page's charts are drawn in the browser (recharts), so its pictures show their space empty.astryx experimental theme editor showkeeps going where a page it draws cannot carry or write something: a theme image over 8 MB is left out of the pages and named in show's notes, rather than stopping the pages, andshow --pngin a theme folder that cannot be written names the folder, rather than refusing on a family page it could not write.astryx experimental theme editor set: when a theme's own source sets the fill of the accent or a status color family to a fixed color or a pair of fixed colors, such as--color-accent: ['[#9333](https://github.com/meta/astryx/pull/9333)ea', '#d8b4fe']int.theme.ts, the family's other shades (links, icons, the muted tint) now come from that color, the one on screen. Before, they came from the color setting the source overrides, so links could turn blue beside purple buttons. The note about a hard-to-read source color now names a shade of that same color.astryx experimental theme editor: a theme whose palette names a palette recipe this CLI doesn't know is now refused plainly, and the file is left exactly as it is. A recipe a newer CLI made gets the same refusal asastryx theme palette generate, with the update step that fits where the CLI runs, instead of asking for the file to be fixed by hand. Any other name is said to be no recipe Astryx makes, and the refusal says to setrecipein the file to one of the recipes this CLI knows, naming them.astryx experimental theme editor: a panel's text color ("the drawer text red", a bottom sheet's, an alert dialog's, a hover card's) is answered with the text color tokens its heading and text read for their color role, never a color property they paint over; a fill set on inputs lands where each member paints its box, a date and time field's two boxes included.astryx experimental theme editor: a part's conditions come from what its theming target declares. The part data records every visual prop and runtime state the part's target declares, and the readers keep a runtime state the target declares (or one written as its own name) as a condition, so a state Core adds needs no change to the editor.astryx experimental theme editor showlists asunreachedeach part whose fill or text color is still its base's (a part counts as reached when both changed, or a setting is on it), the most visible first; the text names ten and how many more, and--jsonlists them all.astryx experimental theme editor:- The part data draws every prop that changes a part's look (a toast's type, an avatar's shape), and reads a prop as a condition where it changes a color the part paints, so "the error toast background darker" steps from the error toast's own red.
- A part kept from a corner change pins every corner token its shapes read.
- A select's chevron or caret is its indicator icon, and a piece a part does not have (a date picker's segments) is named; neither writes the whole part.
- "indeterminate checkboxes red" reaches indeterminate boxes only, and "selected" is a toggle button's pressed state.
- A part that draws a line on some sides only (a grouped button's join) is still listed as drawing no border of its own.
- A one-mode hover shadow on inputs keeps their hover ring; "half as visible" is the input ring's alpha; "all focus rings" colors the inputs' rings too; a one-mode border on a part with no line draws one, see-through in the other mode; a radio's dot is its own part; "the progress indicator" is the progress bar's, and a state it does not draw apart (indeterminate) is named.
astryx experimental theme editor: more part facts read from Core, color asks answered with colors, and refusals that point to the setting that shows.- The part data reads a background a part inherits from the region it sits in (a side nav in an app shell), and the declarations of every target an element carries (an app shell's side nav region, which is a layout panel too).
howanswers a lighter or darker background with a color, never a brightness filter, which dims the text and icons too: from the page's color for "darker than the page", from each variant's own fill in a state, and from the part's resting fill otherwise.howanswers striped or no striped rows with the token Core paints every other row with, on the row.- The focus ring Core draws on a checkbox or radio indicator is read as tokens the indicator reads always: an outline property or a focus state there is refused, pointing to the focus outline token with no state.
- A font size, weight, line height or letter spacing on a part whose text is drawn by elements that set their own from a token (a top nav heading, a side nav heading, a banner) is refused, pointing to that token on the part;
howanswers with it and its current value. - A border on a part that draws none of its own, whose edges its inner parts draw (a date-time input), is refused, pointing to those parts;
howreads "date and time input" as that part and answers for its date and time boxes. - A checkbox's indeterminate look is reachable with
--when checked:indeterminate, andhowadds it beside--state checked. - A text property CSS inherits, set on a part, says which parts inside it also take it.
astryx experimental theme editor: a part that another component places somewhere (the current page's button in a pagination, a pressed toggle) records that place as a condition, so what that component paints it with there is never read as the part's look at rest. A ghost button reads no fill at rest, as Core paints it.astryx experimental theme editor: padding and corners reach the elements Core draws them on.- Padding on a table row, which CSS draws no padding on, is refused for its cells, and
howanswers a typed table row padding on the cells. - Corners on a button group are written as the corner token its first and last buttons read, so the group's outer corners follow.
- Padding on a table row, which CSS draws no padding on, is refused for its cells, and
astryx experimental theme editor: part facts read from more of Core, colors that reach a part's inner text, corners that reach the parts drawing them, and results and refusals that say what is true.- The part data renders each component with each look flag turned on too (a table's
isStriped,hasHover), so a table row reads its hover fill, andhowsteps that token for a lighter or darker hover instead of a brightness filter. howand a refusal of a state a part lacks list the same states.- The focus outline tokens can be set on checkbox and radio indicators, where Core draws the focus ring at focus time.
- Changing one member of a group kept alike (inputs) alone in height says it now differs from the rest, and names
--on <group>. - A color on a part whose text is drawn by elements that read a text color token themselves (a top nav heading, a top nav) also goes into those tokens on the part, so the text shows it.
- Corners on a part whose corners are drawn by parts of its own inside it (a date-time input's date and time boxes) round those parts, for the part and its group.
- A whole-theme corners dial moves a part a base pins to a length or to a token the dial never moves (such as
--radius-fullon buttons), keeps a part Core rounds with a fixed token (a pill badge), and never overwrites corners set on a part. - The result lists every state rule a change writes, including one the base theme already has a state block for.
- A color given beside its own image in one background is never reported as covered by it.
- A keyword with
--modeon a token offers only the color; on a one-mode theme, a thing that takes no mode is refused with the command that drops--mode, never with a change of the theme's mode. - A one-mode state color on a group names the members that cannot keep the other mode and offers
--onlyfor the part named.
- The part data renders each component with each look flag turned on too (a table's
astryx experimental theme:- A part key the build cannot write as intended is refused at its line in an editor theme: a vendor property written without its dash (
msOverflowStyle,webkit-transform, with the dashed form offered), a pseudo name in capitals (':HOVER', which Core does not read as:hover), something after a pseudo-element ('::before:hover', with':hover::before'offered), two pseudo-elements, an escaped pseudo name, the custom property--, an empty key, and a block under a key that nests none ('[data-x', a pseudo key inside a pseudo key). A plain theme'scompilewarns them, astheme builddoes. - A custom property of the theme's own whose value is a
var()that reads nothing is refused at that property, as the samevar()is in a part's property. - A value passed to an imported function (
make('nope')) is blamed on the line that passes it; a value read through an optional chain (all?.toks) or an export that is a property of another block in its file is blamed on the line that holds it. - NaN and Infinity get no example made from them (no
'NaNpx').
- A part key the build cannot write as intended is refused at its line in an editor theme: a vendor property written without its dash (
astryx experimental theme editor how: an element named before "in" or "of" a part ("the selected option row in the selector", "the hovered option in the selector", "the checked item in the dropdown menu") is that part's own element, by the rest of its catalog name and the state said, never another component the words seem to name (a table's rows) or the part itself; the last place said is the place ("the text in the hovered menu item of the dropdown" is in the dropdown), which is never written as a part of its own.astryx experimental theme editormeasures text on a fill the theme sets on a part the base theme draws with none (every tab painted gray): its text in each state is checked on that fill and named on that part, and each line sets the text on that part, so following them ends the problems.astryx experimental theme editor: a part's own state saved in a spellingsetreads typed (toggle-button'sis-pressedorispressedfor isPressed) is read as that state, with a note, instead of being refused as damage. The next change saves the part's spelling.astryx experimental theme editor: a state setting on a part (font-weight 500 --on tab --state selected) wins over the build's copy of the plain part's value, which the build no longer writes after it; andhowkeeps a state at the value the part shows in that state (a selected tab's semibold). A shadow on the resting rule of a part that draws its rings in its box-shadow (a text input's hover and focus rings) is refused with that reason, in both modes or one, since it would replace the rings in every state.astryx experimental theme editor: a part's own state written as the part names it (--state isPressedon toggle-button) is saved and read back as that state. Before, the next command read the savedisPressedasis-pressed, a state the part does not have, and refused every change to the theme. A theme already holding such a state is refused with its undo and asetline that writes the setting in its place, so the theme loads again.astryx experimental theme editor:- A text color on a part whose text sits on Core's media surface inside it (a toast's inverted surface) is refused with the lines that reach it,
--color-on-darkand--color-on-lighton the part, andhowanswers with them; the part data records such a surface. - A resting shadow on a part that rings itself in its box-shadow keeps each of its renders' own rings: a status that draws none while focused gets the shadow alone, a shadow of none leaves the rings in their states, and a state's own shadow for the part wins on every render.
- An input's focus ring is its box-shadow ring:
howanswers a focus ring color there with that ring while focused, and an outline color, width or offset on a part that draws no outline is refused. - "toggle thumb", "switch knob" and the like are the switch's thumb, never its track.
- A one-mode fill's covers notes keep its mode, in their words and their lines.
- The corners help names the step
moreandlesstake between round and pill.
- A text color on a part whose text sits on Core's media surface inside it (a toast's inverted surface) is refused with the lines that reach it,
astryx experimental theme editor:- A part's text made transparent by an amount ("the button text 50% transparent", "the fainter text in cards 50% transparent") is its text colors at that alpha, never the whole part's opacity.
- A state typed by its prop name or its ARIA attribute (
--state isPressedoraria-pressedon a button,isSelectedon a tab) is the state of that name. - Several states at once are taken where the element takes them (a hovered selected tab), saved in one order so either spelling is one setting, and undone in either;
howcarries both states said ("hovered selected tabs"). - A one-mode border on a part that draws a border in that state (a focused input) is that border's color alone; a line drawn as a ring keeps the shadow the part draws in that state.
- A divider's line: "fainter" fades every variant's line, "hide" takes them away, and a thickness for one variant ("subtle dividers thicker") stays on it.
astryx experimental theme editor shownames undermissedthe parts the theme's own changes should have reached and did not, one of each kind first: with the accent changed, an inverted surface (a toast, a tooltip), a disabled part drawn as the accent at reduced opacity, a selected state on the base's fill, a status fill (an info banner); with the corners changed, a pill; with the border width changed, a borderless surface. Each comes with the one line that reaches it, its state named (--state disabled,--state selected). The text shows six and counts the other parts on the base's look;--jsonlists them all. A part whose only fill is the shared hover or pressed tint (a link, a menu item) is judged by its text, so it is no longer listed as unreached.astryx experimental theme editor how: two parts joined by "and" share the ask around them, so "half the corner radius on buttons and cards on hover" gives both parts their own command with the amount and--state hover(before, the first lost the state and the second was dropped). "context menu" is Core's context-menu part, not the dropdown menu.astryx experimental theme …: a pasted change line whose label names a part (background-color (card) -> red) sets that part instead of reading the label as a mode; a label that is no part name is still read as a mode, its typo included ((drak)is dark).astryx experimental theme …: a pasted form is read as the typed one. A var() naming a design token in other letters (var(--Spacing-4)) gets the line with that token, though others of its family are one letter away. A pasted entry with its setting and value in the other order ('pill: corners','{"red":"background-color","on":"card"}') gets the same swapped line as the typed pair. A pasted object of several settings gives each setting's line its scope, from the object's ownon/when/state/mode/onlykeys and from the flags typed with it, and never offers a scope key as a setting of its own. A pasted change line with a mode label and no old value (--color-accent [light only] -> [#7](https://github.com/meta/astryx/pull/7)c3aed) keeps the label as the mode. A change made when the build does not match the saved settings (after a hand edit) says so and lists its token changes against the saved settings, instead of saying the theme already showed it.astryx experimental theme editor set: a pasted object's keys are read as set reads a typed setting name, so a key with spaces around it ({"accent ": "[#7](https://github.com/meta/astryx/pull/7)c3aed"}) is that setting, alone or beside other entries.astryx experimental theme editorpictures (--png) never wait on a network: the picture's browser loads the page's own files only, so a remote stylesheet, font or image a page names (a base theme's Google Fonts import, a template's photo) fails at once instead of holding the picture until the time limit when the machine is offline or has no direct internet.astryx experimental theme editor: a Chrome or Chromium that stops at once (no display, a missing library) is named with its own error when--pngreports the picture was not taken, never with the closed pipe it leaves behind. A typo of a keyword with a dash (cursor not-alowed) is offered the keyword again.- The pictures an agent opens show the overlays, and the output keeps what was missed where a cut output still shows it:
preview.png(the sample page) ends with a strip of a tooltip, a popover, a menu and a select list drawn open, from the overlays the sheet draws.sheet-overlays.pngshows the small overlays first, five to a row, each cell at most 300px tall, and no part of an overlay alone, so it stays under about 1600px.- A change without
--pngnamesshow --pngand the two pictures it writes to open. - A change counts, near its top, the parts the theme's changes did not reach;
showlists them, with their lines, last before its closing look line.
astryx experimental theme editor show --pngand--pngon a change take all their pictures with one browser start, a few pages at a time, so a run of many pictures costs about one start. A focus ring at the edge of a sheet cell shows whole, and the sample page shows a link in its text and one in a card.astryx experimental theme editor's pictures and itsmissedlist show what the theme draws:--pngpictures show overlays drawn open as they look open: each opening animation runs to its end before the picture.- A change that changes nothing counts the parts the theme still misses, as
showlists them. - A base theme's own rule for a state (butter's selected nav item, drawn with no fill) is what the contrast checks and
missedjudge. - An inverted surface that disappears into the page (a toast, a tooltip) gets a line that makes it stand out again, in each mode it disappears in.
- A border line on a part whose variants differ (a button) frames only the variants that draw a box; the ghost button keeps none.
- With the theme's own corners at a pill, no pill part is listed as missed.
show's count line undermissedsays what the rest are: parts whose fill or text color is still the base's, and the other missed parts.
astryx experimental themepictures show what a person sees once the page runs:- A calendar on the sheet shows its days: a part whose server render keeps content inert until the browser runs is drawn as the browser mounts it.
- The open states page draws a context menu (right-clicked), a submenu's flyout, a popover that holds a form, a date and time field's time list, a command palette's items and a narrow screen's navigation drawer. Its drawing asks about the pointer as a desktop's mouse does, presses the controls an opened overlay holds, and closes an open popover when it presses outside it, as a browser does.
- A states section draws each control of the sample page at rest, hovered, focused from the keyboard and pressed: the page marks each one with its state, and the render's stylesheet applies that state's rules to it.
- A nav icon gets the icon its doc suggests, and an icon-only button gets an icon, so neither draws empty or spills its name.
- A border set on the inputs lands on a date and time field's two boxes, not the row around them, so it draws once on each box.
astryx experimental theme editor: settings typed where the theme goes, as a list or a pasted form (show corners, accent,show corners:pill,'{"corners":"pill"}'), get a look at each theme here, never a theme made of them nor "names more than one theme".newreads more settings typed after the name as their options, never as name words: a colon word apart from its value (accent: red), a dial typo (cornres pill),base <theme>as--like, a pasted value across words (font=Inter, Arial), a dial word after an option's value (--accent red corners pill), and a property new takes no option for (padding 8px), offered as asetafter the theme is made; a setting with its value typed as the name (new 'corners pill') is never the name offered.undoreads a value with commas typed unquoted when the theme is left out (undo Inter, Arial), a value then its setting (undo t red accent), and a scope in a spelling set reads (--on Card,cards,--mode drak): the line for that scope's setting leads. An option whose value names another subcommand (editor --on show set t …) keeps it. A mode typed with its letters in another order (--mode kdar) is that mode.experimental theme compilewith no file names its usage and help.astryx experimental theme editorchecks the loading placeholder (Skeleton): one under 1.2:1 against the page or a surface at its brightest, which a person cannot see, is a problem where the theme's colors make it so, with the nearest placeholder color that shows as its line, and a note where the base theme draws it so itself.astryx experimental themerefuses what a build could not apply, at its place, and names the fonts a theme shows:- In an editor theme, null under a style key, a pseudo-class or an at-rule is named once, with a fix that holds no null.
- A pseudo-class or pseudo-element typo anywhere in a selector (
::befor,:hover:focus-visble,:not(:hovr)) is refused with the selector corrected; a block under a pseudo-class's bare name (hover: {…}) is told to start with a colon. - A part's variable in the page's
tokensmap, which the part sets on its own element, is refused with the part-scoped line; a typo of one is named. - A value read from another file is blamed on that file and line, through
export {name}lists, re-exports, namespace imports, imported part blocks and imported single values. - A named pipe, a device or a socket where the app copy goes is refused at once, never opened.
- Fonts: Apple Color Emoji and Noto Color Emoji count as the systems' own fonts. Apple's interface faces (SF Pro, SF Mono, New York) are told by the generic that reaches them (
system-ui,ui-monospace,ui-serif), since browsers do not reach them by name. An installed font package's missing weights are named, a font service request with another axis beforewghtis read, and a weight between the hundreds (550) is named as the face it shows, as CSS font matching picks it.
astryx experimental theme: a stop (Ctrl-C, SIGTERM) duringpreview add,preview removeorpreview appnow ends the command as stopped, with one line saying where the change stands, never[ok]with exit 0; a browser the editor stops at its 60-second bound is said to have timed out, Chrome's startup warnings are no longer given as the reason a picture failed, and a theme folder that cannot be written is named instead of the browser; Chrome gets a profile folder of its own that is removed however the run ends; theseefix for an in-app preview Next does not serve is one that works (preview remove --path …, thenpreview add, or "tsx" in pageExtensions);preview appfrom a subfolder prints a folder andcdthat work from there, and its rule and docs name the project folder as the bound; and from a subfolder, the picture note names every picture with its full path.astryx experimental theme: a change no longer deletes a copy of a picture (such aspreview-before.png): only pictures the editor recorded taking, unchanged since, are removed. Every browser the editor starts for a picture, Playwright included, runs as its own process with a temp folder of its own (removed however the run ends), one 60-second bound and the same stop; a browser that does not start keeps its real cause in the message, and Chrome is named only when there is one. A theme folder that cannot be written is a write failure naming the folder; pictures asked for but not taken are said;preview addfinds a preview renamed by hand instead of starting a second one, through the one list of previewssee, a change's refresh and the preview commands share; a theme the route imports from outside the project folder (a workspace app run from its own folder) is never dropped from the preview; the no-template refusal offers only pages the app can show; a page remove over a theme that does not load names the whole-preview remove; theadd --template <default page>note says what was added; from a subfolder, the wiring's paths work from there; and thepreview removehelp says what happens to a path outside the folder.astryx experimental theme editor: pictures a plain Chrome took are no longer reported as "--png took no pictures"; theseeline nameseditor show <theme> --pngfor pictures, never the command that just ran (an undo run again undoes another change); stopping a change while the browser takes pictures stops the browser and says the change is saved, never a browser failure; a picture's part file left by a stopped run is cleared by the next change and never copied into a new app, and a folder by that name is skipped; an in-app preview route that cannot be written, a damaged preview record and a preview in a folder Next does not serve (src/app/under a rootapp/, page extensions withouttsx) are all said, with no URL that would not load;preview appcopies none of a theme's pictures or preview pages; and from a subfolder,preview listandremovetake the folder they print, and the picture note andpreviewStalename files the wayseedoes (absolute).astryx experimental theme: with Playwright in the project, pictures try Playwright's own browser before the system Chrome, and the advice names only a fix that can help (Playwright's browser only when it is missing); the Chrome lookup passes over a folder or a file that does not run and keeps looking on PATH; a change keeps every in-app preview of the theme in step, including one renamed by hand or whose record was lost, the same previewsseenames;preview add --path app/<x>in a src/app project says that a root app/ would stop the whole app in src/app/ from being served; thepreview apperror table names the project folder as the bound; and a stop that lands after a preview command printed its result no longer turns that ok into exit 130.astryx experimental theme editorandpreview:preview remove --pathgiven a file is refused with the preview's folder (it reported an unknown error). Pictures are taken under a part name and moved into place, so a--pngrun stopped while the browser runs leaves nothing the next run reads as a file of yours. Theseeline namespreview add --theme <name>when the project has several editor themes; gives no URL for a preview moved where Next does not serve it, saying why; says preview.html could not be written when a folder is in the way; says what blocked--pngwhen a picture of yours did; names files by paths that work from a subfolder; and says when the in-app preview was changed by hand, aspreviewStalenow does with what to move out. The show help says pictures change nothing in the app, except that show first brings the app copy up to date after a hand edit. A dial value labeled with another setting (accent 'neutral: [#64748](https://github.com/meta/astryx/pull/64748)b') is refused with that setting's line. The input cleanup reads corner brackets as quotes, keeps escaped quotes and brackets inside strings, reads a light and a dark color typed as a pair (offeringlight-dark()or two--modelines, or one color for a dial), splits a JSON object of several settings into one line each, reads a JSON-escaped font stack, maps--mode nightanddayto dark and light, and readsvibrancy 0.5and"50"as 50; a saved value with paste debris or!importantis offered cleaned.astryx experimental theme: pictures taken with a Chrome or Chromium (no Playwright) are whole-page pictures, the same as Playwright's, through the browser's DevTools protocol, never the top 2400 pixels only. Every browser the editor starts runs under one runner: a temp folder of its own (a run with none is refused, never started on the person's own browser profile), one time bound per browser with the next browser tried when one hangs or fails (and not tried again for the next picture of the run), and a stop (Ctrl-C, SIGTERM, or the terminal closing) that closes the browser's whole process group and removes its temp folder and the unfinished picture. When a later browser took the picture, the result says why an earlier one did not, with its real error. A picture file of your own (preview.pngof any size) is never taken over: only pictures the editor recorded or stamped are.preview addfrom a workspace app's folder keeps a theme the route imports from outside it, aspreview removedoes; two starter apps frompreview appnever share a package name; refusals name commands that work when followed (each app's own folder from a workspace root, a free folder for a starter app, a page this app can show); and the note that the app does not import Core's stylesheet reads the layouts' real import statements.astryx experimental themeandastryx experimental render: a stop (Ctrl-C, SIGTERM, or the terminal closing) while pages render removes the render's temp folders. A page with a root Theme is written with that Theme's attributes on<html>, as Core's root Theme sets them in a browser, so root-scoped tokens such as the focus ring's color follow the theme in the preview and the sheet. Everypreview appcommand a result names works where it is printed: a folder starting with-goes after--, a folder is given from the folder the command ran in, a theme a workspace app holds is reached from that app, and a repaired folder name is a free one. A starter app gets every open font the theme builds, installed in this project or not. A change names the pictures it removed (the preview's and the sheet's) and keeps a section sheet's.preview app --themerefuses a theme whose own files import a file outside its folder, which the new app would not have. A stop duringpreview appsays whether the app was written whole or nothing was written.astryx experimental theme: a theme with both modes gets a sheet and preview that render each part as the app renders it in each mode (a Toast in dark is the app's dark Toast, no longer a blank bar), the page showing the render of the mode it is in. From a workspace root, a folder in a workspace app gets that app's own checks (its routes folder, public/, build folder, themes/, Pages Router, unrouted folders); the pointers to an app below keep every argument (--theme,--template,--top) and use--pathfrom a project root; a theme that a workspace app holds is named there, with the command run from that app. Every pointer is one its command takes:preview addonly where add takes the folder, a starter folder free of any file, dangling link or case twin, acdthat a folder starting with-does not break, andeditor show <theme> --pngafter a stop during the pictures. Starter apps get package names that never collide. A preview moved into a folder with a space or another character no plain URL takes is updated where it is. A second Ctrl-C while the pictures stop kills the browser at once and removes its temp folder.astryx experimental theme: a refusedpreview app --themeorpreview addwrites nothing: a stale theme it builds first is put back when the build fails (a theme source that does not load), so the same command is refused again rather than copying an old build.preview app --themerefuses a theme stylesheet url that leads out of the theme folder (the new app would not build), a theme file too large for one read, and one that cannot be read, each by name (a read, never called a write). A named pipe or a device at a file the editor reads (the preview record, a page, a picture, the pictures record) is never opened, so no command hangs on one. Theme image names are URL text (a%20b.pngis "a b.png"), and a quoted url may hold parentheses; an image that cannot be read is left out of the previews with a note. A section sheet's pictures go with the others when the look changes, and the command that takes them again is named. A starter app names the weights of a font it adds that it does not load.preview addreads a typed dash form of its options, and beside a description offers only a--templatepage this app can add;--topbeside a default page, or alone, offers the command without it; an empty--themeoffers the preview command with each theme.astryx experimental theme previewreads each preview page once per element when it checks whether the page was changed by hand: a page whose JSX nests deep took time that doubled with each level, sopreview addandpreview removewere slow on the generated pages.astryx experimental theme: a preview picture's browser makes no network request of its own (no update, time, sync or metrics checks, no proxy, no host name resolved), on the Chrome and Playwright paths alike. A theme file that is not a regular file (a named pipe, a link to a device) is never read, soshowcannot hang on it.shownames the theme images the previews cannot show (loaded from the network, not found, not a regular file, or over the size a preview page carries), and an image too large for a preview is refused with its name and size instead of as a React failure. Extra words topreview app,preview listandpreview removeget a command that works and the command's help.preview app --themefrom a workspace root gives thecdto the app. A description longer than the words read is quoted as typed, and a refusal says it was cut. A--templatetypo names only pages this app can add now.astryx experimental theme previewand the starter offer lines that work and name what is in the way:preview removewith no preview yet offerspreview addonly where add can work; elsewhere (an app with no root layout) it offers what add itself offers there.preview app --themerefuses, before anything is written, a theme whose import without its extension (./helpers) loads a link inside the theme folder, and one whoseurl()names no file (a wrong-case path); a folder in the theme folder it cannot read is named as a read, not a write.- A named pipe or a device at
sheet.htmlorpreview.htmlis left as it is and named, as at the open states page's name, never written over. preview app --themegiven a theme as a path or a list offerspreview app <folder> --theme <theme>, never a look at the theme.
astryx experimental theme editor: a change's new problems are the ones the theme did not have before it, compared by what each problem is (the text, what draws it, what it sits on, its variant and mode), not by its printed ratio, so moving a color that leaves the same text low makes no new problem.astryx experimental theme editor: a problem a change makes leads its result. The status line counts the new problems, and each follows under it with the command that fixes it: the text token set where the text sits, or the border color, for the mode, to the black or white that reads there. A color that fails its contrast check is a new problem too.showends withopenProblems, every contrast problem the theme has now with its fix (the JSON lists every one; the text shows the first eight and counts the rest). A text token set on the part the text sits on (card text on the card) now counts for the text inside it, so following that fix clears the problem, and a border set again for one mode is measured as set.astryx experimental theme editor:openProblemsandnewProblemslist every contrast problem in JSON, and a change's new problems are compared against all of them, so following one fix line no longer reports old problems as new. The text shows the first eight and counts the rest.astryx experimental theme editor how: a progress bar's height ("progress bar 4px tall") is its track's, never a strip of fill over the unchanged track; a date picker's selected day says its calendar is the plain Calendar and names the calendar day's selected state, as its today does, never "date-input has no selected state".astryx experimental theme editor …: a set of a property typed in other letters (set t Background-Color green --on card) is that property, so it fixes that property listed twice in the settings file, instead of a refusal that offers a swapped line back and forth. A top-levelbasein the settings file (the editor's word for it) is read as the base, with a note, instead of the theme building on no base, and any other top-level field the editor does not read is named, with the field it is a typo of. A saved setting with no source and its part under a field the editor does not read ("part") names that field and offers the undo that removes it, instead of only a remake.astryx experimental theme:- A pseudo-class after a pseudo-element that takes one is accepted: any after
::file-selector-buttonand::details-content,:window-inactiveafter a highlight such as::selection,:target-currentafter::scroll-marker. One that does not take it is refused with what it takes. - Only
:hoverand:activewritten in capitals are refused, the two names Core reads;::BEFOREor:FOCUSbuild as written. - A part property that builds dash-first without a vendor prefix (
Color,BACKGROUND,-webkit-) is refused, with the name in lower case. - A tokens map spread from a defined theme's tokens no longer trips over Core's own private copies in it; another private variable it carries is named as coming with the spread, with the way out.
- A value read from another file is blamed on that file through an array element (
cs[1]), a template (`${c}`), a choice (B.x ? B.x : '#fff'), a call of a global or a function of the theme file's own (String(B.x)), andawait import().
- A pseudo-class after a pseudo-element that takes one is accepted: any after
astryx experimental theme:- In an editor theme, a pseudo key that is no single selector is refused at its line: one that leaves a parenthesis, bracket, quote or comment open (
':nth-child(2n', with the closed form offered), one no browser reads, and a selector list (':hover, :focus'), which is named with one key per member. A plain theme'scompilewarns them, astheme builddoes. - In an editor theme, a custom property with capitals in a part's block is refused: the build writes a part's property names in kebab case, so
--myColorwould be set as--my-colorwhilevar(--myColor)reads the name as written. A plain theme'scompilewarns it. - A variable a component sets on its own element is refused in
localTokensand in another part's block, with the part that sets it. On its own part,var()of that variable reads it. editor seton a theme whose stylesheet is a named pipe gives the pipe refusal, never a failed module load.- A value read through an imported object's member (
all.toks), a destructure of one, an imported function's return, or an imported typography object is blamed on the file that holds it. - A null value in the theme's own file builds as it is with a warning at its line, as in any theme; a null part or style key is still refused.
compileof a missing file near the theme source (themes/t/t.theme,t.them.ts) offers that source.
- In an editor theme, a pseudo key that is no single selector is refused at its line: one that leaves a parenthesis, bracket, quote or comment open (
astryx experimental theme editor howreads more questions the way they are asked:- "make cards the color of the page" gives cards the page's color and never changes the page ("but 10% darker" steps that color in each mode; an amount before "lighter" or "darker" after "but" stays with the ask);
- "make dialog shadows 50% more transparent", "20% less opaque" scale each shadow layer's own alpha, in each mode, instead of writing one alpha on every layer; a part that draws no shadow of its own says so;
- "make borders 3:1 contrast" gives the border color at the lowest strength that measures that ratio against the page, surfaces and cards in each mode, instead of a fainter border;
- a bound on a whole-theme ask holds: "padding bigger but at most 2px" (the base spacing step is past it) and "corners square but at least 8px" (square is 0px) write nothing and say why;
- "make shadows use 20% black" sets each shared shadow's layers in that color, offsets kept, and a color written as a function (color-mix(…, transparent)) is never read as a "transparent" ask;
- "what color is the text", "what color is the accent", "what is the body text size" answer with the theme's value in each mode it shows;
- "more colorful" and "less saturated" are judged by how colorful the accents look (OKLCH chroma, the measure vibrancy moves), so a pale accent such as butter's dark yellow can be made more colorful.
astryx experimental theme editor howchecks its answer against what the question means: a part the question only compares against ("rounder than buttons", "darker than the page") is never changed, and the answer says so; a prohibition ("don't make the cards bigger", "buttons should not be rounder") changes nothing and says what stays; a question about a value ("how much padding do buttons have", "what color is the button") answers with the value now. Comparisons write onto the first part only, with a typed offset ("4px rounder than buttons"), its variant and state, and the property the words name ("button text the same color as the card text", "input border the same color as the button background"); two parts that should match copy one value, or say they already match. "Except" keeps an exact radius change, a text size change, a variant beside a part, small and muted ones, and a state. A side border ("remove the top border"), close icons and header titles, "inputs with errors", a heading level ("red h1"), a part's own radius, text colors for two button variants, an elided second clause ("… and darker when pressed", "… and half on ghost ones") and "buttons inside cards" (the container is kept, and the answer says the part changes everywhere) are read as asked. A theme name typed in another case keeps the question.astryx experimental theme editor: on an installed Core that draws a radio's circle with the pill token (--radius-full), squaring the pills ("no rounding anywhere", the square-corners note) keeps the radio marks round with that token at Core's value on them. On a Core that draws the circle at 50%, no pin is written. The "thick borders on everything" answer also frames the label boxes (badges, tokens).astryx experimental theme editor: the cached part data is rebuilt once more, so a calendar's range band is read in a cache built before it was drawn.astryx experimental theme editor: the part data draws a component whose look names its value's kind (a calendar's range mode) with a sample of that kind (a range of days), so what Core draws for it, the band behind the days in a range, is read: "the calendar range band blue" sets the token it paints with on the calendar. A shadow or border asked of a part drawn inside an overlay that paints its edge for it (a typeahead's list, in its popover) points to that overlay, saying a change there reaches every one, and writes nothing.astryx experimental theme editor: one reader for each kind of input, on every path.- A family list reads each family from its end, on the font dial, a family token and a part's
font-family: a size, a weight or a style after a family's name (Inter 16px,Inter Italic) is refused with the family and the size's, weight's or style's own line; a bare number in a list (Lato, 16) is a weight only as a whole hundred; a misspelled generic (sansserif,serf,system ui) or, on the font dial, preset (sytem) is offered as that name, never saved as a family. A family the editor knows keeps its last word (Source Sans 3,Arial Black 900is Arial Black and a weight). - A swapped setting and value is offered only when set takes it as typed, with the scope typed, never a sample command on a part nobody named.
- A property written with
_or spaces (font_size,"border radius") reads as the property, as camel case does, and gets the same answer. - One yes/no reader for a flag given a value and a saved
only: the documented spellings of yes and no, or a typo of one; any other word is refused with no line guessing it. The line offered is checked as every repair is. --modereads a word that names one mode (dark-only,darkmode,dark mode) as that mode, in set and undo alike.- A pasted object of one entry gets that entry's repair.
- A saved value that set repairs (
headings "blod",spacing "romy",text-size "16px") is offered that repair beside the undo. - A damaged base or mode is offered the lines that set it again (each installed base, each mode), never a default that drops it; a base written with
theme(neutral-theme) is that base.
- A family list reads each family from its end, on the font dial, a family token and a part's
astryx experimental theme editor: a typo of a font preset reads as that preset when the preset and the system family it names both match (Verdena,Segoe IU); a family near a system font only (Times New Romna,Arailin a list) is kept as typed, with a note whose line sets that font.showandcompilegive set's repair for a damaged saved value beside its undo, as every change does, and an entry saved in a typed form (corners: pill,red --on card) gets the reading set gives it. The editor's own printed setting line pasted back (corners = pill (whole theme),opacity = 0.5 on card) carries its scope. A dial saved for one mode is refused assetrefuses--modeon it, never built for both modes or for none.set mode nightreads as dark only;undocompares colors as colors (#F00is the saved#ff0000); two headings words (bold wide,bold and wide) are onenewline, and set's second line is the next step; a token in another style (--color_accent) or with a typo is offered as the token.astryx experimental theme editor setpoints at a line that works and says what happened. A word that names a dial and its value (shadows none,elevation none,dark-mode true) offers that dial's line (set t surfaces flat,set t mode dark-only) whatever the theme has now. A state a part does not have names the part drawn inside it that does ("today" on a calendar offers the line--on calendar-day --state today). A no-opmodeorbaseset says nothing was built and no undo step was added, as every other no-op does. A theme with one color mode lists its own mode's token changes first.- Receipts say what happened:
astryx experimental theme editor setof a value the theme already has reads "font = system (whole theme) was already set; nothing changed" in place of "system -> system"; anundonames a setting that still applies where the removed one did ("#fef3c7 in light mode and the base theme's value in dark mode"), never the base value alone; and a theme set to one color mode saysastryx theme add <theme>records the mode and its wiring passes it, in place of reading as a manual step. A dial already at its last rung names an exact size that goes past the rungs (set t text-size 18), beside the step the other way. astryx experimental theme editor: a refusal offersnewto make a theme again only for a settings filenewitself remakes; a setting listed twice gets its keep and remove lines, and aliftedfield that is no list of text is dropped (the build writes it again).newrepairs a value as set does: a line never adds a setting nobody typed (a mode read from a color's words), a did-you-mean reads the whole value typed,howis named for a value no reading makes work, and a repaired value (ff0000as#ff0000) stays in the line. Words of a flag value typed unquoted onnew(--font Open Sans) belong to that value, and the line offered is checked as new checks it. show and the preview commands read their options with the one option reader, so a did-you-mean always matches the command offered. A base that is not installed leads with the install, then the set, and a theme already on a base is not offered no base. A part and its variant written in other letters together get the line that works. A corners size saved in rem is read as the px set saves it as.astryx experimental theme editoroffers lines that run and do what they say:- A setting and value in the other order beside a mistyped option (
set t red --color-accent --mdoe dark), or with a spaced name beside a part typo, get one line with both repairs. - A
var()naming a token one letter off gets the line with the token repaired, typed and as the repair of a saved entry beside its undo. undonaming two settings of different scopes (undo t spacing background-color --on card) offers one undo for each, never one that drops the other.- After a plain part fill, the "to fill only one of them" and "to change only its fill at rest" lines start with the undo of that fill.
new --baseoffers the--likeline asnewchecks it (an install first, other flags repaired).new --font Open Sanswith no name reads Sans as part of the font, and offers a free name.--mode light --mode darktogether read as both modes.- The editor's own lines pasted back keep their repairs in the arrow form (
accent tomato -> tomatoe), read a mode label in any case or withmode/only((Dark),[dark only]), refuse a mode typo with its line, and keep a printed scope in another case (on [Card](/components/Card),:Hover). - A pasted entry's field keys are read in any case (
{"Thing": …, "Value": …},"On"). - The line that drops
--onlykeeps every other scope flag.
- A setting and value in the other order beside a mistyped option (
astryx experimental theme editor: lines offered work as the person will run them. Anewrefused for its name keeps each misspelled value as new repairs it for a free name. A word after--like <base>is read into the name, never glued onto the base. A damaged saved entry's set line is offered on its own only when it replaces that entry; otherwise it is labelled as the step after the undo. A typo of a built-in base reads as that base, installed or not, with its install first (set,new --likeand a saved base alike), and an unknown base getshow base, neverbase nonefor a theme on a base. A thousands comma reads as such on a property that takes only whole numbers (z-index '-1,000'), and a comma in a ratio is a pair only between whole numbers of 1 or more (0,75is 0.75). An undo naming several settings offers one undo each; an undo with only a scope offers a step back only when there is one. A setting pasted in the saved form, or beside its scope keys, is one setting with its scope as flags. A word after a mistyped yes/no option is left out of the line and named. The settings reader reads a savedonlyof 1 or 0, refuses a vibrancy with no color as set does, and a saved step word steps from what applies without it.astryx experimental theme editor: a repair's offered value reads the whole typed value, never a subset of its words. A line may carry part of the value only when the refusal's other lines carry the rest (Inter 600gives the family and the weight,italic boldon a part gives the style and the weight); a part alone (allforall 200,boldforextra bold,5for0,5) is not offered.- A comma between digits is a decimal point (
1,5remis 1.5rem,0,5is 0.5), or before three digits after a whole number a thousands mark (1,000on a weight is 1000), never a split into layers. - Several values of one kind for a property that takes one offer the first as typed, with px only when the property takes no bare number (
line-height 1.5 2is 1.5), and never one value of a shorthand of several kinds (transition all 200getshow). headings extra boldoffers heavy (800), andtext-size x-largeoffers 24, the size CSS gives it.moreorlessauthorizes a computed value only on a dial with a scale: a token, a part property or a dial's other name given a step getshow, never a stock color, weight or size.- A saved value authorizes only a keep line for its own setting, never the setting being typed, so
base buterno longer offers the base the theme already has. - A light and dark pair on a part's color in a one-mode theme gives the half that theme shows, as a token does.
- The note about a second pasted declaration names its line only when
settakes it, or the linesetoffers for it.
- A comma between digits is a decimal point (
astryx experimental theme editor: every value a refusal or a saved-settings repair offers now passes one gate, and each offered line is checked assetchecks it before it is shown. A value may come only from these sources:- What was typed, under exact readings: quotes, labels and copy debris (a trailing
;,!important, a comment) taken off; the same number written another way (full-width digits, a comma decimal, an exponent, rem or pt as px, a percent); CSS color names written as words (dark redisdarkred). - A documented table: Tailwind's radius classes (
rounded-lgis 8px), a dial's own words, a weight word, a number read as a dial's nearest rung. - The theme's own saved values, for a keep or unlock line.
- The setting's documented fallback or other-direction step.
- The correction of a typo of what was typed: one letter off for a word of five letters or fewer, two for a longer one.
Anything else, such as a stock color, a stock shadow or easing, a reset, a default token or a nearest guess, giveshow <thing>. A scale step (red-500) is no bare color.Also:font 'Inter 600'offers the family and the weight separately.- A Google Fonts spec (
Inter:wght@400;600) offers its family. - Another property's label on a part property (
padding 'margin: 8px') offers that property. --color-dangeroffers the error token, and--color-primaryor--color-brandthe accent token.- A CSS property typed for the whole theme leads with its dial or token (
border-radius 8px→corners 8px), never a part that was not named. - A pasted object's nested values are read, and each of its lines is checked.
- A bare fraction on a size token gets no px guessed.
- A very long input is near nothing.
--state 'hover,focus-visible'gives one line per state.- A saved light-dark pair for one mode is refused with the half for that mode.
- A CSS-wide keyword on a token offers the undo only when the theme sets the token.
- What was typed, under exact readings: quotes, labels and copy debris (a trailing
astryx experimental theme editor: repairs follow the readerssetalready uses.- A saved property name with a space or capitals (
"background color") is repaired bysetin place: the line replaces the broken entry, and the theme loads again. - A unit typed after a space joins its number for every CSS unit (
50 %,50 vw,200 ms,1,5 rem), not only px, rem and em. - A typo in
--when(variant:primray,siez:lg) offers the same command with--whencorrected. A saved one gets the undo, then that line, so the setting is kept. undo <thing> <value>with no--modeis refused when the setting is saved for one mode with another value, and names the saved value and its mode.new --font 'Inter 600'offers--font Inter --headings semibold, assetreads the same value.- A saved entry that names its thing under
setting, a saved entry with the setting and value the other way round, and a saved mode of"both"or""are read assetreads them typed, with a note, so the theme loads.
- A saved property name with a space or capitals (
astryx experimental theme editor: repairs work when followed. A damaged mode or base with a second bad value in the list leads with the fix for that value, which also saves the mode or base as meant, and no repair offers a bareundothat would throw away the last change. A stored vibrancy is offered as a set only when a color dial is set, and the no-effect refusal names a token color as one vibrancy does not change.undowith a theme name typed in another form (tTheme,T,brand_dark) suggests the same undo with the theme's name. A missing name with a doubled or trailing dash suggests the cleaned name thatnewtakes. The tracking half of headings listed twice is undone withundo <theme> headings tracking, the form that works. A trailing comma or a typographic dash in--on(text-input,,text–input) names that part, never its whole group. A light and dark color pair onnewoffers the user's own colors per mode, never a stock color. In a one-mode theme, a doubled entry for its own mode is kept with that--mode, which now replaces both entries.astryx experimental theme editor: a reset value typed with a typo on a part property (display nnone,font-weight normall) offers that value again (none,normal), since it is what was typed, corrected.astryx experimental theme editor: a resting shadow on a part that draws rings in its box-shadow (an input's hover and focus rings, a status's ring) is written, and in each state Core rings it the theme's shadow comes with that ring after it, so the rings keep working; a shadow the theme sets for a state keeps its own.how "sunken bevel on inputs"answers with an inset bevel lit from the bottom right.astryx experimental theme editorresults say what the theme does: a mode's own setting under one for every mode names the one still drawing the other modes, with its undo; an inverted surface left as the base's is given the theme's own other-mode surface (a warm dark tooltip on a cream theme), or its surface in a one-mode theme; a token set on the top bar reaches the text over its ground, and a fix for that text stays in the top bar; a container's faint border, or a hairline where the base draws one too, is a choice, and a border or secondary text that needs a fix gets the nearest color that reads, not black or white; pills are listed as missed only when the corners go square; the open problems header and the missed count say which lines exist and where each miss is listed.astryx experimental theme editorlists under missed a part where the base theme takes a role color away on its own, once the theme moves that role: the base pointing the role tokens at others there (an info banner drawn in the base's categorical blue), or a variant named for the role drawn in a color of the base's palette written out (an accent progress fill in a pale blue). Each line gives the part the theme's role color there.astryx experimental theme editor: what is pasted is read as meant, and a repair carries the value given.- A repair never offers a stock value the input did not hold (a gray, a violet,
inter,system,1px): a line that sets the same setting again carries the value typed or saved, cleaned, elsehowfor the setting. - A value labeled with a word that is not the setting's own name is refused with what the word means, never set with it dropped: a mode (
accent 'dark: [#2563](https://github.com/meta/astryx/pull/2563)eb'offers--color-accent '[#2563](https://github.com/meta/astryx/pull/2563)eb' --mode dark), a state (set on a part with--state), a kind of screen (not set per screen), a part (--on <part>), a heading level (headings 'h1: bold'offersfont-weight 700 --on heading --when level:1), or a word it does not read. The setting's own name before the value is the value (font 'fontFamily: Inter, serif'); a camelCase or quoted label of another setting names it. - A size multiplied by a variable with a number fallback (
calc(0.75rem * var(--x, 1))) is taken. - CSS function names in any case are read (
LIGHT-DARK(…)); alight-dark()with another separator offers the comma; a font list missing the comma before its generic family (Georgia serif) or with a spaced generic (sans serif) offers the list meant. - A backslash before
#, a quote or a space is taken off; a JavaScript escape in acontentstring is written as CSS writes it (\u2022is\2022); JSON arrays and design-token objects ({"$value": …},{"value": 18, "unit": "px"}) are read as their value. headings lighteris the weight light; two headings words give one line each.- The change receipt names a quote or space mark as its CSS escape, so text and JSON name the same value; a saved value in corner brackets is named as quoted, not as spaces.
- A repair never offers a stock value the input did not hold (a gray, a violet,
astryx experimental theme editor: several values of one kind on a property that takes one (margin-top '-4px -8px',padding-top '1pt 2pt') are offered the first again, with its sign and any unit: the repair and the repair gate read "several values of one kind" through one shared reading.astryx experimental theme editor …: a saved setting that writes one field two ways (valueandValue,onand--on) is read the editor's way with a note naming both, and the next change writes the field once. A pasted declaration whose unquoted value went on past a space (set t font=Inter, Arial) is read whole, so the line offered with the theme left out works too.astryx experimental theme editor: a saved font family in French quotes (« Inter », with plain, no-break or narrow no-break spaces) is offered as"Inter", the value set saves, not" Inter ".astryx experimental theme editor: names saved in a spelling--stateorsetreads typed are read the same way, with a note naming the spelling saved. Before, every command refused the theme. This covers:- a part's own state in other letters or with a space, an underscore or a colon (toggle-button's
IsPressed,is pressed,is_pressed,:isPressedfor isPressed); - a CSS property in other letters (
Background-Colorfor background-color).
A state's prop name typed or saved in one case (--state ispressedorISPRESSEDon button,isselectedon tab) is that state, asisPressedandaria-pressedalready were.- a part's own state in other letters or with a space, an underscore or a colon (toggle-button's
astryx experimental theme editor:--onlynow means one thing tosetand to the settings reader. A savedonlyon a part that is styled on its own (as another editor version saved it) no longer stops the theme from opening. It is read and built as without it, which is what it means there, and one note says so; the next change saves it so. Where that puts it at the same place as a later entry of the same setting, the later one, the one the build shows, is kept, and the earlier one is named and left out.set --onlyreads it by the same rule.astryx experimental theme editor: a state saved in a spelling the editor reads (aria-pressedon toggle-button) is named by the part's own state (--state isPressed) in every line the editor offers, even before a change rewrites the saved entry.astryx experimental theme editor how: "lighter" or "darker" on a part's fill starts from the fill it shows at rest (its own setting first; never a pressed overlay), uses the amount asked and keeps a see-through color see-through. "except" keeps every excepted part or variant at the value it has now (its own shadow, its own weight) in one answer, says when a part reads none of what changes, and says when an excepted place is not a part. Sub-parts and catalog parts named in words go to that part ("dialog header", "dialog title", "code block header", "text inputs", "date pickers", "toggle buttons", "select boxes", "switches"); a sub-part Core lacks ("card header") is answered for the whole part, and the answer says so. "As round as", "the same padding as" and "match" copy the other part's value onto the first part only (an amount of it with "twice as round as"). Each clause keeps its own variant; a bare size in a list of text changes is the font size; "headings 20% bigger" scales every heading level from its own size; a font stack stays whole on the part; side words write only those padding sides; a part whose name has a state word ("hover card") is the part; "card text lighter" and "dialog text twice as big" get commands; a second part with an ask of its own keeps it; and a theme name near the one typed with--themesuggests the same question.astryx experimental theme editorcontrast-checks a change limited to one state or condition (a selected row's fill, an info banner's fill) like any other: the part's text is measured on its fill there in each mode, and a problem comes with the nearest readable color, set on what draws the text in that state or condition, instead of a "not checked" note.astryx experimental theme editor how: a part kept to its container ("buttons inside cards", "headings in cards", "the card title", "the button groups' dividers") is answered only with a token the part reads, set on the container, which keeps it there ("headings in cards bigger" and "the card title bigger" set the heading sizes on the card); a part's own setting would reach every one, so then nothing is written, and the answer says why.astryx experimental theme editor setandnew:- A new part setting that writes the same token reference Core already uses there, at rest and in every state, such as
border-radius var(--radius-full) --on badge, is no longer written, and the result says "[no change]". A setting whose value only matches what the part draws today, such ascorners pill --on badgeon a round badge, is written as the person's own choice, and the result says it matches and holds if that token changes. - The "missed" line that
newandsetprint near the top now says what it means: each part it names, with the variant and state (or at rest), still shows the base theme's own look where your changes did not reach. Keep each one, or bring it in line with the lineshowlists for it. The JSON lists the same places asmissedWhere.
- A new part setting that writes the same token reference Core already uses there, at rest and in every state, such as
astryx experimental theme: the settings a theme's source extends are the settings module's own export, by identity anywhere up itsextendschain, so a theme merely named like the settings is refused and one that reaches them through another theme is accepted. A source that stops loading is refused byshowand never recorded as built.compilebuilds a family in afontshorthand like any font, leaves a family the app copy loads out of the full font help family by family, names a theme folder it cannot write with its fix, says in its JSON result the--outwarnings text prints, and says that an editor theme's next set or show builds it without--icons-specifier.setandshowgive the install line for every built family nothing loads, a font token's included. A theme or anextendswritten as a helper's call or a conditional is named as what the build cannot follow, not as an inline icon registry.astryx experimental theme editor show --pngcuts a family's picture taller than 1600px into pictures of at most that height, in order (sheet-inputs-1.png,-2…), each cut between parts, so a reader takes each in whole. The pictures show a looping animation (a skeleton, a pulsing dot) at a frame a person sees, a status dot in its color, a vertical divider at a height, each table, code and app shell variant on a row of its own, and a section's sample text; a deprecated part, and a closed overlay the open states draw open (the mobile navigation drawer), are no longer drawn as empty cells.astryx experimental theme editor showdraws every part of the sheet and its pictures whole: a cell grows to what it holds instead of cutting variants at its bottom; a table, a code block and an app shell take the whole row; a looping animation (a skeleton, a pulsing dot) is drawn at rest; and a section or a form layout holds sample text instead of nothing.astryx experimental theme editor showshows a look's overlays open and names the parts the look leaves unchanged:- The sheet's overlays section draws each tooltip, popover and hover card open beside its trigger, each drawer, bottom sheet and lightbox at its cell's size, and, open, each part another section holds whose control opens a menu or list (a dropdown menu, a selector, a tab menu), in light and dark, so its pictures show how a look styles them.
shownames, asunreached, the parts with a fill of their own the theme leaves on its base's look: no setting is on them, and their fill or text color is still the base's (for example toast, banner, badge).- The author-a-theme guide opens with the theme editor, and a search for brand colors finds the theme topic.
astryx experimental theme editor: a shorthand set for one mode points to commands that change that mode only.- A shorthand with a color longhand (
border,border-top,outline,text-decoration,background) set with--modepoints to its color longhand for that mode and its other words (width, style) for both modes, so following it never repaints the other mode; a named color counts as a color. - A shadow's color for one mode is offered in the value as
light-dark(): on a part with no shadow of its own, the other halftransparent; on a shadow token, each layer's other half kept from what that mode shows, or a true reason when the layers differ. set --helpandundo --helpsay a light-only or dark-only theme takes--modefor the other mode, which applies where Core draws that mode.- A light-only or dark-only theme lists the other mode's token changes it writes.
- A shorthand with a color longhand (
astryx experimental theme editor show --pngtakes the sample page, the open states, and one picture for each family of components the theme sets a part of with--on, a group of parts counting as its parts (actions, inputs, selection, navigation, feedback, data or containers; the buttons when it sets none), each cut from the full sheet:sheet-<family>.pngfrom thesheet-<family>.htmlit writes beside the sheet. A family taller than 1600px is cut between rows of parts into pictures of about that height, in order (sheet-<family>-1.png,-2…). The full sheet, every component, is still written as sheet.html but is no longer pictured as sheet.png, which was too tall to read whole.show --section <family> --pngtakes any other family. The result names the family pictures first among the pictures to open.astryx experimental theme editor show --theme <name>(the formsetandundoalready repair) offers the show on that theme, saying the theme is show's first word, in place of its help alone.astryx experimental theme …: starter apps, pages and pictures say and write what is true.preview appwith--themegiven no value says so and offers only lines that work; with no folder, it offers a free folder name and its help.- A starter on a variable Fontsource family no longer says it loads weight 400 only: the weights its stylesheet loads are read from the package, and no import of a file the package does not ship is offered.
- A starter leaves the theme folder's version control (
.git) and installed packages (node_modules) out, with a note, and refuses before writing when an image url reaches its file through a link the copy does not follow. - The overlays picture draws every example of a drawer, a bottom sheet and a lightbox.
- A file of yours at
preview.html,sheet.htmlor a section's sheet is left alone and named, as one atsheet-overlays.htmlalready was. showon a theme source that does not build offers the build failure's own way on.set --pngnames as removed only the pictures it did not take again, andshow --png --sectiontakes the open states too, as the help says.preview removesays when nothing was removed.
astryx experimental theme preview removein an app made bypreview apptakes the starter home page's link to the removed preview, and names a home page changed by hand that still links there, instead of leaving a dead link with no word.astryx experimental themestarters and pictures say and write what is true:- A starter's note for a font the CLI does not know names the stylesheet of each weight the theme uses, not the package's index sheet, which loads weight 400 alone.
show --png --section overlaysmakes, photographs and lists the open states page once.- A starter leaves out every version-control folder (Sapling, Bazaar, Pijul, CVS, Fossil and darcs beside Git, Mercurial, Subversion and Jujutsu).
- A pipe or a folder at the pictures record is left as it is and named, and no picture is taken; the editor's writer never replaces a pipe, a device or a socket.
- A write of the same bytes a file already holds leaves the file as it is, so a refused command that puts back what it built changes nothing.
astryx experimental theme preview app --themejudges an import written as a template literal with nothing put in it (await import(`../shared.ts`)) as the string it holds, so a theme file outside the theme folder, a Sass file or a name the new app cannot type is refused there as it is when quoted. A query or a hash on any module the theme imports (./x.ts?raw,./d.json?raw) is refused too, since the new app's type check reads it as part of the module's name.astryx experimental theme preview app --themerefuses a theme that imports a stylesheet in a language other than CSS by the same list the theme build loads (Stylus, PostCSS and SugarSS beside Sass and Less), and with a query after it (./brand.scss?inline), before anything is written. Before, those starters were made and the new app's type check stopped at the import. A refusal that comes after the theme's stale build was made again puts that build back, so the refused command changes nothing, as it says.astryx experimental theme preview app --themerefuses a theme that imports a file only a bundler loads by a name the new app's type check has no declaration for: a CSS file with a query or a hash (./brand.css?inline), an upper-case extension (./brand.CSS), or a font file (./brand.woff2). Before, the new app was made and its type check stopped at that import. The declarations it reads are the new app's own (*.css) and the pictures Next declares. A refused command that put back a build it made first now puts back each file's and folder's times too, so a dev server or watcher sees no change.astryx experimental theme preview apprefuses a starter whose theme reaches a file outside its folder withimport x = require('…'), or with a/// <reference path="…" />at the top of a file, which the new app's type check reads, as for any import.astryx experimental theme editor show'smissedandunreachedlists name only what was missed, and each fix line works when followed:- A state is named only when the part draws it as a look of its own (a selected nav item's fill); a readonly field on its surface and a checked switch's thumb are drawn so on purpose.
- A setting takes a part off a list only when it covers the aspect the list is about (the resting fill or text color, the fill in that state, the corners, the border); a hover fill or a corner radius leaves it listed.
- The disabled button's line covers only the variant drawn as the accent, and recolors its label with its fill.
- A status fill's line generates that status color (
set <theme> info …), never the accent. - An inverted surface (a toast) is named only when it no longer stands out from the page, with how's answer for it.
astryx experimental theme editor: state settings keep the base theme's other state styles, one-mode halves across the background family and states, and one-mode tokens that are no color.- A state setting (a hover text color, say) keeps the base theme's other styles in that state, such as a variant's own hover background, in both modes.
- A one-mode color in a state keeps, in the other mode, what that state shows there: its own value, else the resting color a setting gives the variant or the part, else the base theme's.
backgroundandbackground-colorcount as one property for one-mode settings: a variant's earlier color is kept as the other half and replaced, and a later both-mode color replaces a one-mode one of the other name.- A one-mode color in a state is accepted where the base theme gives the part that color.
- In a
light-onlyordark-onlytheme, a token that is no color (a shadow) is written as one value, never as a light and dark pair. - When
--modeis refused in a one-mode theme, the offered command keeps--whenand--state, and offersmode bothfirst for the mode the theme does not show. - The spacing dial reads kept sizes in pt, pc, in, cm, mm, Q and em, in any letter case, and keeps a variant's own exact size in order on that variant.
astryx experimental theme editor how: "the card fill" is the card's own background, never a part inside it; "the text after the checkbox" is its label; "the table's header cells" are the table's header cells; an unknown word before a part's piece ("the card zorp title") is said and nothing is written; a second state a part does not have ("the selected and hovered menu items") is said, never dropped; "the inputs in dialogs" are the inputs, never a command palette's; "the separators of menus" are the menu's own divider; "the card headings" are the card's title, kept to the card.astryx experimental theme editor:howkeeps a state where another of the part's own states was changed only where both hold: a checked, disabled checkbox keeps Core's fill, and an unchecked one is left alone.- A long answer is cut only between whole asks; the rest follows as the next runnable sequences.
- "remove the underline from tabs" makes the tab's indicator transparent where it paints.
- An input's focus ring is its box-shadow ring for a color, a width or a removal; in one mode only that mode changes, and status fields, which draw no ring while focused, keep none.
- A resting shadow on ringed parts keeps each render's own focus look, for every variant (selectors included) and for a write scoped to one status.
- A piece of a part Core has no part for ("the popover arrow", "the empty state icon", "sheet titles") is named and nothing is written for the whole part; a sheet is the bottom sheet, and an alert's title is the banner's own text.
- A toast's text color refused in one mode keeps that mode on the lines it offers.
- The corners help lists the step between round and pill among its rungs.
astryx experimental theme editor: several states saved joined by+with spaces around it ("selected + hover") are read as those states, as--statereads them typed, with a note. Before, every command refused the theme. A part's own state saved by hand in a spelling the editor reads (is-pressedon button) no longer leavescompilerefusing aftershow: the build reads the state, and the settings stay as saved until a change writes the part's spelling.astryx experimental theme editor: a--whenor--statetypo, or another case, on a group (--on inputs --when status:eror,--on checks --state chekced) gets the corrected command, read against what the group's members have between them, as the same typo on one part does. A setting's name typed where the theme goes gets a command on the theme here (show accentoffersshow t,set corners pilloffersset t corners pill,undo cornersthat no theme holds offersshow t), never a theme of the setting's name;undo t accent corners spacingreads the bare words as a list; and an unknown subcommand followed by an option (experimental theme preview path --theme t) is named as the unknown subcommand, with the near ones.astryx experimental theme editor:- States Core paints from an ARIA attribute are states
setnames:current(a pagination's current page),pressedandexpanded(an open menu button), built as that attribute. - Several states at once (
--state checked+disabled) are taken where Core paints them together, andhownames them that way. - A group styled alike (checks, inputs) spreads a setting only to members Core draws alike: a checkbox's corners stay off the round radios.
- The part data reads what a checkbox list and a menu holds (its rows, a row's icon), so scoped tokens on them are taken.
- A fill drawn by an element inside a part (a slider's filled range) is reached through the token it is painted with.
- States Core paints from an ARIA attribute are states
astryx experimental theme editor show --pngpictures a control's hover and press with Core's own wash, which Core puts behind a(hover: hover)query, whatever the browser taking the picture reports about its pointer. The open states picture shows the states first, and show's result says so; a popover that holds a form is no longer cut at its cell's edge.astryx experimental theme editor:- a
--when status:<x>setting now wins over the part's plain one-mode color whichever was set first: the variant blocks a plain color is written into come before every other condition, so an accepted status border always shows; howvalue questions read what the part draws: "what is the focus ring of inputs in dark mode" gives the ring it shows when focused (no longer the mode dial), "what color is the toast text" gives the color on the toast's own inverted surface, and "what is the shadow of cards" gives none at rest instead of the selected card's ring;- "make all borders red in dark mode" gives every step: a line a part does not draw yet gets its color see-through in the other mode, so the whole answer runs.
- a
astryx experimental theme: a font macOS or Windows ships (such as Avenir Next, Optima, Futura, Candara, Corbel, Bahnschrift or Segoe UI Variable) gets no install line, and a Fontsource package the editor cannot vouch for gets its own install line in compile's font help, so one that does not exist never stops the others installing. Typographyfallbackswith nofamilyin that role are refused, as Core builds nothing from them. A weight the theme uses that the base theme's font stylesheet does not load is named, with the weight it shows as, byshowandcompile.astryx experimental theme editor:howcolors a table's row lines ("table row dividers red", "table borders red") through the color its cells draw them with, set on the row; never the Divider part, a row fill or a border over the cells.- "outline buttons" is the buttons dial's outline; one variant outlined ("the danger buttons outline only") clears its fill and takes its own color as its border and text.
- A keep that needs two states at once ("the switch red when on except when disabled") says so.
- An input's focus ring asked per mode is one ring for both halves of a mode pair, and a layer per mode for a width in one mode, so the other mode is unchanged; a status named with the inputs ("error inputs") is that status's ring; "50% more transparent" is the ring color's alpha; a question about the ring writes nothing.
- A hover or press shadow on inputs keeps the focus ring while the field is focused.
astryx experimental theme editor: a selected table row's fill is the token Core paints it with.- The part data reads the paint Core writes inline when it sets a state at run time, so a table row in
selectedreads--color-accent-muted. how "selected table row light blue"answers--color-accent-muted <color> --on table-row --state selected, and a background on a selected table row, which Core's inline wash would hide, is refused with that command.
- The part data reads the paint Core writes inline when it sets a state at run time, so a table row in
astryx experimental theme editor how: tighter table rows lead with the spacing step on the rows, which reaches every row, and offer the body cells' block padding one spacing step down as the line that shows more; never the header cells alone.astryx experimental theme editor showdraws a table with a row selected and a column sorted on the sheet's open states section and its pictures, as the browser shows them: Core marks a selected row and a sorted column as it mounts, so a theme's selected-row and sort styles are now in the pictures.astryx experimental theme editor: the text result names a setting with the API's own wording, so an entry saved with no value is removed as "(no value)", never "undefined".astryx experimental theme editor how: an answer that writes a panel's look for every one (a card's) says once that the cards an app places in a carousel, a grid or a stack take it too, and names the place to ask for to keep them apart.astryx experimental theme editor:howreads "<part> title" (and header) after any part the census knows, of one word or more ("the empty state title"), as that part's own title part, never as every heading; "bigger" on a part that is only text is its text size, so "the empty state title red and bigger" colors and sizes the title text.astryx experimental theme editor:how: a dialog's or drawer's title is colored, made bold or bigger through the text tokens on its title block, never on every heading; a title Core has no part for (a card's) is said so. A weight, size or color set on a part whose text is all in parts inside it that set their own is refused with those tokens.how: an alpha said of a shadow ("card shadows with 30% alpha", "50% transparent") sets its colors' alpha in every layer the part shows; a part's shadow in a state is read from that state at its default status (an input's own hover ring, never the error ring), never from a hidden layer; a ring with no blur softens through its alpha.how: "on-accent text" is the on-accent color; "heavy borders" are thicker borders; "pill buttons less round" steps the corners; a fully round part steps from half its height; "checkbox" is the box itself, not the checks group.- The part data records a file input (a required prop that may be null is sampled as null), so a resting shadow on it keeps its hover ring.
astryx experimental theme editor's sheet, preview and pictures draw a toast's text on the side the app's own measurement picks for the fill the toast draws, by the rule the contrast checks use: light text on a dark fill, dark text on a light one, in each mode and for each type a fill is set for (an error toast's own fill read apart), so the pictures match the app and the checks.astryx experimental theme editor:- A toast's text takes its own
coloron the toast: it goes into the two colors Core's media surface gives the toast's text, on the toast alone, so the lightbox and the scrim keep theirs. A text color token on the toast is refused with that line. - Text on a one-layer linear or radial gradient is measured on the color under the text (the gradient's middle or center), so a glossy highlight at an edge is not taken for the ground.
show'smissedlist names shape and ring too: corners the theme left at the base's size beside one it changed (a popover at the container size beside square elements), with one line that sets the size it left, and a focus ring still drawn outside each part beside square corners or a theme border, with a line that draws it inside. A line is offered only where it changes the built theme.- The inverted-surface line in
missedgives the inverted surface to the part alone, with its text readable on it, and a variant with a fill of its own (an error toast) keeps readable text.
- A toast's text takes its own
astryx experimental theme editor: a setting on toggle-button's own pressed state (--state isPressed) is built on the attribute value ToggleButton writes,[data-is-pressed="true"], so it now applies; before, it was built on[data-is-pressed="isPressed"], which never matches. A part's state that names a boolean prop of its component is built as that prop's "true" value; any other state is built as its own name, as before.astryx experimental theme editor: the check of a theme's own values judges every block the build writes from. Each adaptation rule's tokens, local tokens and parts are judged, named as the file writes them (adaptations.rules[0].value…); avar()reads the custom properties the theme sets intokensandlocalTokens; a part's property given as text gets the checksetgives it, a property that reads a design token of a kind it does not take (background-color: var(--radius-element)) is refused insetand in the file alike, and a misspelled property is refused with the one meant; and a theme the source defines between the editor's settings and the exported theme is judged too, by its name and line. In typography, a weight with no type scale (which builds nothing) is named with the scale it needs, a weight refusal names the weight field, and a scale field that is no number is named as written (a symbol,NaN,true), never a crash.astryx experimental theme editor: the check of a theme's own token values judges what a build made now writes, through one path forshow,set,undoandcompile. A value from an import, an expression, a spread or a computed key is judged by its built value; only the value a later key keeps counts; a pair is judged as thelight-dark()it builds. The source is read only to name the file and line that hold each value (an imported file is named, not the theme file) and for what a build erases: a secondtokenskey, and a pair with other than two values. Typography is judged by the values the build was given: a scale base with a unit (which buildsNaNrem) is refused with the number of pixels it means, a scale with a ratio and no base is named, a family written in quotes or holding; { } < >is refused with the working form, andfallbacksis checked as part of the family list it builds. A family set through typography no longer gets the phone note.astryx experimental theme editor: the check of a theme's own token values judges every token its source gives, a design token or the theme's own custom property, and a part's CSS properties:null, a boolean, an object or a number a property does not take bare is refused as no text, with its file and line, incompile,setandshowalike. A BigInt or a symbol is named as it is (never a crash), a page token leftundefinedis not set (in a part's rule, where the build writes the textundefined, it is named), and avar()reads the custom properties the theme itself sets.astryx experimental theme editor: the check of a theme's own token values judges the input its source givesdefineTheme(), evaluated as a build evaluates the module, so a value the build would drop or Core would refuse is named before anything is written.nulland booleans are refused as no text; a value under a computed key is judged before the build drops it; a typography weight given as a number names its field and the quoted form; and the tokens a part's blocks incomponents,onDark,onLightand adaptation rules set are judged like page-wide tokens, each named by its scope and line.astryx experimental theme editor: a token family follows the token it is made from. A surface the theme sets (--color-background-surface) now carries the fills made from it, cards, popovers and menus, the muted fill (table stripes), code blocks and skeletons, at the base theme's lightness step from it; an opaque--color-bordercarries--color-border-emphasized, so inputs and selectors frame like cards; and the neutral color now reaches the page (--color-background-body, the app shell's header and side nav) at the official theme's step, as it reaches the cards. A token the theme pins, by a setting or its own source, always keeps its value.astryx experimental theme editor newoffers a free name for a token's name typed where the theme's name goes, with or without its dashes (new Color-Accent,new --radius-element), as it already does for a dial's name: the editor reads a token by either spelling, so neither is a theme to make. A name of its own (new Brand) still reads as that name.astryx experimental theme editor setsays when a token set on a part is read there only under a condition the part is not drawn in by default (a link reads--color-text-primaryonly ascolor primary): it changes nothing in the default look, and the note names the token that look reads (--color-text-accent) and the condition that reads this one, each with its line.astryx experimental theme editor: a token value your<theme>.theme.tsgives is checked entry by entry as written, andshowandcompilerefuse with one message. A number ('--radius-page': 12) is named as not text, asshowalready said; a--font-family-*token is checked likesetchecks it (a family list wholly in quotes, as Core returns one, is taken); each half of a[light, dark]pair is checked; a computed key that is text (['--radius-page']) is read like a literal one, and one the editor cannot read is named as not checked. The refusal names the line that sets the token, never a comment that mentions it.astryx experimental theme: tokens of the theme's own that read each other (--a1: var(--a2),--a2: var(--a1)) are refused at their line, as a token that reads itself is. A token inonDarkoronLightis judged against what that surface sets, so a surface token that reads a token the page sets from it is accepted.astryx experimental theme editor: the sheet and its pictures show a typeahead's list open. The render loads React DOM's client with a document in place before the page (a part that loads it with the page, such as a toast, loaded it with none, so typing never reached a field's change handler), types as a person types, and opens a typeahead's open look without waiting for its search delay.astryx experimental theme: more typed and pasted forms are read as meant. A part named beside a property's value (set my padding 'card 8px','red on buttons','button:hover: red') gets the line on that part and state; the editor's own result line pasted with its head ([ok] my: corners = pill (whole theme)) is read;new's settings written as pairs apart at commas ('like: neutral, corners: pill') keep every pair; a base with a stray quote or comma (--like "neutral'") gets its line without a did-you-mean for the same word; and a font family whose last word names a weight ('Bodoni Moda Bold') is kept as typed with the family and weight lines in a note.astryx experimental theme editor: every repair reads a typo of a typed value, setting, part, state or theme or token name the same way: within one letter for a word of five letters or fewer and two for a longer one, two letters swapped counting as one. Soborder-style lineis no longer offerednone, anddisplay flxeis offeredflex, neverflow;nnoneandnormallare still corrected. The words of ahowquestion keep their own spelling reading.astryx experimental theme editor set: a part drawn under an invisible native input (a checkbox's or radio's box, a switch), which the part data now records, refuses a hover, press or focus state, which would never apply there, naming the part that holds the input; for a token, the same token with no state, which Core reads when it paints that state from the input, is offered.astryx experimental theme editor undo: the headline names what the undo took back ([ok] v: undid neutral = [#78716](https://github.com/meta/astryx/pull/78716)c (whole theme), orundid 2 changes: …), in the text and in the JSON (undid), so a tail of the output keeps it. When the last change command was refused, the undo says that command changed nothing, so it took back the change before it (refusedBefore).astryx experimental theme editor undo: with no--mode, a setting saved for one mode only is removed, and the result names its mode; one saved for each mode gets an undo line per mode instead of a refusal that contradicts itself.astryx experimental theme …: undo and pasted forms are read as typed.undo t 'cornres pill'names the setting the typo means, and a setting the theme does not hold getsshow, never a step back that would remove another change. Bare words for undo that are a held setting's value (corners pill accent) are read as that value. A setting's name where the theme goes, in other letters or as a token (undo Corners,undo --color-accent,show Corners), offers the themes to look at, never a new theme of that name. Several lines pasted as one argument give one line each. An empty pasted object with a separator ({,}) points to the dials. A pasted label that is a part typo ((crad)) is read as that part and a state ((hover)) as the state; a label that is no mode is never dropped for a line that changes both modes. A damaged saved entry beside a clean one of the same scope gets only its undo, never a set over the clean entry.astryx experimental theme editor set … font: a family the editor does not know is kept as typed (Corben, Gabriela, Candal are real families, no typos of Corbel, Gabriola, Candara), with a note giving the line that sets the font a system ships spelled near it. A typo of a font preset is refused with the preset, a name listed both as a preset and a system font counted once (Gerogiareads as georgia), and the presets are read before the system fonts near it (Corieris courier,Monlomono). Arial Narrow and Andale Mono are noted as fonts only macOS ships.astryx experimental theme editorandcompilename more of what a theme's own source misspells or misplaces, each with its file and line:- a field
defineTheme()or anonDark/onLightblock does not take (component,tokenz), with the field meant, read from the installed Core's own types; - a
tokenskey one typo from a design token (--color-acent), pointing a property of the theme's own tolocalTokens; - a part's pseudo-class one typo from one browsers know (
:hovr), a part variable one typo from one the part reads that nothing in the theme reads (--button-focus-ofset), and a part variable's value of the wrong kind for its default; - an unknown component (
cardd, or a part named by its class), and a component entry that holds no block of properties; - a typography role or field Core does not read, a heading level outside 1–6, a scale with no ratio, and the
fallbacksfield when it is what a family refuses; - a part's
fontFamilyread assetreads a family list, and avar()of the theme's own property read as the text it holds; - a
var()of the wrong kind inside a token's function (color-mix(in srgb, var(--radius-element) 50%, red)), in the source and inset; - a value in a theme the export extends from another file, named in that file;
- a path Core itself refuses (
adaptations.rules[0].when.pointr), at its line.theme buildgives the import hint only when an import did not resolve.
- a field
astryx experimental theme editor: lines the editor offers run as offered.undowith a value one mode holds removes that mode's entry, and an undo of one of two settings says what each mode shows now; a theme typed second gets no line for a theme that does not exist; a dial or property name a letter off (cornres,paddng) gets its set line, with the value and scope kept; saved entries with their field names in other letters (Thing,Value) are read; a design token with a fallback (var(--color-error, red)) is offered as typed; and a setting typed where the theme goes (undo accent) gets that theme's undo, never a new theme of the setting's name.astryx experimental theme editor howvalue questions read the status or state they name: "what is the border of error inputs in dark mode" gives the error border, "…of focused inputs" the focused one and "…of selected cards" the selected one, instead of the plain rule's value; "how thick is the input focus ring" gives the ring's width with how it is drawn.astryx experimental theme editor: a value your<theme>.theme.tsleavesundefinedis taken as not set wherever it is (a token on the page, inonDark/onLightor in an adaptation rule, a part, a style key, a property), now that the theme build writes nothing for it. A part givennull(or another value that is no block of style keys) is refused at its line, at the root and inonDark/onLight, instead of failing the build.astryx experimental theme: a token inonDarkoronLightthat loops through a token Core sets on that surface itself (--color-on-dark: var(--color-text-primary), while Core's dark surface sets--color-text-primary: var(--color-on-dark)) is refused at its line.astryx experimental theme editor how: a value question ("how thick are dividers", "how round are the cards now?") reads a token set on the part itself (or its group) before the theme's own value, so it answers what the part shows.astryx experimental theme editor: avar()is read as CSS reads it. Glued after a letter or a digit (padding '2var(--spacing-4)'), CSS reads no reference there, so the value is refused instead of written as a value the browser drops. Text glued after it ('var(--spacing-4)px','8pxvar(--spacing-4)') is refused for the value's grammar, not as the token being the wrong kind, and the refusal no longer offers the same input again.astryx experimental theme editor: avar()with spaces inside its brackets (background-color 'var( --color-accent )') is read as CSS reads it, the same asvar(--color-accent). Before, every color refused it as no color.astryx experimental theme editor howreads three more kinds of words as what they say: a weight word before the text it describes, however many words about the text sit between ("thin elegant headings" is the weight, never a border around every heading); "reader" and "readers", which are no longer corrected to "header", so a book-reader ask changes the theme and not the app shell header; and a CSS custom property pasted from a stylesheet, whose last words name what it sets (--brand-bgis a background,--brand-textthe text color), never the prefix a codebase repeats on every one of them.astryx experimental theme editor: one reading for each kind of word. A mode is read one way everywhere (the--modeflag, a mode label in a value, a saved entry's mode and the settings file's mode): light or dark in its written forms, or day, daytime, night or nighttime; black, white, dim and bright are no longer read as modes. A base is read one way bynew, set and the settings file. Anewon a base that is not installed leads with the install, then the samenewon that base, as set does.howreads state words from one table. A font file in a family list is found with the one family-list reader.astryx experimental theme editor how: "table headers" (plural) are the table's header cells, never its rows; "menus" said plainly is every menu (the menus group); a tab's underline asked for a color or a thickness ("a 2px black underline when selected") is its indicator's fill and height, never a text decoration it has no text for.astryx experimental export: the file drops the web font faces that no character in the page, its stylesheet or its script reaches, so a page with a web font is smaller.- A font package ships one face per script (Latin, Latin Extended, Cyrillic, Greek, Vietnamese) for each weight. A browser loads only the faces its text needs, but the file used to carry all of them. A page that imports a font package and never uses its family now carries none of its faces. An English page that uses two weights of a font package is 10% smaller.
- A face stays when its font family is named outside the faces (in a rule, a token, the markup or the script) and its
unicode-rangecovers a character the page can draw: one in the markup, the script or the stylesheet (acontentstring). A character written as an escape (\u039ain the script,\41fin a stylesheet) counts too, so text that a later view, a menu or a hover shows keeps its face. A family name counts as CSS reads it (Gill\ Sansis'Gill Sans'), also when the script holds it as escapes. A list or counter style with other letters (lower-greek, a@counter-style), or atext-transformthat changes the characters (full-width), keeps every face of a named family, whether the stylesheet (directly or in a custom property), the markup or the script sets it. Each character's other cases count too, foruppercase. - The cut runs before the font files are read, so a dropped face is not counted in
imagesand gives no missing-file or network warning. - Some text is not in the file, so no face is kept for it: text a reader types, text the script builds from character codes, and text the browser writes in the reader's or the page's locale (a date field's placeholder, Intl-formatted dates and numbers). Such text in a script that no kept face covers is drawn with the next font in the family list.
- Only the exported file is cut. The theme editor's previews keep every face, so text typed into them draws in its font.
astryx experimental export: a page whose root theme draws in one mode stays readable in a viewer of the other scheme. Before, the file declared both color schemes, so a dark viewer showed its dark canvas behind a light-only theme's dark text. The export reads the theme module'scolorModesexport when it has one, without running the module. Otherwise it reads the page or text colors the theme's compiled stylesheet, which the page imports (directly or through an@importin its own CSS), sets on its root: a light page with dark text draws in light only, and a dark page with light text in dark only. Any color the theme editor reads counts (hex, a named color,rgb(),hsl(),oklch()and the other CSS color forms). A theme that sets neither (a fonts-only or accent-only theme), sets alight-dark()color (a value for each mode), sets one the export cannot fix (such as avar()), or sets any page or text color under a light or dark condition keeps both modes, as before. A one-mode page declares only that scheme and paints the theme's own page color on the document. For a theme passed to[Theme](/components/Theme)unbuilt, whose CSS is injected only at run time, only what the page's own stylesheets set on that theme's root counts. A page whose theme draws in both modes, or that has no theme, is written as before.astryx experimental exporttreats a package thatnode_moduleslinks to a folder inside the project (npm link, afile:dependency, a workspace package) as a package: the file no longer carries its modules as page files, so--reversegives the page back exactly instead of refusing it. The page looks and runs the same.astryx experimental exportreads the page's packages faster. Node looks up the package scope of every module it loads and parses a package's exports map again for each one, so a page that loads hundreds of Core's modules parsed Core's exports map hundreds of times. The export now resolves an import between two files of one installed package by its path, and reads each folder's package.json at most once. Every other import, and every import of the page's own files, resolves as before. Exported files do not change.astryx experimental exportcompiles the StyleX in a package that ships StyleX source, as an app's build does. A component from such a package, installed or linked in from a workspace, that usesstylex.keyframes,stylex.defineVars,stylex.createThemeorstylex.firstThatWorksused to fail with "Unexpected 'stylex.keyframes' call at runtime". Its styles now compile with the page's own class-name prefix, so they never share a class with Core's, and its animations run in the exported file. A file of the package that the page loads lazily carries its styles too. A package that ships compiled StyleX stays as it ships.astryx experimental exportloads a page whose modules import a.tsxfile by its.jsname (./parts/Kpi.jsforKpi.tsx), which used to fail withERR_FILE_NOT_FOUND.--reversegives back a page whose modules import any TypeScript file by its JavaScript name (.js,.jsx,.mjs,.cjs), which it used to refuse as damaged. A file in which such an import is relative says render format 3, so an earlier CLI names the CLI that reads it instead of calling it damaged; one through a path alias (@/lib/rows.js) keeps format 1.astryx experimental exportrefuses a page that uses no Astryx components or styles, withERR_RENDER_NOT_ASTRYX, exit 1 and nothing written: "page.tsx uses no Astryx components or styles;astryx experimental exportonly writes pages built with Astryx. Don't add Astryx to this app to export it: share the page with the app's own build instead (for a Vite app, a single-file build); nothing was written." The page's own script decides: a page counts as Astryx when any module its script holds belongs to an Astryx package (imported directly, through a local component or a re-export, or lazily), or when it imports an Astryx stylesheet. The theme editor's previews are unchanged.astryx experimental export --reverse: an image a carried module names with percent-escapes (/pics/a%20b.png,./c%20d.png) is expected back as the file those escapes name ("a b.png"), the file the export read and carried. Before,--reverserestored the file but listed the escaped name as missing and reported the restore as not exact. The export also carries such an image when the page draws it only later (after a click), so it shows from the file. An image the page imports, or loads withimport()orrequire(), by such a name is carried and followed as written, as before.- Outside a project,
astryx experimental exportloads a subpath that a package from its package set exports only under theimportcondition, as a theme package's./themes/<name>often is. Such a page used to fail as if the package were not installed. A subpath the package does not export keeps the answer it had. astryx experimental export: the warning for something the page loads from outside the file says so in the words the Checks section uses, which fit a file beside the page as well as a remote address. The share-a-page guide points to the Checks section the export prints instead of a separate reverse run.astryx experimental exportwarns when text inside an SVG drawing that scales to its box would show under 10 px on a 375 px phone, because the text shrinks with the drawing. The share-a-page guide says how to keep chart labels readable.astryx experimental theme editor set <theme> surfaces flat: in a mode where the theme gives a panel a fill of its own (white cards in light mode), the panel shows that fill, so its pieces (a gray badge's pill, the muted fill) stay as they are there instead of being drawn in the card's color and vanishing on it.astryx experimental theme editor set <theme> surfaces flatkeeps its tinted panels, and the gray pieces inside a panel drawn in the tint's color (a neutral badge, a progress or switch track) are drawn in the panel's own surface there instead, so they stay visible; colored fills keep their hue, and the emphasized border is stepped inside the panel where it would stand out less from the tint than from the panel's surface.astryx experimental theme editor: undersurfaces flat, menus, popovers, select lists, hover cards, dialogs and drawers, which float over the page, keep their own fill and get a hairline--color-borderedge instead of the page's tint with no edge (cards and the banner keep flat's tinted look). A floating panel a theme leaves within 1.1:1 of the page with no border or shadow is now a problem, with a line that adds a 1px border.- An
astryx experimental iconsubcommand typed alone, such asastryx experimental icon add, now finds icons for its name when an icon (or, with no icon set installed, an icon definition) matches the whole name, asastryx experimental icon <words>does, and names the subcommand's usage on one more line. Otherwise the subcommand keeps its error and names the search. Outside a project, a subcommand that needs one still refuses. A subcommand given an argument or an option runs as before. - Icon definitions: five descriptions now name only the job the icon does.
scaleno longer describes its drawing;wrenchno longer reads as a secondsettings(it means tools for a technical fix or setup);clouddrops weather;globedrops language, which has its own definition; andmailis about email rather than a message inbox. - Icon definitions: a definition can name its
group, the family of related meanings it belongs to (for examplenotification,notificationActive, andnotificationOff), and Astryx's definitions now name theirs. A set's own definition may join an Astryx group or name its own.experimental icon --definitionsshows each definition's group; each finder match gainsrelatives, the other definitions in its group with what each means (the text answer names a few under the first match only); with no set installed, each matching definition gainsgroupandrelatives; and a definition's docs page names its group's other members. Groups are information only: ranking does not change, and stable commands print what they printed before. - Icon definitions can declare
replaces: the name of an older definition they take the place of. The old name keeps answering, through every later replacement: an icon set'smapkey that uses it maps the new definition, a template'siconsvalue and a definition named toexperimental icon maporaddmean the new one, andastryx experimental icon <old name>finds the icon drawn for the new one.integration checkwarns with eachmapkey to rename (icon_definition_replaced), the nextexperimental icon mapwrites the new name, andastryx doctorwarns when an installed set still uses an old key.experimental icon --definitionsand the definition's docs page show what it replaces. - Icon definitions:
messageno longer listsconversationandtextCaseno longer listsuppercaseorlowercaseamong its words. Each of those words is another definition's name, so a search for it now lists only that definition. - Where icon features are on (an icon-set package is installed or
experimental.iconSetis set), the agent block thatastryx initandastryx upgradewrite adds one line under the runner line: "Need an icon? Runastryx experimental icon <what it means>and paste the import it prints, instead of copying one from a template or other code." Where they are off, the block does not change. astryx experimental icon <words>in a project with no icon set installed says so, lists the icon definitions that match (built-in names first, which Core draws with no set), and says how to get a set, in text and in--json(reason,definitions,next).--listgives the same next step instead of pointing back at the search, andexperimental icon use <set>or--set <set>with no set installed says how to get one. Afterexperimental icon use <set> --variant <look>, the search prints each match's import in that look where the icon has it, and names both looks (look) where it does not.astryx experimental iconranks faster: each search works out every icon set's searchable words once and each query's forms once per pass, so its passes read every icon without rebuilding its words. Answers are unchanged.- Experimental
exportIconIndex()andrankIconIndex()in@astryxdesign/cli/api, the icon counterpart ofexportSearchIndex()andrankSearchIndex().exportIconIndex({cwd, package?})returns the icon setsicon()searches in a folder as plain JSON, andrankIconIndex(query, indexes, {set?, limit?})ranks stored indexes withicon()'s own ranking, so a catalog that must not load package code can store each package's index once and answer icon searches exactly asastryx experimental icondoes.icon()ranks through the same function, so its answers are unchanged. An index is ranked only by the CLI version that made it. astryx docs cli/experimental/icon-setsexplains icon meaning groups andreplacesin its overview: a match lists the other meanings of its group asrelativeswithout changing which icon comes first, and a replaced meaning's old name keeps answering whileintegration checknames themapkey to rename. The search example now says the set's icon for a meaning answers where the set maps one.astryx docs cli/experimental/icon-setsopens with the icon model in one place: Astryx owns generic meanings (a description and a few words each), a library maps its icons onto them inside its own package or the integration that already ships for it, with no separate add-on, a missing meaning is added in that package withexperimental icon new-definition, andastryx experimental icon <words>puts the set's icon for the matching meaning first while related icons stay findable by their own words.- With no icon set installed,
astryx experimental iconandastryx experimental icon --listnow name the discover search that lists icon packs when discover lists one the project could add: Find an icon pack withastryx discover "icon set", install it, then runastryx experimental icon use <set>. To make your own set, readastryx docs cli/experimental/icon-sets. The finder reads the catalog copies discover saved and calls no discover source, so before the first discover run, and where no catalog lists an icon pack, the step reads as before. The JSONnextfield carries the same sentence; its shape does not change. - Installing an icon-set package turns icon features on, with or without
experimental.iconSetin astryx.config. A project that installs no icon-set package and sets noexperimental.iconSetsees no change in any command, apart from the search change for experimental docs below. In a project that installs one, these stable commands now read the installed sets, so their output changes there:astryx discover: lists each package's sets, and--type icon-setworks.astryx doctor: runs theicon-setscheck and reports an invalid installed set. It runs theicon-placeholderscheck when a main set is decided: the oneexperimental.iconSetnames, or the only installed set.doctor integration validate <package>checks an installed package's sets.astryx docs icons: one section, added in the name of the package that ships your set, says how to find its icons (astryx experimental icon <words>).astryx searchdoes not return it, and search output does not change.
Copied templates still follow a set only onceexperimental.iconSetnames it.For integration authors:astryx searchnow leaves out the sections that a doc markedstability: 'experimental'adds to another topic withextends, as it already leaves out an experimental topic.astryx docsstill shows those sections.Compatibility: in a project that installs an icon-set package,astryx discover --type icon-set --jsonnow lists that package instead of failing as an unknown type, so its answer no longer carries the error fieldsdiscover-type-icon-set.json.code,discover-type-icon-set.json.error,discover-type-icon-set.json.suggestions,discover-type-icon-set.json.suggestions[].nameanddiscover-type-icon-set.json.suggestions[].reason. A script built on 0.7.16 keeps working: a type discover does not know still fails with the same fields, and a project with no icon-set package gets the same error as before. astryx experimental iconand the icons block ofastryx searchleave out the words that only join others (with,and) when they look for icons that carry a query's words, socard with an icon of a starno longer lists an icon only because its name holdswith. A query that no whole word answers as typed is now read without them, souser with plusfindsuser-plusdirectly.astryx experimental iconnames each match's meaning import when its icon set maps the icon for a definition:meaningImportimports the icon under the meaning name, such asimport {TrashIcon as DeleteIcon} from '…', so app code keeps the nameDeleteIconwhen another icon set drawsdelete.astryx experimental iconanswers a query of several words that no icon matches as a whole, such as a glyph named in a phrase with the control around it. Icons that carry some of its words come back as word matches (score 20), the project's set first and, within a set, the icon carrying the rarest words first; a word that names a definition the set maps an icon for counts twice for that icon, and a word no icon carries counts for nothing. Word matches appear only in the search's own answer, and only where nothing answered before. A word written as an export name (SearchIcon,ChevronDownIcon) is also read as its words; the reading with the better-scoring match answers, so an answered query changes only when the split reading finds a better match.- The icon-sets guide shows how to make a set inside your own app, with no other package to make, install, or publish. When the package's own package.json sets
"private": true, theexperimental icon new-setreceipt leaves out the publishing steps (peers, thetypecheckscript, the strict check's TypeScript, the placeholder description) and its notes end with theexperimental icon use <set>step that turns the set on. Every other package gets the notes as before. - Icon sets: the generated icons module marks each adapter call and each theme-map element
/* @__PURE__ */, so a bundler drops the icons an app does not use. Before, importing one icon from a set also bundled its whole theme map (and, for a set built with an adapter, every adapted icon). Modules written without the marks, or with/*#__PURE__*/, read the same; the nextexperimental icon add,map, or refresh adds the marks, keeps any mark a statement written by hand already carries, and changes nothing else. Set authors: author and check a set with this release or later. An earlier CLI misreads a module written with the marks: itsexperimental icon addandmapdrop the adapter import, itsnew-set --fromrefuses, and itsintegration checkanddoctor integration validate <set package>reporticon_generated_types_mismatch. In an app on an earlier CLI, template copies, icon search and the defaultdoctorrun read a marked set as before; validating the set package itself fails until the app moves to this release. - Icon definitions: two new definitions,
fullScreen(show something full screen) andexitFullScreen(leave full screen), so an icon set can map its full-screen icons apart from the icons it maps toexpandandcollapse.expandandcollapseare unchanged for now, so every set keeps answering full-screen asks with the icons it maps today; sets that map neither new definition keep working, andexperimental icon --definitionsandintegration checklist them as optional. astryx experimental iconbreaks a tie between equally scored icons in favor of one whose name the query names in full, so a request for a plus icon to add a row getsplusbeforefolder-plus. Remaining ties keep id order.astryx experimental theme editor set <theme> accent <color>: when the accent is a color far from the hue of the base theme's info, and the theme leaves info unset (a pink theme over a bright blue info), the result says info's banners and badges keep the base's color and offers an info between the two hues, so it sits with the palette and stays apart from the accent.astryxdiscovery lists the lab's new media players:[VideoPlayer](/components/VideoPlayer),[AudioPlayer](/components/AudioPlayer), and the[MediaPlayer](/components/MediaPlayer)root and parts for custom layouts.astryx experimental theme editor set <theme> neutral <color>: a neutral color whose shades are the base theme's own grays (black, white, or a pure gray) now says the page, surfaces, text and borders keep their colors, and how to get dark surfaces, instead of a bare[ok]: a gray sets the tint of the grays, not how light or dark the surfaces are.astryx experimental theme editor: text on a role fill (accent, success, warning, danger, info) where neither the theme's white nor its near-black reads at 4.5:1 now uses the end of the gray ramp on the better side (black, or white) when that reads better, so the editor's own pick no longer makes a contrast problem that a darker gray would have solved; an exact fill that then reads keeps its color in dark mode too.astryx experimental theme editor set <theme> neutral <color>says the page background follows the gray too (or keeps a page color the theme sets), as it does, and so does the neutral dial's help; a moved accent text color's note names only the grounds it fails on, with the ratio on each.astryx experimental render: a page whose script holds a long run of letters and digits, such as a large string, renders in its usual time again. The pass that finds the script's reads of images from the embedded source started a match at every character of such a run, so a page with a 1 MB string took minutes.astryx experimental rendercarries the page's own modules and JSON data whose names only look like configuration:config.ts,lib/arc.ts,data/chart-config.json,data/config.json. They were left out as tool configuration, so the page came back from--reversewithexact: falseand without them. These names stay refused:tsconfig.jsonandtsconfig.*.json,jsconfig.json, any*.config.jsonor*.config.{js,ts,…}module, manifests and lockfiles, and dotfiles such as.eslintrc.js. A file that carries one says render format 2, so a CLI that reads render formats names the CLI that reads it; 0.7.16 and earlier refuse it as damaged.astryx experimental renderdraws a recharts chart sized by itsResponsiveContainerat a set of widths, from a narrow table cell to a wide screen, and the file's CSS shows the drawing nearest the width the reader's browser gives the chart, with no script. Before, such a chart was drawn once at a guessed size and stretched to the page's width: its text was about one and a half times its size on a desktop and half its size on a phone, and a chart that filled a box of fixed height ran out of the box. The widths run from 60 to 1920 pixels, each the square root of two times the one before, so the drawing shown scales by at most the fourth root of two either way. The chart now keeps the height the page gives it (a number, the width overaspect, or its share of the height that the box it fills states in its own style) and fits that box whole, so its text stays within a fifth of its own size. A box whose height comes from a stylesheet gives no height to read: the chart is drawn 300 pixels high and fits inside the box, scaled down in a shorter box and with empty space above and below in a taller one. Its legend sits inside its picture, where recharts places it, and keeps the rest of its style. Each such chart carries eleven drawings, whose coordinates keep two decimal places, so it takes several times the room in the file that one drawing takes. A chart of fixed size is drawn as before.astryx experimental exportchecks the file it wrote and says so: whether the file's markup and stylesheets load anything from outside the file (the page's own script is not read), and whether--reversegives back every carried file exactly, naming any that differ (data.checksin JSON). When the file stands alone, it names it as the one file to share, with its size.astryx experimental export: a large exported page that repeats an element names each repeated list of the StyleX classes Astryx's packages write (thex…classes) by one short class in its first paint, when those repeated lists add up to at least 16 KB; the page's own StyleX classes keep their names, so a large table or list writes a much smaller file: a 10,000-row grid goes from 52 MB to 18 MB. The page looks the same, also where scripts are blocked; its script draws with StyleX's own classes, and--reversegives the page back exactly. The experimentalrender()takeskeepClassNames: truefor a caller that styles the file's markup with its own copy of the StyleX styles.- When a page does not compile,
astryx experimental rendernames the file and the line the error points at, also for a module the page imports. When StyleX cannot read a value a style imports, the message names the value and the import, and says what StyleX needs: the value written in the style, or a.stylex.tsor.stylex.jsfile that defines it; for a.stylexfile it cannot find, it says to check that the file or its package is there. astryx experimental exportchecks itsdropped-childrenwarning against Core's component docs. A Core component whose docs list nochildrenprop is named as the one that dropped the text, even when the text sits inside another component (<[Badge](/components/Badge)><[Text](/components/Text)>New</[Text](/components/Text)></[Badge](/components/Badge)>names Badge), and the warning points toastryx component <Name>. Text that the first paint does not show yet (a collapsed Banner, an inactive tab or route) stops warning only when every component around it is a Core component whose docs listchildren. A text inside a page's own component, or another package's, keeps today's warning. A warning for a text in another of the page's files names that file (on line 12 of components/[Card](/components/Card).tsx). The warning's code does not change.astryx experimental rendernames every package the page and its own modules import that is not installed, in one refusal, before it runs the page, with one install line for all of them. An Astryx package (a theme, say) counts as installed outside a project only when the CLI's package set holds it; otherwise it is named with the rest. Before, it named only the first, so a page that needed three packages took three failed renders. The message and the install suggestion name every package. In a TypeScript module, a static import the module uses only as a type, or not at all, does not count, as TypeScript drops it; a re-export,import()orrequire()of the same package still counts. A JavaScript module loads every import, so each one counts. A package stylesheet that is missing is still a warning, as before.astryx experimental render: a rendered file now explains itself to whoever opens it next. A note at its top names the CLI version and render format that made it, the page's path, the files it carries and the packages it rendered with, and gives the exact commands that get the source back and render it again; a short note after the embedded source repeats the way back.--reversereports the render format, the CLI version (renderedBy), the packages and an explicit--title(title), and, for files this version renders, whether someone changed the markup after the render (edited, read as a browser reads the file, so a copy whose line ends changed on the way is not edited) with each text change (edits: what it was, what it is now, and the restored file and line that hold the old text, in a module or the JSON data it imports, also where it wraps across lines). A file in a newer render format than the CLI reads is refused with the newERR_RENDER_NEWER_FORMAT, which names the CLI version that wrote it; a file that names a CLI version that is not a semantic version is refused as damaged, so no printed command carries it, and every path a printed command takes from a received file is quoted. The render format stays 1, so earlier CLIs keep reading the files this version writes, except for a file that carries an.mts,.ctsor.cjsmodule, which says format 2 so that a CLI that reads render formats names the CLI that reads it; 0.7.16 and earlier refuse it as damaged.astryx --json experimental export: thedata.filesdescription also names the images a page names by a path from the site's root, which the export reads frompublic/.astryx experimental render --reversefinds a rendered file's title, styles and body as a browser does, outside comments and outside the text of the style element, so an untouched file whose stylesheet text looks like HTML, or whose page path looks like a tag, no longer reads as edited.astryx experimental rendersays why when no answer from the page's process reaches the CLI: the answer was sent but not received, the process ended while it sent it, or the stage it ended in, after how many seconds and with how much memory free. When the page's process cannot send its answer, the error now says so.astryx experimental export: an exported page's script reads from the first paint an image the first paint shows throughsrc,srcsetorposterwhen the page's code names it as a whole string by that exact path or https address. The file holds each such image one time fewer: a page with one 450 KB local photo goes from about 2.05 MB to 1.45 MB, and an https image the page shows throughsrc,srcsetorposteris held once (the same photo by an https address: about 1.46 MB to 0.86 MB). The first paint is the same, also where scripts are blocked.- A page rendered with
astryx experimental rendercarries one copy fewer of each image a page module imports (import photo from './photo.png') when the file's embedded source carries it. The page's script reads such an image from the embedded source, so the script holds no copy of its own. An image the embedded source leaves out (under a dot-folder or innode_modules) keeps its own copy in the script, and an image the page names by a string path keeps its copy too. - New
astryx experimental import <file.html>turns a fileastryx experimental exportwrote back into its page, the same asexport --reverse, which keeps working. Help, the share and export guides, the file's own note and the render's suggestions now give the way back asexperimental import. The JSON answer is unchanged (render.reverse). An oldexperimental render --reverseline now points straight toexperimental import, and an unknown top-levelimport,back,restore,unrenderorreversesuggests it without running it. astryx experimental export: a link to a place in the page (<a href="#section">) keeps working in a viewer that shows the file in a frame given its document inline (srcdoc), as many artifact viewers do. There the address resolves against the viewer's own page, so the click navigated the frame away and the page vanished. Now the file moves to that place, as a browser tab does: it scrolls there, sets:targetfor the page's CSS and fireshashchangefor a page that routes by hash.#goes back to the top. This also holds in a viewer that cancels such a link itself on its way down and only scrolls to the place, from a listener its own script adds on the frame's window before the file's script runs, or on the frame's document from a DOMContentLoaded listener its script adds on the frame's document before the file's script runs: tabs and navigation that route on the address switch there too, also for a link inside a card that stops the click. A link the page cancels or handles itself, from any of its own listeners (also one its modules add while they load), one with a target, and a click with a modifier key keep their own way.astryx experimental rendernow writes the page as a live app in one file: popovers, menus, dialogs, tabs, forms and every other control work as in the app. The file carries the page's own script, inline after the embedded source: the page's modules and the packages they use, bundled for the browser by esbuild. It paints the rendered markup first, then the script draws the live page over it. It is still one file, and the render adds no network request and noeval, so it works in a sandboxed frame that allows scripts, under a content security policy that allows inline scripts; a frame that blocks scripts shows the markup, and--reversestill gives the page back byte for byte. A link out of the file opens in a new tab, and a form submits even in a viewer frame that blocks form submission: the file fires the form's submit event itself. A page whose script cannot be built for the browser (a module it loads needs Node, say) is refused with the newERR_RENDER_SCRIPT, which names the module. esbuild is a new dependency of the CLI, and onlyexperimental renderloads it, so no other command starts slower. The JSON addsscriptBytesandscriptModulesto a render. When the page's script throws, in its render or in an effect (a frame that blocks storage, say), the file keeps showing its first paint. An image the page names by a path in a string, insrcorsrcSet, keeps showing once the script draws the page, and an image named insrcSetis carried too. A page file the page loads later (a dynamic import) that does not compile is refused as a static import is, withERR_RENDER_COMPILEnaming the file and line.- The experimental command
astryx experimental renderis renamed toastryx experimental export. It still writes a page as one self-contained HTML file, and--reversestill turns that file back into its page; its options are the same, and its text output says "Export it again:" where it said "Render it again:". The old name is no alias:astryx experimental render …fails, exit 1, withERR_UNKNOWN_SUBCOMMAND, and suggests the run withexportin its place, keeping the options before it (also as a JSON error with--json). An unknown top-levelexport,render,share,bundle,snapshotorstandalonesuggestsastryx experimental exportand never runs it, unless the next word is a name another command reads (astryx export [Button](/components/Button)still suggestsastryx component [Button](/components/Button)) or the active base does not serve the command. The guidecli/experimental/render-pagesis nowcli/experimental/export-pages, and the command's reference iscli/commands/experimental-export. JSON fields that carry the command name now sayexperimental export: the command's entry inastryx manifest --jsonand inastryx --json experimental --help, and every suggestion'snamethat names the command. The result types stayrender.pageandrender.reverse, the error codes stayERR_RENDER_*, and therender()function keeps its name. A file written before the rename names the old command in its note;--reversereads it as before. astryx experimental renderrefuses a page that imports a name its module does not export, as a build refuses it, withERR_RENDER_COMPILE: "The page does not compile (src/page.tsx, line 3): @astryxdesign/core has no export Chart". It checks named imports in the page's own modules from those modules (not from a CommonJS one, which a bundler reads by interop), from Astryx packages and from StyleX variables modules (.stylex), and an element drawn as<Name.Member>whose export has no such member. It counts only names the page uses as values, so a type imported withouttypeis fine, and a file the page reads as text (?raw) is not checked. The script's build names the file and the module the same way. An import of a package subpath the package does not export (@astryxdesign/core/[Chart](/components/Chart)) is refused the same way: "@astryxdesign/core has no export ./Chart". Before, the render named what the missing import broke, not the import:ERR_RENDER_FAILEDwith "Element type is invalid" for a missing component,ERR_RENDER_FAILEDwith "… is not a function" for a missing function the page calls as it loads,ERR_RENDER_SCRIPTfor a name only the script uses, and a missing.stylexvalue rendered without its style and with no error.astryx experimental render: when a page imports packages that are not installed, the suggested install line now follows the page's own package, and no line is offered where running it would install in the wrong place. The page's package decides the package manager. When its lockfiles disagree, the message names them and suggests no install, where it suggestednpm install. For a page in another package than the folder you run from, the message names that package and the line to run there, since the line run here would add the packages to this folder's package. In a folder that nopackage.jsonholds, the message says to install them in the project that uses the page, and suggests no install, since an install there would make the folder a project.astryx experimental export: an exported page's script is a module script when it runs the same in strict mode, so it runs once the file is parsed: a browser paints the page before the script draws it, and on the pages measured a small page shows its first paint about 200 ms sooner on a slow phone, with about the same time until it responds. A page whose script bundles a file that is not an ES module and does not ask for strict mode (CommonJS code, or a side-effect file with noimportorexport), or code that readsdocument.currentScript, keeps a classic script.astryx experimental exportleavesautofocusout of the file's first paint. The page's script owns focus once it draws the page, as the app does, so a field the page focuses still gets focus. A viewer that shows the file in a cross-origin frame no longer logs a blocked-autofocus error.astryx experimental exportdraws some large chart pages faster: React no longer logs each render's timing while the export draws them. A page of four charts of 50,000 points each took 42 s to render and now takes 29 s; most pages take the same time as before. The file it writes is the same.astryx experimental rendernames every file the page uses that the rendered file does not carry. A file left out because its name reads as a tool's configuration now gets the warning codenot-carriedinstead ofnot-embedded. It says what carries the file: rename a*.config.json, such aschart.config.jsontochart-data.json, or move the values the page reads from a tool's own file, such aspackage.json, into a file of its own. The note at the top of the file lists every left-out file on a "Not carried" line, and then no longer says the page comes back exactly. The JSON addsnotCarried, and the text output shows it, both only when a file is left out.astryx experimental render --outaccepts an absolute path in any folder, such as a folder of files to upload as an artifact. The render still never replaces a file it did not write. A relative--outstill stays inside the current folder, and its refusal now says that an absolute path works.- render: a page's own styles compile with their own class-name prefix, so they never share a class with Core's stylesheet. Core's rules keep their layer on Core's elements (a Table's first and last cells keep their edge padding), and a page's override of a component still wins, as in the app.
astryx experimental theme editor: the overlays a page opens are drawn one part at a time, so a part's document listeners (a typeahead's or a menu's outside press) hear only presses on its own controls. Every editor command that reads the part data, and every sheet picture, no longer pays for each press on every other part. The part data is the same as before.astryx experimental export: more images named by a path from the site's root (/pics/shoe.png) show in the file and come back with--reverse.- When the project has no
public/folder, export reads such a path from the nearestpublic/above the page, inside the project. This covers a site folder below a shared package.json. Outside a project, it reads it from the nearestpublic/above the page, inside the folder you run the command from. - The file now carries each such image with the page's other files, so
--reverseputs it back in thepublic/folder export read, at the same path. - An image the page names this way but draws only later (after a click, in the next view) is carried too, and the file's script shows it from the carried data.
- Export reads such a path only from
public/. A file of that name at the project's or the page's root is no longer read, and a path that leavespublic/(/../x.png) is not read. A path to a file that is not inpublic/gets the missing-image warning, which now names thepublic/folder export searched. - The experimental theme editor's image notes read a theme's
url(/…)file the same way: a file at the project's root, not inpublic/, is now reported as missing.
- When the project has no
astryx experimental renderand--reversesay that a file they cannot read cannot be read, with the reason (EACCES: no permission, a folder or a pipe given as the file), and the new error codeERR_READ_FAILED. They used to say the file does not exist, withERR_FILE_NOT_FOUND, which a file that is not there keeps.astryx experimental exportnow fetches each image a page names by anhttpsaddress, once while the page renders, and the file carries it, so the image shows in a viewer that blocks the network. The render sends no cookies or credentials, takes only an image (by its type and its bytes) up to 8 MB, and gives each image 2 seconds to answer and 5 to arrive, and all of them 15, and asks for no more when the network answers none of the first ones. Any failure (no network, no answer in time, not an image, too large, or an address that is nothttps) leaves the address as the page wrote it and warns, naming why; an address the page's code holds that counts as an image only by a name (an object'ssrc,imageUploadUrl) is listed, and its fetch adds no warning, when its answer is another type. The JSON result lists every address fetched and every one that was not (remoteImages); the text names the first ten of each and counts the rest.--reversegives back the page with its addresses. A fetched image travels with the file, so anyone who has the file can see it.astryx experimental export: an https image the page shows only later (after a click, in the next view) is carried too, when the page's own code writes its address whole. That means an address an element shows as an image (an<img>'s or an<input>'ssrc, an<img>'s or a<source>'ssrcSet, a<video>'sposter), written there or in a variable the same file reads there (const logoUrl = '…'with<img src={logoUrl}>); an address whose path ends in an image extension; or one a name says is an image: a component's or an object'ssrc,srcSetorposter, or a property or attribute one of whose words names an image (avatarUrl,cover_image; notlogoutUrl). An address written only where an element takes it for something else, such as an<iframe>'s or a<video>'ssrc, is not fetched, even when its path names an image, and the file puts no carried data there; nor is one whose path names a type that is never an image (clip.mp4). It is fetched with the same rules and limits as an image in the first paint, and listed inremoteImages. The page's script keeps every address as the page wrote it, so a link, a text, a comparison and the URL API read the page's own address. Where the browser takes an image's address (the same attributes, or a CSSurl()in a style the script sets), the file gives it the carried data instead, so the image shows offline. An address the code gives a fragment gets the carried image too; one it gives another query (${hero}?w=640, or the URL API'ssearchParams) can name another image, so the file asks the network for it. A link's address written inhref, directly or through a variable that only links read, is never fetched, even when it names an image file. An address that counts only by a name (imageUploadUrl, an object'ssrc) can be an API's or a player's: when its answer is another type (an API's JSON, a page),remoteImages.failedlists it with why, and the fetch adds no warning. Any other address the script draws later warns when its fetch fails, as in the first paint. No other address is fetched. An image address the code builds from parts where a whole one would count (a template or+chain that starts withhttps://) cannot be carried: aremote-assetwarning names it, its file and its line. An address built any other way is neither carried nor warned.astryx experimental export --reversegives back a page that imports through a path alias in a project whose alias leads outside the new folder, instead of refusing it. When the file the alias reaches, and every carried file it imports where the project has it, is byte for byte the page's copy, the page uses the project's files and their copies are not written (aliased.sameAsProject), so export, reverse, edit and export again work in the page's own project, again and again. When that file differs or is not there, the page's copy comes back in its own layout inside the new folder, never into a folder that exists, and the answer names the file the alias reaches today and any file it imports that differs (aliased.differs), with thepathsentry that leads the import to the copy. It says that entry applies to the whole project (projectWide) and gives the narrower fix: the relative import of the copy for each restored file that makes the import (instead). A file from a CLI that recorded no alias imports gets the samepathsentry, found from the carried file the import's path ends with.aliased.configandaliased.pathsnow appear only whenaliased.importsis not empty.astryx experimental render --reversegives back a page that imports files through a path alias (@/components/Header) in a folder whose project has no alias for those imports, such as an empty folder holding only the HTML file. A render records which carried file each alias import named; where no alias of the receiving project names the import, the file comes back in the page's own layout inside the new folder, byte for byte. The result'saliasednames each such import with its file, the wholepathsthe page needs to build (the entries the config has now, own or inherited, with every target the imports need), and the tsconfig.json or jsconfig.json it belongs in (the one TypeScript reads for the page, else a new one), and the text prints them. Only an import that cannot be a package name or a package's own subpath import is followed this way (@/…,~/…), so a received file can never remap a package or the reader's own imports. Such a page used to be refused as carrying "files the page does not import". Where the project's alias points outside the new folder, the restore is still refused; an import that looks like a package name (@components/Header), or a file from an older CLI, which records no alias imports, is still refused unless the receiving project has the alias, and the refusal now says so.astryx experimental rendernames at most 10 files in its text answer, then counts the rest and names the folder they share, such as "... and 190 more in page-restored/images/". A page with many images no longer prints a long line an agent must read. The JSON answer still lists every file.astryx experimental export --reversenames every file the render records as not carried as missing, soexactis false whenever one is. A rendered file now records the files the render left out, and the reverse adds them tomissing. This covers a module the page imports through a path alias from outside the carried folder, which the reverse cannot resolve and used to report as exact.astryx experimental render --reverserefuses two kinds of damaged Astryx page withERR_RENDER_SOURCE_DAMAGEDand writes nothing, instead of answering with a page that looks fine. A rendered file cut short before its embedded source used to come back rebuilt from the part of the markup that was left; it is now refused as cut short. An Astryx page a merge left with conflict markers used to give back one side's source without a word; it is now refused, naming the conflict, so you keep the whole file from one side or render the merged page again. A file that is not an Astryx page is still refused withERR_RENDER_NOT_ASTRYX, markers or not.astryx experimental exportsays what the file's size is made of, one line per part (scriptBytes,cssBytes,markupBytes,sourceBytes, with a note when the script is most of it), and addsmarkupBytesandsourceBytesto its JSON.astryx experimental exportkeeps a theme's rules for the parts a component draws only after the first paint, such as a Banner's icon, a tab's indicator or a dialog. Core builds those parts' class names while the page runs, so the cut now also keeps, for each name in the page's script, the class Core's naming module makes from it. Before, those parts lost their theme styles in the rendered file.astryx experimental exportwarns when a page gives a Core component's prop a value it does not have:unknown-prop-value, "page.tsx:12: Button has no variant "danger"; its variants are primary, secondary, ghost, destructive." Such a component draws no variant's look and nothing else says why. The check reads Core's own docs for the component in the page's Core (the propsastryx component <Name> --package @astryxdesign/coreshows), so an integration that replaces the component does not change it. Where a theme can add values to a prop (Button'svariant, Banner'sstatus, Link's and Heading'scolor, which take Text's colors), the values the project's themes add count too: the check reads the module augmentations in the project's own TypeScript files (a theme build's.variants.d.tsincluded) and in the declaration files of the theme and integration packages it installs. It checks only string values written in the page, for props whose type is a closed set of strings, on components imported from Core by name or through a namespace import (<Core.[Button](/components/Button)>). A value the page computes, a component that is not Core's, and a prop with no doc entry are not checked.astryx experimental render: a page that saves to storage or copies text keeps working in a viewer's frame that allows scripts but blocks storage or the clipboard (sandbox="allow-scripts").- Storage: there, touching
localStorageorsessionStoragethrows, and the page went dead after its first paint. Now the file gives the page an in-memory storage that acts as the browser's does, methods and properties alike (localStorage.theme,Object.keys(localStorage)). What it saves lasts until the page closes. A file opened from disk or on a real site keeps its real storage. - Clipboard: a frame can leave
navigator.clipboardout, refuse it by permissions policy, or refuse the write, so a page's own Copy button failed. Now the write falls back to the browser's copy command where Core's clipboard hook does. It resolves when the text was copied and rejects withNotAllowedErrorwhen it was not, so the page's own success and error paths run.readTextrejects withNotAllowedError, as a browser does.
The share guide now says what such a frame allows: forms, storage in memory and copying work; a cookie write throws, fullscreen and printing do not work, and a link opens only when the viewer allows pop-ups.- Storage: there, touching
astryx experimental exportfollows an import written the TypeScript way, such as./helper.jsforhelper.ts, to its source when it looks for the files a page uses. A module from outside the carried folder that imports one now gets that file named innotCarriedtoo.astryx experimental renderwarns when the page asks a media query in JavaScript, with Core's[useMediaQuery](/components/useMediaQuery)(from@astryxdesign/coreor@astryxdesign/core/hooks) or withmatchMedia. The rendered file runs no script, so readers on every screen got the layout of the answer the page had on the server, with no word why. The newscreen-querywarning names each query and says to fold the layout with CSS:[Grid](/components/Grid)withcolumns={{minWidth}}, or a StyleX@mediaor@containerstyle.astryx experimental theme editor: a role color the theme sets (accent, success, warning, danger, info) now reaches the parts where the base theme draws that role on its own: a variant named for the role in a color of the base's palette written out (a success badge or progress fill), a role token the base points at another color on a part (a success banner), and a color the base gives a part as its own accent written as the color itself (nav links, outline buttons). Those parts take the theme's color, the missed list no longer lists them, and a color the theme sets on the part itself stays.astryx experimental theme editor: a role's text and icons (warning, danger, success, info, accent) now start from the fill the theme really shows in a mode where it sets the fill token exactly, and the note names that color and calls the text by its role (warning text and icons) instead of the dial's color and "links and accent text".astryx searchno longer lists icons for aniconoriconsright afterwith(onlya,anorthebetween) when its results hold a component or template:card with an iconanswers the card alone. An icon described afteroforfor(card with an icon of a star), or named before the word (button with plus icon), still lists the icons that answer it.- With an icon set installed,
astryx searchanswers a query that asks for an icon (trash icon,SearchIcon, or a set's name) with up to three of the installed icons that answer it, after the results:iconsin the JSON, one line each in the text. The results and their count do not change, a search with--typelists no icons, and with no icon set installed every search answers as before. astryx search's icons block names a set two installed packages ship with its package (trash (@acme/glyphs/glyphs): …), as the JSONnamedoes, so the two lines no longer read the same. A set no other package ships prints as before.- When an unknown top-level word such as
shareorexportsuggestsastryx experimental export, the reason now says what the command is for, as its help line does: one self-contained HTML file from a page built with Astryx components. It used to say "a page as one shareable HTML file", which also read as an offer for pages that do not use Astryx. The command's summary inastryx experimental --helpandastryx experimental export --helpsays the same ("Export a page built with Astryx components as one self-contained HTML file, or turn one back into a page"), and the group's example is "Export an Astryx page as one HTML file". astryx experimental theme editor: the fills that follow a surface the theme sets (cards, popovers, the muted fill) keep their place between the page and the surface, as the base theme keeps them: a dark card that is the base page's shade never turns darker than the page the theme sets.- Twenty-one new icon meanings let templates that drew their own icon for a meaning keep it when they import icons by meaning:
copyText,paste,block,verified,alert,create,media,listView,currency,checklist,channel,team,schedule,help,signal,house,moveToFolder,columnSettings,halftone,groupRowsandreview. Each falls back to the meaning the template used before, so an icon set that does not map or declare the new meaning draws the same icon as before, and the set's unmapped template meanings leave it out when the set maps its fallback. The template icon table drawsinfoas the information circle; the form wizard's review banner keeps its badge throughreview, which icon sets draw asinfo. astryx templatewrites each icon placeholder a template imports (DeleteIconfrom@astryxdesign/template-icons) as the import of the icon the template icon table names for its variant (a Heroicon, or a Lucide icon for/lucide), under the same name. A project with an icon set then maps it like any declared template icon. The component showcase source and build's setup notes do the same.- The CLI ships the template icon table: for each icon meaning a bundled template draws, the Heroicon (or, for the lucide variant, the Lucide icon) that draws it. A private workspace package,
@astryxdesign/template-icons, is generated from it, so template sources can import icons by meaning (DeleteIcon) and previews draw the same icons. - Bundled templates pick each icon by meaning: the template icon test fails on an icon imported straight from an icon library, with the command that moves it. Copies are unchanged.
- Twenty-five page templates (ai-chat through kanban-board) import their icons by meaning from the template icon placeholders. Copies draw the same icons as before: the same Heroicons and Lucide icons with no icon set, and the set's icon for each meaning with one. Icon sets' template meaning counts read placeholder imports. The docs site's code view, playground, MCP source and ShadCN registry, and the theme editor's preview sheet, use the same filled source a copy writes.
- Twenty-five more page templates (library through work-item-detail) import their icons by meaning from the template icon placeholders.
astryx templatecopies draw the same icons as before, with and without an icon set. The template icon table gains a Heroicons drawing forwallet, so every variant of the table draws it. - Fifty-one block templates (AlertDialog through MultiSelector) import their icons by meaning from the template icon placeholders. Copies draw the same icons as before, with and without an icon set. The ChatSendButton custom-icon block's send arrow mirrors in right-to-left pages, as other send icons do.
- The last forty block templates (NavHeadingMenu through VStack) import their icons by meaning from the template icon placeholders, so every bundled template now does. Copies draw the same icons as before, with and without an icon set.
- When
astryx templatekeeps an icon imported from a subpath of the library an icon set wraps, its reason names that library too:it already comes from @heroicons/react/24/solid, part of @heroicons/react, which <set> wraps, not the subpath alone as if the set wrapped it. - The theme editor no longer loads all of Core when it checks a theme against its base. The check copied the build's module stand-ins with an object spread, and the spread read the lazy
@astryxdesign/coreentry, so each firstnew,setorhowin a process imported Core's whole root entry and React for a theme that imports only@astryxdesign/core/theme. The stand-ins are now copied with their getters, so the root loads only for a theme that imports it. Results do not change. astryx experimental theme editor how: a focus-ring change that keeps a status ("make the focus ring on inputs red but keep the invalid ones") keeps that status's ring as Core draws it while focused, on every input the new ring reaches, instead of writing the status's resting shadow.astryx experimental themereads its cached part data once per change of the cache file instead of parsing it again for every command in a process. The per-user cache of transpiled TypeScript is not read again when it has grown until its oldest copy could be removed, so a large cache no longer slows every theme command's first load.- The theme editor (
astryx experimental theme editor) reads the families and weights a base theme loads from its font stylesheet's own@font-facerules, as the built-in themes now ship them, so it keeps the base's weight notes and does not suggest installing fonts the base already loads. astryx experimental theme editor set <theme> font <family>says when the theme file covers the setting. Atypographyfamily or a--font-family-*token in the theme's own file wins over its settings, so set now names the roles that keep the file's family, the line that gives it, and how to change it, in text output as well as--json.- The theme editor reads a pagination's current page as its own cell. "Make the current page in pagination blue" writes
--on pagination-item --state selected, kept apart from every other button, instead of acurrentstate on every button, andbuttonno longer listscurrentas a state. astryx experimental theme editor show: a theme image named by a path from the site's root (url(/pics/paper.png)) that is not there now says it was looked for inpublic/, the only folder such a path is read from. Before, the note said the image was not found beside the theme.- The theme editor knows Core's calendar range band and keyboard key badge parts. "The calendar range band" is
calendar-range, and "range" is no longer corrected to "orange". "The key badges" arekbd-key; "keyboard keys", "the keyboard shortcut" and "the kbd" still read Kbd. A part that draws none of what is asked hands it to the one piece of its own inside it that draws it at rest, and names it: "make the keyboard keys gray" writes the fill onkbd-key. With several such parts, nothing is written and the answer names them. Spacing asked between the parts a holder lays out side by side ("more space between the keys in the keyboard shortcut", "between the tokens in the tokenizer") is that holder's gap. A fill set onkbdor oncalendarwas refused, because the key badges and the range band painted over it from a token; they are parts of their own now, so that fill is taken and paints the group's own box. astryx experimental theme editor undorefuses athemesthat is a file, not a folder, by name on Node 22.13 too ("themes in this app is a file, not a folder …", withls -la themesto see what is there). Before, on the CLI's oldest supported Node, it stopped with a raw "ENOTDIR: not a directory" error instead.astryx experimental theme preview add <description>adds a page only when build is sure of its start. When build starts from the app shell, or from a page its page pick gives less than a clear fit (start.fitunder build'sCLEAR_FIT), it refuses, says why, and offers the nearest pages this app can show by name (--template <id>), then the list of every page. A description that names a page by its id or display name, names an app the preview has pages for, or names a page build's ranking matches by its name or a keyword, still adds it.astryx experimental theme editor how:- A value no page could show, such as a line height of 0 or 99999px of padding, is not written. The answer gives the range that works instead.
- "List items more spacing between them" points to the list's gap, not each item's padding. A visited link gets the "no visited state" answer.
- "selected tab with a 2px underline" gives the tab underline. "the selected date in the date picker" names the calendar day.
- When the page background is part of a longer request, the combined line also paints the frame and main panel, as the page's own answer does.
- White text asked for the header goes to the mode where it can be read, and the answer says how to have it in both modes. Readable-text lines no longer print an empty "()".
- "buttons font weight medium" sets a weight, not the medium size. "semibold instead of bold" is one request.
astryx experimental theme editor howwrites nothing for more kinds of messages that don't ask for a change:- Tag questions: "spacing is compact, isn't that so".
- A question about how the theme looks now, beside a look it names: "cards no border. is the shadow still there?".
- A question about what a dial does: "what does spacing less do". The answer lists the examples in its text instead of offering them to run.
- Sarcasm shown by emphasis or a "yes because" reply: "yes because neon green links are SO professional".
- A past hypothetical: "had we gone with serif headings".
- A change timed to a later event: "after the review, square the buttons".
- An ask that takes back a setting the theme doesn't have: "accent red; also undo the corners" with no corners set. The answer says so, and asks for the rest on its own.
Other fixes:- In a sequence ("make it compact, then make it roomy"), the later step now decides where it ends, instead of the two being offered as a contradiction.
- "badges: no fill" now makes the badge see-through, including every variant the theme fills itself. It no longer takes back those fills, which brought back the base theme's solid fill.
- A screen named by what it shows ("a records table view") no longer counts as that part.
- A real word is no longer read as a typo of another word that differs at its first letter ("stable" is not "table").
- "no shadows" after a part that draws no shadow ("visible focus ring, no shadows") now applies to the whole theme.
set … buttons outline(orsoft) no longer claims that an exact text color on the button's plain rule wins on the primary button. The primary label is now measured on the fill an exact property gives that variant.
The answer to a list of looks for a part now reads each item as part of that list:- A subject how doesn't know ("flurbles: subtle gray background") writes nothing and names the word. It never falls back to changing the whole theme.
- Other design systems' names for a part now resolve to that part: a snackbar is a toast, a lozenge is a badge, and form controls are the inputs.
- A length and a color after the part's line ("inputs: 1px border #79747e, 2px #6750a4 when focused") are that line in that state, not a fill.
- A color word with its value after a text ask ("uppercase 12px text, gray #6b7280") is the text color.
- A day in the date picker ("date picker: today's date circled") is the calendar's day, and gets the calendar answer instead of filling the field.
- A state at the end of a with-item ("red background with white text on hover") applies to the whole look, so it no longer contradicts the resting fill.
- A text color for every button keeps per-variant lines when only a hover fill comes with it.
- A part label with padding ("dialogs: no border, 16px padding") writes the padding on that part.
- Corners on some sides ("4px top corners and square bottom corners", "4px corners on top only") change only those corners. A step on some sides asks for a size.
- A color said with a shape ("a #e8def8 pill") is that shape's fill.
- "divided by 1px lines" is no longer read as a change by 1px, and "shadow-sm" is the small shadow.
Real asks said next to a question ("set font to Inter; does that need an import?") still write.astryx experimental theme editor how:- Two-word color names ("off-white", "ink blue", "grass green", "safety orange", "slate blue-gray"), tan and paper now resolve through the color table. Off-white is a warm off-white. "pure white" means exactly white. "amber for warnings" sets the warning color. A typed value said with a named color, as in "bold safety orange #ea580c accent", wins.
- "make it calmer" and "a calm dark mode" lower vibrancy. "more cheerful" means more colorful.
- When no command can do the whole request, the text output now says each result explains why, instead of pointing to lines "above" that appear below.
- Tailwind shadow sizes ("shadow-sm") map to the editor's shadow sizes.
- "dividers between list rows" and "table rows divided by 1px lines" give a bottom border. "32px rows in the menu" sets the menu item height.
- "should be a #e8def8 pill" gives that fill with pill corners. "dialogs with a dark overlay behind them" darkens the overlay. "big touch targets" makes buttons and inputs bigger. "a 2px dark border" uses the theme's stronger border color.
astryx experimental theme editor set: a step past a dial's last rung names an exact line only where one setting does it. On a part, spacing goes on in the control height the part reads ("bigger buttons" at the top rung offers--size-element-md 46px --on button); the text size offers a size it takes; the whole theme's spacing, which no one setting carries, claims no exact line. A one-mode theme reads its own mode named with--mode(--mode darkon a dark-only theme) as the same as no--mode, insetas inundo, and says so. A control height offered past the top rung is measured from the base theme's own height, so a base with taller controls offers a taller line.astryx experimental theme editor: a role color the theme sets now reaches a badge or other part the base theme draws for that role in a color of another family (stone's info badge in its categorical blue): the part takes the role token the base gives that same color, so its look stays and it follows the role.astryx experimental theme editor: the fix line for a loading placeholder that does not show now offers the theme's own gray nearest the placeholder's color (else a darker or lighter shade of that color), not a plain gray.
astryx experimental theme editor: a value drawn on a track (a progress bar's fill) that a theme makes vanish on it, below 3:1 at rest, is now a problem with the nearest track color that reads, set on the track alone; a slider's thumb, larger than its track, counts only where it reads neither on the track nor on the page. Before, a black border the track follows and a near-black accent left a progress bar as one black bar with nothing reported.astryx experimental theme editor how <part>names what a token shows where the base theme points it at another one on the part or a part around it (neutral's progress track reads the muted fill, which it points at the emphasized border:shows: --color-border-emphasized), and a border the emphasized border follows names the parts the base theme draws from it (the progress bar and switch tracks).
New Features
- The agent block that
astryx initwrites ends with one line on how to remove it: runastryx init --remove-agents, which removes it from the agent files at the project root and in the folder you run it in, and delete any other copy between its markers. Asked to take Astryx's text out of a project, agents deleted whole agent files or cut one copy by hand and left the others; with the line, they run the command and remove what it leaves. astryx upgradekeeps each theme's chat corners now that--radius-chatfollows the container radius: it adds--radius-chatto the tokens of eachdefineTheme()theme (28px, or the page step of its radius scale) and the page step to each adaptation rule with a radius scale. A theme that extends an Astryx theme, or a theme this project defines (a relative or aliased import is trusted to be one), and has no radius scale of its own inherits its base's value; one that extends another theme, such as one from another package, gets a TODO that also covers that theme's adaptation rules. It leaves a TODO where it cannot read the theme, and reports a default-exported object shaped like a theme for manual migration. The token it writes is declared at the theme root, so a value a project sets on an ancestor such as:rootno longer reaches the theme's chat surfaces: set the token in the theme instead.- The Best Practices section of
astryx component <Name>,astryx hook <name>and an integration component read throughastryx discover <package>/<Component>puts aDo:orDon't:label line before each run of items with the same guidance, instead of repeating a bold badge on every item; a blank line separates runs, so each run stays its own Markdown list. Every item keeps its place and its guidance;--jsonis unchanged. astryx buildlists blocks as examples to read, not sections to insert. The kit starts from the template, builds its parts with components, and shows up to three BLOCK EXAMPLES for reference. The JSONblocksfield keeps its shape and still holds the same blocks, now shown as examples.astryx buildpicks which page template to start from with a second word model, once the existing model has called a page. The page-or-shell and page-or-block calls are unchanged; only the choice among page templates changes.astryx buildreportsstart.fiton a page-template start: the page-pick model's probability for that template among the ready page templates, from 0 to 1. At 0.4 or more the choice is clear; below it, several templates fit about as well. It is absent for a template the word tables do not list.--verbosetext shows it too.- Bases, first step: a run resolves one base. The new global
--base <package>picks it; otherwise, in an integration package, the base it is or builds on; else the project's Core; else its one installed base; else Core. A package becomes a base by declaringbasein its integration manifest. Commands and options that need a platform step the base does not serve (theme build, add, use, remove, targets, and template;template --skeletonand--cdn;integration add theme;experimental render) are hidden from help and refused withERR_BASE_CAPABILITY. Commands do not call base adapters yet, so a base other than Core serves no platform step. In a run on another base, component, hook, swizzle, template, docs, search, and codemod reads leave out Core's items and answer from the integrations that build on the base (an empty list or an unknown name). There,buildnames no Core frame or foundation components; thehook --listandswizzle --listenvelopes name the active base as their package;upgrade --fromtargets the active base's installed version, runs only the codemods of integrations that build on that base (even whenastryx.configdoes not list the base), checks no copied ShadCN composition (with--registrytoo), and keeps the agent-docs versioninitwrites; anddoctorchecks that the active base is installed instead of reporting Core and Core's theme packages as missing.component --list --detail compact|fulllists no integration's components, so on another base that view is empty (the base's own components appear in the default list). A project with no base-declaring integration gets the same command output as before, except that root help gains the--baseoption; the "Component style overrides" lines of theme help, and the--jsonunknown-subcommand suggestions ofthemeandexperimental, start with an integration'scliCommandwhen one is declared, as every other printed command does; andastryx manifest --jsongainsbase,availableon each command and each command option, andrequireswhere a command, option, or argument declares steps.--baseis a global option, soexperimental theme editor new <name> --base <theme>reads it as the base library and refuses withERR_BASE_NOT_FOUND; the refusal suggests the same run with--like <theme>, which stays the editor's base-theme option. - The bundled official themes export
colorModes, the modes each draws: gothic['dark'], the others['light', 'dark']. astryx docs --listlists every docs topic: the same list thatastryx docsprints with no topic, in text and asdocs.listwith--json. It used to fail withunknown option '--list', whilecomponent --list,template --listandhook --listeach list their catalog. Every other docs flag reads with--listas it reads with no topic; a topic or section beside--listis refused withERR_INVALID_ARGUMENT.docs()takes the samelistoption.astryx docs <name>points to the right command when the name is a component, hook or template rather than a docs topic. The read still fails withERR_UNKNOWN_TOPIC, and its first suggestion is now the command that reads that entry, such asastryx component [Button](/components/Button),astryx hook [useHotkeys](/components/useHotkeys)orastryx template ai-chat. Only an exact name counts, in any case and with or without spaces and hyphens (docs text-inputpoints toastryx component [TextInput](/components/TextInput)); a hook also answers to its name withoutuse. The suggestion keeps the usual{name, reason}shape and takes the last suggestion's place, so the list does not grow. When no docs topic shares a word with the name, it is the only suggestion, instead of the whole topic list. The check reads file names first and loads no docs for other names, so a docs miss stays fast. Docs routes and docs typos get the same suggestions as before.doctor's cache row names the docs not-found hint's name summaries.astryx doctortext used to print each check as a block ofid:,status:,label:,message:andfix:lines, with the summary counts on four lines. It now prints each check as one record: its status ([ok],[warn],[fail],[info]) in a column, then its id, label, message andfix. A legend under the heading names each field by its--jsonkey, and the summary prints its counts on one line. Every field still prints, so the answer reads the same in less space: about 10% less on a small app checked with--built. The JSON output does not change.astryx doctor integration validate(and sointegration check) lists each component example that is notkind: 'setup'but cannot run on its own, the way a docs page or catalog card runs it as a live preview: code that does not compile, such as a top-levelreturnor code that stops partway (example_does_not_compile); code that renders nothing (example_renders_nothing); a name the example never defines or imports (example_undefined_name); an import of code that runs only on a server, an async server component it renders, or a read ofprocess.env(example_server_only); and an import of a relative path or of a package the package does not declare (example_import_unresolvable). Each is a note with its fix that failsintegration check --strict --nextnow and--strictfrom the next minor release, so no build that passed before fails. An example may use without importing the components its package documents, the components and hooks Core documents, React's exports, and browser globals.previewableExample(example, scope)from@astryxdesign/cli/authoringis the same rule for a tool that shows examples as live previews: it returns the module to bundle, or why the example cannot run.integrationExampleScope(pkg)from@astryxdesign/cli/apireturns the scope Doctor reads a package's examples with, as JSON, so a catalog can store it and a preview tool read each example exactly as Doctor does.showcase_not_standalonenow reads the same packages: a Node built-in name such aseventsthat onlydevDependenciesinstalls counts as server-only, because an app that installs the package does not get it.astryx component,astryx hookandastryx templatenow point to the right command when a name they do not find is an entry another lookup command reads, asastryx docsalready did. One rule serves all four commands. An entry's name is its full id: a component, hook or template id, or a docs route. A name matches the typed name at one of four tiers, best first: exact (the whole name, in any case); folded (the whole name without spaces and hyphens, and a hook with or withoutuse); last segment (only the last segment of a path id or docs route, exact or folded); words (the name carries every typed word). When the typed name matches another command's entry at one of the first three tiers, that command joins the suggestions by the entry's full id, such asastryx hook [useHotkeys](/components/useHotkeys)forcomponent use-hotkeys,astryx component [Button](/components/Button)fortemplate [Button](/components/Button), orastryx docs typography/font-setupforhook font-setup. A better tier wins; inside a tier, a component comes before a hook, a hook before a template, and a template before a docs route; among docs routes, the route with the fewest segments comes first, then the first in tree order. The hint goes right after the command's own suggestions that match at its tier or a better one, so it is first only when none does. The list never grows: the last suggestion drops, and a hint that would come last is left out; when a command had no suggestion, the hint is the only one. Every hint names an entry the hinted command reads: a template only whenastryx templatelists it, and any route of the docs tree, namespaces included. The error code and the{name, reason}shape stay. Docs keeps its rule that the hint stands alone when no topic shares a word with the name, andcomponentkeeps its example-block message, which already namesastryx template. Names that resolve still resolve as before, and a miss stays fast: file names and doc text say first which components, hooks, templates and docs routes can match, so only those are read.- For AI tools that cannot run commands,
astryx mcpserves every astryx command as a Model Context Protocol (MCP) tool, over standard input and output; agents that can run commands keep using the CLI. Each command that answers with--jsonis one tool, named by its words (theme buildistheme_build), with the command's arguments and options as its inputs under their CLI names, and every root option except--jsonand--version; an input a tool does not list is refused. A tool call runs that command with--jsonin the project folder, or in a folder inside it that the call names, and answers with the command's output unchanged; a command that exits non-zero answers as an error. The tools come from the same command definitions as--helpand the manifest, so a new command or option is a tool input at once. When the project has no agent docs yet, the server gives the agent the textastryx initwrites.astryx mcp --docs-onlyserves only the commands that read the docs (search,build,component,hook,docs,template,discover,theme listandtheme targets), one message at a time, without the inputs that name a folder, a file to write or a package to read (cwd,path,cdn,overwrite,packageandbase); the docs site's MCP server is this command.astryx mcp --jsonexits 1 withERR_INVALID_OPTION, because standard output carries the protocol.astryx docs working-with-aishows the client entries. - Component docs:
playground.mobileholds the props of a second render at a phone viewport, merged overdefaults, for a component whose layout changes at phone width; the theme editor's part census renders it too. AppShell declares its mobile layout there (the menu button in the top bar, the open drawer); its playground defaults are unchanged. - A command doc's option can declare
pointers: parts of its description that help leaves out when the run's base does not serve what they name. On a base other than Core,astryx template --helpno longer names--skeletonin the--listtext or suggests--package @astryxdesign/core, andastryx mcp --helpno longer namestheme targetsin the--docs-onlytext. astryx component <Name>prints a short answer by default: what the component is, its import, a usage line, every prop as one line (name, type, default, required, and its description's first sentence), its accessibility requirements, its pieces with one command that reads them all, and the commands that print the rest (--propsfor each prop's whole description,--detail fullfor anatomy, best practices, examples and theming). The same answer is--detail compact;--detail fullprints the whole doc as before, and--jsonis unchanged. Every part comes from fields each component doc already has, so an integration's component gets the same answer.- The computer-level agent text says that inside a project with its own Astryx text (an
astryx-projectskill, or an Astryx block in AGENTS.md or CLAUDE.md), an agent follows that text, which knows the project's version and setup. Asked a vague question about a project, agents loaded the generic computer text and missed the project's own facts. astryx discovernames the sections an installed integration adds to a doc another package owns, so a reader can open its own section straight away: the list prints the read beside the doc,docs: theme (read: astryx docs theme install-and-apply), the JSON entry gainsdocSections(each name's section keys, each opening withastryx docs <name> <key>), and the doc's item page gainssectionsand prints the same reads.astryx discovershows an installed integration's package.jsondescription, as it already did for a package a source lists: on the list's Installed side and on the package page (discover <package>). Text shows its first sentence;--jsoncarries the whole description as the entry'sdescription. Terminal escape codes and control characters are removed, and a blank description is left out. Search (discover <words>), which already matches package descriptions, now also finds an installed package by a word in its description.astryx discover <words>matches word by word, asastryx searchdoes: every word is part of the query, and an item matches by the words of its name (camelCase split), title, summary, and keywords, with its package's description adding words. Sodiscover chart categoriesfinds aBarChartwhose summary says "Compare values across categories", which the old whole-phrase match missed. When an item matches every word, only such items are listed; matches rank by how many words they match. When nothing matches, the error suggests the Core component or hookastryx searchgives first for the query, such asastryx component [AlertDialog](/components/AlertDialog)fordiscover modal, when search matches it by name or keyword.astryx searchnow prints its "More in packages you could add" line only when thediscovercommand it names would list a match: discover's own search, run over the saved copy of a discover catalog, decides. With--type <kind>, the line namesdiscover <query> --type <kind>. With no saved copy, the line prints as before. Search reads only the saved copy and never calls a discover source.astryx docs <topic>prints the topic whole, as--jsonalready did, so a guide's first read carries its rules and examples. A topic whose own text is over 16 KB still lists its sections, and a whole read ends with the commands that open one section or the section list.--indexlists the sections of any topic, and--fullprints any topic whole.astryx doctorwarns about a Core button that does nothing when pressed (button-actions): a[Button](/components/Button)or[IconButton](/components/IconButton)from@astryxdesign/corewith noonClick,clickAction,href, orsubmitorresettype, or with an empty handler or a link that goes nowhere (#, unless the app routes by the URL hash), where nothing around it acts on a press. The warning names each button's file, line and label. Doctor reads the app's own source as syntax trees and leaves out test, story and fixture files. It does not report a button it cannot judge: one with props spread in, a ref, a tooltip, or a disabled or loading state, or one inside a link, a trigger prop, a custom element, aProviderread off a namespace import of the app's own module, or a component it does not know, or one that holds an HTML control, a custom element, another package's component other than an icon, or content doctor cannot read ({children}a wrapper passes in). It does not judge a workspace member's buttons when the app imports the member by its package name. When doctor cannot follow a linked folder, it treats no component as a page. When the app's own code listens for a press through the DOM (addEventListener('click', …), anaddEventListenerwhose event a variable names, a library's.on('click', …), or anonclickproperty), doctor judges no button and reports the check as not run. Nor does it judge a component that a module may load by a path doctor cannot read (a computedimport()orrequire(),import.meta.globorrequire.context, in a module, an MDX or Astro page, or a module that does not parse), or that an MDX or Astro page names. The check never failsdoctor.astryx doctorwarns about a prop the app gives a Core component that the component does not take (core-props), such asselectedIDon[TabList](/components/TabList)orlabelHiddenon[CheckboxInput](/components/CheckboxInput). Such a prop does nothing, and unless the build type-checks, no build step reports it. The warning names up to eight props, each with its file, line and component and a documented prop with the same words when there is one, and counts the rest: "src/App.tsx:6 CheckboxInput has nolabelHidden(did you meanisLabelHidden?)". A prop is reported only when Core's docs for the component leave it out and Core's own types, read with the project's TypeScript as its pages see them, do not take it either. The name of an HTML, SVG, DOM or ARIA attribute, which a component can pass on to what it renders, is never reported, and neither is a name with a hyphen (such asdata-orhx-attributes), which JSX never checks against a props type, a prop that JSX gives every component (such as acssprop the project's own types declare), a prop of a component from outside Core or of a generic component, or a prop in a module compiled with another JSX runtime. Doctor reads the app's own source as syntax trees and leaves out test, story and fixture files. Without TypeScript, or in a project whose TypeScript or build config compiles JSX with another runtime, the check says it did not run. The check never failsdoctor.astryx doctorprints a short kept-cache row. Before, thegather-cacherow printed a paragraph of about 2 KB: every kind of kept result, when each is used, the size limit, the transpile cache, and "deleting the folder clears it". Now the row prints only the folder, its entry count and size, the command that lists every kept item and the size limits (astryx doctor --json), and the exact command that clears the caches, such asrm -rf ~/.cache/astryx/catalogs. That command also names the transpile cache folder when it exists. The JSON check keeps its wholemessageand adds an optionalbrieffield with the short form, which text prints in the message's place; the legend then readsmessage (or brief). Ids, statuses and exit codes do not change.- With no update check recorded,
astryx doctor'snewest-releaserow reads "Newest release unknown: no update check recorded here. Only a copy installed for the computer checks, daily in the background after a command; a project's copy changes only when the project upgrades it; a tool running its own copy picks its release." Thegather-cacherow keeps its list of what is kept, and states the CLI's build id, the lookup commands' not-found path and the size limit in short clauses. Check ids, statuses, fields, the JSON shape and exit codes do not change. astryx doctorwarns when a setting of an added local theme does not show as written (a later shorthand resets it, a more specific rule of the theme it extends wins, or cascade order decides), naming the theme, the setting with its line, and the fix, from the same checkastryx theme buildruns. It is a warning, never a failure: the theme builds as before.astryx init --to <places> --oncewrites a copy that is saved nowhere, so no laterinit,upgrade, or background refresh touches it (a bundle, or a skill to upload elsewhere).astryx init --removeremoves the Astryx skill from every place the project saved, and with--tofrom the places it names, in the project, a folder outside it, or the computer (--remove --to user), and drops each from what is saved; an edited skill file is kept and named.--remove-agentsis now the same option as--remove; in a project that saves nothing it removes the block as before, adding one note when a folder is saved for this computer (kept, with the command that removes it), and itsinit.removeresult gainsfrom,skills, anduser.--onceis refused for the AGENTS.md block and for a place already saved, and a skill file Astryx did not write is kept, a linked skill folder's included, while an unedited Astryx file is the place's own through a link too (a folder saved for this computer where every file was kept is not saved; in the project, linked copy folders share one file, written and removed once); the computer-level skill and its links and copies, reached through a saved folder such as~/.agents/skillsor~/.claude/skills, are kept (astryx init --remove --to userremoves them).astryx initsays what it did to each agent-doc file:[ok] AI agent docs: AGENTS.md updated (Astryx 0.7.15 -> 0.7.16),... created,... already current, nothing changed, or...: Astryx block removed, another agent file holds it. Theinit.runreceipt addsdocsChanges({path, change, from, to}per file, indocsWrittenorder); every earlier field keeps its name and value.astryx initin a project whose Astryx agent-docs blocks are all current prints thebuildandsearchcommands (and where the setup guide is) instead of the five install steps, since the app is already set up. It judges the files the run writes: the--agent-docs-pathfiles, the--agentpreset's file, or every agent file at the root. A first run, or a run that refreshes an outdated block, still prints the install steps. Theinit.runreceipt addsagentDocsStatus(missing|stale|current, the agent docs before the run; null when agent docs were not installed or the write failed);nextStepsis false when the steps are left out.astryx init --to <places>puts the Astryx skill where your agents read it:agents-md(the AGENTS.md block, still the default),skills(theastryx-projectskill in.agents/skillsand.claude/skillsin the project, named apart from the computer'sastryxskill so neither hides the other),user(this computer, the same as--user), or a folder written as a path. The choice is saved: in astryx.configskills.tofor the project, so a laterastryx initwrites the same places, and in the settings file for a folder outside it, whose copy the CLI installed for the computer refreshes after each of its upgrades while it is there (delete the copy to stop it). Moving a project to another place removes the skill from the old one.astryx initwith no--toand nothing saved writes exactly what it wrote before.- An integration can say how its apps add a dependency:
installGuidancein its manifest, one line where{packages}stands for the packages to add. Where the CLI prints a step that adds packages the app lacks (template readiness,init's theme step,doctor's fixes, theme hints and errors,theme eject, the theme editor's notes, anddiscover's add commands), it prints that line instead of the package manager's command; thetemplateandtheme ejectreceipts carry it asinstallGuidancebesideinstallCommand. Steps that move Astryx's own packages to another release, or add@astryxdesign/cliat the project's Core release, keep the package manager's command. Without guidance, doctor's Core and peer-dependency fixes,theme build's no-Core message andrender's missing-package suggestion now print the project's package manager in place of a fixednpm install. Two different lines cancel out, and a newinstall-guidancedoctor check warns. An invalid line is ignored with aninvalid_install_guidancewarning. - An integration can ship a skill: a doc that sets
skill: {name, description}becomes a skill of its own in every app that keeps the Astryx skill in a skills folder (astryx init --to skills), and the AGENTS.md block gets one line that names it and points toastryx docs skills/<name>.astryx docs skillslists every skill a folder has (the project skill, the computer skill, and each integration skill), andastryx docs skills/<name>reads one.astryx upgrade --applyrefreshes integration skills and removes one an integration no longer declares,astryx doctorchecks them, andastryx discoverlists them. A skill that breaks a rule (its name, a repeated name, its description) is left out with a note, and its doc still loads.agentDocs.appendkeeps working as before, and a project whose integrations declare no skill gets exactly the block it got before. astryx theme add, on the first add, when an installed package names the provider that wires its themes, says so: "This app may already get its theme from <Provider> (from <module>, declared by <package>)", with the props it takes the theme and mode through. When that one provider takes the theme (its manifest'sthemeProvidernamesthemeProp), every receipt that shows wiring shows that provider in place of a Theme wrap: the first add passes the generated module's theme to it (<Provider theme={themes[defaultThemeSlug]}>, plus<modeProp>={themeModes[defaultThemeSlug]}for a theme with one color mode when it namesmodeProp), a later add that first liststhemeModespasses the mode to it when the manifest namesmodeProp, andtheme removeof the last theme undoes those props and keeps the provider. With nothemeProp, or two such providers, the first add names each provider and its trade-off ("Replacing <Provider> applies this theme everywhere but also drops anything else it sets up; a Theme inside it themes only what it wraps.") above the Theme wiring. No receipt reads app source. The JSON carries it asappProvider: each provider as{export, from}(withthemePropandmodeProp),wire, andthemePropandlinewhen the provider form applies. An integration manifest'sthemeProvidertakes an optionalthemePropand, beside it, an optionalmodeProp.themeProvideris a hint and never stops a manifest loading: a part this CLI cannot use (an export that is no component name, a prop that names no prop, amodePropwith nothemeProp) is dropped with anignored_manifest_fieldwarning.- For an app whose theme its integration's provider wires,
astryx doctornames the theme a stylesheet of the package belongs to: one in that theme's own folder, or one its stylesheet imports.astryx theme listsays on each such theme'swiredByline that the provider applies when the app renders it, and thatastryx doctorchecks where. - An integration that wires its themes with its own provider component can name it once in its manifest:
themeProvider: {export, from}.astryx doctorthen counts the package's theme as wired when the app renders that component (the theme whose stylesheet the app imports, or the package's only theme), instead of warning that no theme is wired, and its CLI-managed-themes check names the theme and its provider instead of offeringtheme add. An import of the provider that is never rendered still does not count. A stylesheet the app imports from the package counts as the theme it is, wherever the package keeps it; doctor names it, and never calls it missing when it cannot match it to one theme.astryx theme listshowswiredBybeside each of the package's themes, in text and JSON; its added and default marks stay as they are. A CLI that does not know the key, or a key inside it, ignores it with a warning and keeps the rest of the manifest. - When
astryx componentorastryx templatefinds no entry, the not-found error also points to a hook the name nearly spells or names by meaning. Ause…name one or two slips from a hook's name, or one whose every word that hook's name carries (useTableExpansionfor[useTableRowExpansion](/components/useTableRowExpansion)), suggests that hook (astryx hook <name>). Forastryx component, a name of two or more words that are exactly a keyword one hook's doc declares (CopyButtonfor a hook whose doc listscopy button) suggests that hook. The hint goes first only when no own suggestion matches as well: a suggestion whose name nearly spells the typed name or carries every typed word, or a component whose doc keywords or search-card synonyms hold the same phrase, stays ahead of it. The list never grows, the lookup still fails, and a name that already matches another command's entry by name keeps that hint. - Palette generation has a second recipe,
astryx-oklch-v2, besideastryx-oklch-v1: its pale stops, where a vivid seed asks more than the sRGB gamut holds, follow the vibrancy and each seed's own chroma instead of all landing on the gamut's edge, and a dusty seed stays dusty there; the dark side of a ramp, and every pale stop whose gamut holds the most vivid seed at the default vibrancy, are drawn exactly as v1 draws them, so role text and dark fills keep their strength. New palettes name v2:astryx experimental theme editorrecords"recipe": "astryx-oklch-v2"in each palette config it makes, and the palette guide's example config names it. A request or config that names no recipe still runs v1, fromgenerateTonalPalette()andastryx theme palette generatealike, so existing callers, the shipped themes' palettes and any existing config keep their colors; a config keeps the recipe it records, and naming one pins it. A theme the editor saved before keeps the recipe it was made with, and a color change on it says how to move it. astryx component <Name>(and its--propsview) lists props one per line,- `name`: `type` = `default` - description, with the required and experimental markers after the type, instead of a four-column table. Union types keep their pipes as written, and no field is dropped;--jsonis unchanged.astryx component <Name>prints the first sentence of each prop's description, under one line naming the command that prints them whole: the read's own selector and--packagescope with--props, so it resolves to the same component. A read prints its descriptions whole when that line would cost more than the cut saves. The--propsview,--jsonandastryx discoverkeep every description whole.astryx searchprints the first sentence of each result's description instead of the whole description, so a list of 20 results stays short. Component, hook and doc results' commands print the full doc;--verboseand--jsonkeep descriptions whole.- Every
--jsonresult that lists or returns a template gives itisReady: false for a template whose doc setsisReady: false, else true.discover, which names a package's templates only by id, carries neither. That coverssearchresults,build's start, alternatives, pages and blocks,template <id>(shown,--skeleton, and copied), andcomponent <Name> --blocks;template --listalready had it. In text, those commands mark an unready template(not ready), andtemplate --listsays(not ready)instead of(WIP). Search still lists an unready template in the same place. - In an Astryx project, and outside any package,
astryx searchfinds the experimental guides for sharing a page as one HTML file. A search for words like "share", "single file", "static html", "snapshot" or "artifact" now returns them, one entry per guide, and each says it is experimental; every other experimental doc still stays out of search, and in a package without Astryx search answers as before. A reference doc gains the optional fieldsearchable: true, which only these CLI guides may set. - Outside a project, when a tool runs the CLI for you from its own package set, a page can use the other packages that set's
package.jsonlists, such as an icon library, as it already uses Astryx, React and StyleX.renderrenders a scaffolded template page with nothing to install, andtemplateno longer asks you to install those packages there. Before,templateprinted annpm installstep for the template's icon library, andrenderstopped until you ran it. In a folder with nopackage.json,template,buildandtheme ejectnow name a package that nothing provides as missing, for the project that uses the page, instead of printing an install step that would turn the folder into a project. astryx upgraderewrites the deprecatedswipeActionsandswipeBehaviorprops of[Item](/components/Item)and[ListItem](/components/ListItem)toswipe={…}where each entry is an object literal. It defines each swipe once with[createSwipe](/components/createSwipe). The definition goes to module scope when every value outside a handler is fixed at import: a literal, a JSX element, an import or a moduleconst. It goes intouseMemoin the enclosing component or hook when the options read its props or state. A function counts as one when it is declared or assigned under a capitalized oruse…name, directly or throughmemoorforwardRef. Each entry with noidtakes one named after its label or handler, else its side and place, with a TODO. On a[ListItem](/components/ListItem), a handler that compares the row'sitemKeyvalue with===or!==takes it fromonActivateinstead. Where it cannot define a swipe once, it keeps[createSwipe](/components/createSwipe)on the row and leaves a TODO. That covers options that read a map callback's value, a ref'scurrentor a local assigned after its declaration. It covers a local they read at render when code sets, updates or deletes a property read from it. A method called on such a local counts too, and so does passing it to a call, naming it again, storing it or returning it. It also covers options that call or read at render something that is neither fixed nor one of the component's own props, state or locals. The codemod assumes that props, state and hook results are not changed in place, as React's rules and the React Compiler assume. Only an entry'sonActivateruns when the action fires; any other callback in the options runs at render. On an[Item](/components/Item), that TODO says an[Item](/components/Item)passes noitemKey. It reports, and leaves unchanged, a value whose entries it cannot see and a JSX spread that may carry the props. It migrates a condition only when it can read every id and prove both swipes key alike exactly where the deprecated props did. Otherwise it leaves the condition unchanged, with a TODO.- The
tableandincident-consolepage templates are ready, so build can start from them. - The markdown tables in
astryx component <Name>,astryx hook <name>and an integration component read throughastryx discover <package>/<Component>use a three-dash rule under each header cell (|---|---|) instead of a rule as wide as the header text. Tables render the same in markdown. - The
tablepage template now builds what its description promises: sortable columns, row selection into a bulk-action toolbar, and a per-row overflow menu, with a confirm step before removing members. It stays unlisted (isReady: false) for now. astryx template <name> <path>names the components the written file uses in one line right afterCopied template to ...:Read the components it uses in one call: astryx component A B C, so an agent reads them all in one call instead of one at a time.astryx template <name>prints the same line to stderr, so stdout stays the source. The names are the onesastryx componentanswers in the project (Core's and each configured integration's), in the order the file first renders them, each once, and in a project with an integration each is written as<package>/<Name>for the package its import names, so the read never opens another package's component; a chart library's parts and the file's own helpers are left out, and nothing prints when none are left.--jsoncarries them ascomponentson thetemplate.copyreceipt and ascomponentsToReadontemplate.show; every existing field is unchanged.astryx template --listprints the first sentence of each template's description, so the catalog is about a quarter shorter.--jsonkeeps descriptions whole, andastryx template <id> --skeletonprints a template's whole description above its layout. The first-sentence rule thatastryx buildshares no longer ends a sentence at a period inside quotes, so a description quoting a date such as "2. Nov. 2026" reads whole there too.- When
astryx template <name> <path>refuses the destination of a Core template that no integration replaces, outside the project (an absolute path, or one that leaves it through..), it also names the command that writes that same destination: a change to the nearest folder of it that exists, then the template command with the path from there, printed with the CLI invocation for that folder. When--overwritewas given, that command and the scratch-copy command keep it, so they do not refuse a second time; the suggested place inside the project is another file and never gets it. A..path used to get the refusal with no command to run; it now gets the same commands as an absolute one. A..path that lands in the system temp folder is still not a scratch copy; the refusal names its absolute path, which takes one. astryx template <name> <path>writes a scratch copy to an absolute path in the system temp folder (os.tmpdir(), or/tmpon a POSIX system), such as/tmp/dashboard, instead of refusing it. The receipt names the folder by its whole path (data.outputDirin--json), and the checks of a write in the project apply: no link carries the copy out of the temp folder, and an existing file is replaced only with--overwrite. A temp folder that is a disk's root or holds the home folder is not used. Any other path outside the project is still refused withERR_PATH_TRAVERSAL.theme addandtheme usewire a theme with one color mode in that mode. When a theme's built module exportscolorModes(["light"]or["dark"];theme buildwrites it when the theme source exports it), thetheme.appreceipt gives that theme amodefield and the generated theme module lists it in athemeModesexport. The first import's wiring passesmode={themeModes[defaultThemeSlug] ?? 'system'}to[Theme](/components/Theme), so the selected theme shows its own mode and a theme with both modes follows the system. When a latertheme addortheme usefirst addsthemeModesto an app that is already wired, the receipt markschange.wireModesand prints the wiring line to use. Once the module has exportedthemeModes, it keeps the export (empty when no theme has one mode), so the wiring keeps compiling aftertheme remove. The mode is read from the file that declares the theme, so a theme module that re-exports the built module (whole or by name) carries it. A project whose themes all have both modes gets the same receipt, module and wiring as before.astryx theme addwith a shared theme follows an integration's install guidance: in a project whose integration says how it adds packages, the command installs nothing with the package manager and names that line for the Astryx base packages and any others the theme imports (data.copy.installGuidance).astryx theme addinstalls a theme someone shared in one command: give it the theme's folder, a.tgzarchive of it, or an https URL to a.tgzinstead of a slug. It checks that the one theme folder it finds is a complete, built theme, copies it into the app's local themes root (src/themes/<name>), installs the Astryx packages the theme imports that the app lacks (its base theme package) with the app's package manager and install scripts off, and records the theme as the app's default, so an app wired to the generated module shows it at once. Nothing of the theme runs during the add. Any other package the theme imports is named with its install command, never installed. The result lists every file written and the record and dependency changed. It never replaces a file it did not write, and adding the same shared theme again replaces its own unchanged copy.theme removeundoes the add: it deletes the files the add wrote (keeping any you changed) and uninstalls the packages it installed.theme add <slug>is unchanged; the JSON gainsdata.copy, and a remove's gainsdata.undo.astryx theme build --family: the family's root may extend a theme the family does not select, such as an installed theme package. Its CSS and export carry that base as the root's standalone build does, and the module imports the package for the icons it inherits. That package is a requirement: the family's receipt names it (base) and its text output says which package it requires, and a build fails naming the package and the theme when it is not installed or does not export the base, never building the root without it. A member whose own base is not selected is refused naming that base, and a local base the family does not select that supplies icons is refused naming the base to select.astryx theme buildwarns about a component setting of a theme's page rules that the browser does not show as written, for each setting a key of the theme's own file (or a local theme it extends) writes, also through a call, a const or a spread; settings a helper function builds or a module the theme imports writes, its onDark and onLight surfaces and its adaptation rules are not read. It names one a later shorthand resets (aborderafter the block's ownborderTopColor, or a second key that builds the same rule), one a more specific rule of the theme it extends beats on a variant, and one whose order against such a rule (or the theme's own variant of it) decides what shows where both hold. A rule for a runtime state alone (:hover,selected) is the look of that state and never counts. Each warning names the setting's line, the rule that wins and the change that makes it show, and the receipt lists them insettingIssues. The output is the same as before.astryx theme listnames, for each theme, the owner the app imports it from and whether that owner is installed (owner,installed). The CLI ships a bundled theme's descriptor and source (fortheme eject), not the built output the app imports:theme addrecords and the app imports that from the theme's own package (such as@astryxdesign/theme-neutral), and refuses to add it until that package is installed; the list now says so instead of naming only the CLI. Existing fields are unchanged.- The Theming section of
astryx component <Name>(and of an integration component read throughastryx discover <package>/<Component>) prints itsdefineThemeoverride example, and its standard-CSS example, on one line each instead of a multi-line code block. The same keys and comments appear;--jsonis unchanged. astryx theme removecan remove the only added theme. Before, it refused and said to add another theme and make it the default first, so removing a theme left the app on a theme nobody chose. Now it deletes the generated theme module when the module is exactly what the CLI wrote, and prints the module import and the[Theme](/components/Theme)wrapper the app root must drop. A module with changes the CLI did not write stays, and the command says how to finish by hand. Removing the default while other themes are added still asks fortheme usefirst. In--json, thetheme.appresult of that removal has no themes, an emptydefault, andchange.moduleRemoved: true(andchange.themeModes: truewhen the deleted module exportedthemeModes).astryx theme templatelists the'@light'and'@dark'block form among a component's style keys, with a commented example: a block that applies only in that color mode.astryx upgrade --applyrefreshes the Astryx skill in every placeastryx init --tosaved (astryx.configskills.to), under init's rules: the two copies of the project skills folders are written together or not at all, an edited file is kept, and nothing is written through a folder linked out of the project. The dry run names each file it would write. An Astryx block is still refreshed wherever it is, and a project that keeps its Astryx guidance only as a skill is no longer told to add it.astryx doctoradds askill-placescheck: it passes when each saved skill file matches this release, and warns when one is missing or stale, when the two copies of a place differ, when the block and a project skill copy (in the project skills folders or a saved project folder) are both there without both being saved, or when a project skill is namedastryx. Doctor'scomputer-agent-textcheck names the folders outside a project thatinit --tosaved. Inside a project,astryx init --tonaming only places outside it (user, or folders outside the project) with no feature beyond the agent docs is answered by the copy that started the run, as--useris.astryx upgrade --listprints each codemod on one line, its name and title, under its version, with(optional)on the codemods that run only on request and the package named once when every codemod shares it, instead of a five-line record per codemod. The list now grows by one line per new codemod, plus a heading when a codemod starts a new version.--jsonis unchanged.
Fixes
astryx addrefuses a named pipe or a device where it writes a file, never opening it.- The note for an Apple interface face offers its generic once (
system-ui, sans-serif), and a font name such asconstructoris no Apple face.astryx doctornames the package that loads a family a theme's font stylesheet lacks when it is an open font it knows (npm install @fontsource/inter), then the command that writes the stylesheet again; for a self-hosted family (such asAcme Sans) it gives the step to add the font stylesheet export or a local<slug>.fonts.css. astryx theme buildwarns, andastryx experimental themerefuses, a radius scale with nobaseormultiplier, or one Core cannot read as a number (a boolean is read as 1 or 0, so it builds). Core builds every scaled corner from it as NaNpx, which the browser drops. A radius of0or''is said too: Core skips it and builds no corner token, so the base theme's corners stay (radius: {base: 0, multiplier: 1}squares them). In the editor:- A family typed alone that the base theme already uses keeps the base's own fallbacks (Fraunces keeps Georgia and serif).
- Any other family typed alone gets fallbacks of the kind its name says (a Serif name serif ones, a Mono or Code name monospace ones), as the open fonts do.
- A family the base's font stylesheet loads is no longer also named as a font no package loads.
astryx theme buildandastryx experimental themejudge the shape of a typography block by what Core reads:- a type scale with no base or ratio, or one that is no block, which builds every size as NaNrem;
- a role or a typography given as a plain value, which builds nothing;
- a heading
weightsthat is no block of levels, which Core reads letter by letter; - one heading level written twice (
'01'and1), where Core keeps one.
Without a type scale, any role weight gets the no-scale reason, and an empty weight is named as skipped. A boxed value is judged as its primitive, a signed number weight (-100) is read as written, and a plain-object theme is judged on the values it loads.astryx theme buildwarns, at its line, a typography value Core builds into something no browser uses, asastryx experimental themerefuses it: a font stack with a space in onefamily(Core quotes it whole), a quoted family name with a space, a role weight with no type scale, and aweightsentry that is no heading level. Both judge a family by what Core writes, so a quoted name without a space ('"Lato"') and a list without one ('Lato,serif'), which build as written, are taken. On the font dial, a weight number in any form CSS reads (Inter +500,Inter 1e3) after a known family, or a weight or style word before it (700 Inter,bold Inter), is that weight or style, never saved as a family of that name.astryx theme buildwarns a typography value wherever the theme writes it (a const, a role const, a spread, an import, a value computed at run time), at the line that writes it when one does; a role weight that is no font weight ('semi-bold','1200'), which the browser drops; and a heading weight under a number key that is no level ({7: '800'}). Both the build andastryx experimental themeread a heading level as Core does, so'01'and'1.0'are level 1. On the font dial, a weight or style word after a name that starts with a family the editor knows (Inter Tight Bold) is read as a number there is: a weight where a family goes.astryx theme buildandastryx experimental themename a typography weight given as a number (weight: 600) as a type mismatch: the field takes the text'600'. The message says Core still writes a weight from 1 to 1000, and offers the text form.- Two example blocks no longer cause a hydration mismatch:
TimestampAutoFormatandTimestampRelativeFormatread the clock once per mount after hydration instead of during render; the server markup shows a fixed placeholder date until hydration. Six example blocks that show several breadcrumbs, outlines, paginations or side navigations side by side now give each one its own accessible name, so screen readers can tell the landmarks apart. No visual change after hydration. - Six chat example blocks (the full-featured composer, the composer drawer with progress, the message bubble with custom content and with metadata, and the message metadata footer and showcase): Copy now copies the message and says so; Retry, the thumbs, Mention, Attach and the report card show a short demo note instead of doing nothing. Other chat examples are unchanged.
- Layout header and footer, card and empty state example blocks: their action buttons show a short demo note instead of doing nothing. The general Layout example blocks are not part of this change.
- The CommandPaletteGroup basic block, both CommandPaletteList blocks and the DropdownMenuGroup showcase: picking an item shows a short demo note instead of doing nothing. Other command palette and dropdown menu examples are unchanged.
- Five nav example blocks (TopNav showcase, centered navigation, enterprise dashboard and mega menu; SideNav with a header menu): Search, Notifications and Profile show a short demo note, and Sign in, Get started, Upgrade and the header-menu side nav's items are links. Other top and side nav examples are unchanged.
- Nine example blocks (Toolbar card header, sizes and three slots; Selector and MultiSelector ghost toolbars; Selector option descriptions; Table bulk actions; TabList tabs with actions; Popover hook usage): their action buttons show a short demo note instead of doing nothing, and the three-slot toolbar's Back arrow mirrors in right-to-left. The three-slot toolbar's Back still does nothing on press; the bulk-actions Delete and Archive, and controls in other blocks (such as the toolbar-with-tabs New item), are unchanged.
astryx build's block picker counts every block its doc-side word weights were fitted with as known, so those blocks no longer get the head start the picker gives blocks it has never seen.- The heading truncation, bottom sheet menu, step content, step indicator, step states and grid focus examples lay out with HStack and VStack instead of hand-written flex wrappers, so their gaps follow the theme's spacing steps. They look the same in the default theme; themes with roomier spacing show wider gaps.
astryx buildranks blocks also by single words a block's docs use that its fitted word weights do not know (such as a newer Core block's own terms), so a request that uses those words can tie to that block.astryx buildcalls page or app shell with a refit word table and new blend numbers. The weights file stores that table once: the pick model reads the call model's tables when it carries none of its own.astryx buildstarts from a family's frame template when the frame holds the page the idea names. "Notification settings in a modal" now starts from the settings dialog template instead of the plain settings page; a modal that holds only a part ("a toggle in a modal on the settings page") keeps the settings page.astryx buildtreats a frame as evidence for a page template only when the frame holds that template's kind of page. "Saved drafts in a modal with resume and delete row actions" asks for a list of drafts in a modal, not a settings page, so it no longer starts from the settings dialog; it starts from the app shell, with the parts listed in the kit.astryx buildno longer starts a part, a change to an existing page, or a page it would put on the app shell from a template kept off the template gallery. The theme showcase, a page of sample product screens, was taken as the app shell; those requests now start from a real shell template.astryx buildreads a request that opens with "add" and says where the piece goes ("add a filter row above the table") as a change to a page the builder already has, so it starts from the app shell. "Add a dashboard to the app" and "add a new dashboard" still start from a page template.astryx buildkeeps "a side panel with an owner, a status, and a history" as one part that starts from the app shell, and reads "a list of planning jobs" as a page. Component categories now declare the page-template family whose records their components hold.astryx buildstarts a part from a page family's base template only when that template leads the ranking and the family is where the part goes. A part request headed by a word that also names a component, such as "a table filter chip", asks for that piece and starts from the app shell.astryx buildwith no query now names the exact theme wiringtheme addprints for your project: the imports and the value<[Theme](/components/Theme)>takes (themes[defaultThemeSlug]from the generatedastryx-themesmodule), the color mode for a theme with one, or the provider to pass it to when an installed package declares one. Before a theme is added, it reads the installed theme's built module the waytheme adddoes, so the wiring it names is the onetheme addthen prints. When no theme is added yet, a last step gives thetheme add <slug>command for your installed theme or the starter theme. The old rule left the value open (theme={...}), so pages often passed a theme name such as"light"and crashed once script ran.astryx buildnames a page template that is not ready only when the idea names it, as a reason ("incident-consoleisn't ready yet, so build started fromshell-top-nav."); otherwise no not-ready template appears in its output, includingpagesand the "Keyword search matched" line.astryx buildchooses its start from ready page templates only: a template that is not ready yet, however well its words match, is no longer search's direct match for build and no longer keeps an idea on the app shell.astryx buildreads search as if every page template that is not ready yet were absent: search leaves such templates out of what it ranks for build, so the start, the page list, the block suggestions, the components andmatchCountare exactly what they would be without them. A not-ready template's name typed as the idea no longer empties the kit. When the idea names a not-ready template that search matches directly, the reason still says it is not ready yet.astryx searchstill lists every template.astryx buildnames where its start and each alternative go in the project it runs in, so the scaffold command runs as printed: the pathastryx templatenames for that template from the project's layout and the template's own id (not the Core id an integration replacement stands in for): in a Next app, its App Router folder (app/<name>orsrc/app/<name>) or, with only the Pages Router, the page filepages/<name>.tsxorsrc/pages/<name>.tsx; elsesrc/pages/<name>. The path is quoted when a shell would read it otherwise. In a folder with no package.json, the command keeps the<path>placeholder.astryx buildsettles an exact ranker tie by whether a template is its family's base, instead of by how many hyphen-separated parts its id has: a family's base keeps its place ahead of a tied variant. Templates still tied, in the same family or not, are ordered by how strongly each one's own descriptor answers the idea, then by how typical of its family it is, then by name. A template the idea names by its whole name wins a tie. The page-pick model settles an exact tie of its final score the same way, and its rank features give equal values equal ranks, so the order of the weights file never decides.- When page templates of one family tie exactly and the ranker's pick is one the word tables do not list (such as the collapsible and comparison tables, or an integration's template),
astryx buildstarts from the tied template whose own description, keywords and page components best match the idea, then the one most typical of its family, instead of the alphabetically first. - When
astryx build's ranker picks a template the word tables don't list, it now weighs that template against the pick model's best listed page, the same model that chooses the page everywhere else, instead of against the call model's. - A page template that is not ready yet no longer takes one of the places in the search results
astryx buildreads, so it no longer pushes a page, a block suggestion or a component out of build's kit;matchCountstill counts it. When the idea names a not-ready template, the reason still says so even if another not-ready template ranks above it. astryx build: a page template named the way code writes it (CheckoutWizard,kanbanBoard) starts that template, as its plain words do, and so does a name with two neighbouring letters swapped in a word of six or more letters (dashbaord). Shorter words are read as written.- A long-running CLI process reads a family doc or a theme or icon descriptor again when npm replaces it with a file of the same size and modification time, and reads the theme part data cache again when it is rewritten in place with the same size and modification time.
- The
canvas-editortemplate draws the corner radius field with the one-rounded-corner icon and the per-corner button with the four-corner icon, and declares each icon with the meaning its picture shows, so a project whose icon set reaches these Lucide icons through reviewed matches also gets the right picture on each control. - The canvas-editor page template fits a phone. When 40% is too wide for the canvas, the artboard opens at the largest zoom step that fits, the tab strip keeps the open tab's close reachable, and the save note leaves the screen when the header is too narrow for it (a screen reader still reads it).
- The
canvas-editortemplate's flip buttons draw the mirror axis of their action: Flip horizontally shows the vertical axis and Flip vertically the horizontal one. Before, each button showed the other's picture. Each button keeps its meaning, so icon sets that map the flip meanings draw the same icons as before. A main icon set that wrapslucide-reactand names no variant keeps the template's Lucide imports, so it now shows the corrected pictures too. - The checkout wizard template fits a 320 px phone again: the order summary, the step strip, the promo code row and the Continue buttons stay inside the page's side padding instead of running about 18 px into it, and the promo code's Apply button keeps its full label while the field gives up the room. Wider screens look the same.
- The bundled chocolate theme's light category text reads at 4.5:1 on a card.
- The bundled gothic theme template matches the gothic error-toast fix.
- The bundled matcha theme's dark menus, popovers and muted fills take its near-black neutral like its cards.
- The official themes that
astryx theme ejectscaffolds carry the theme packages' text contrast fixes: text, links, category and status text, and code text meet WCAG AA (4.5:1) on the surfaces the theme packages now check. - The neutral and y2k themes that
astryx theme ejectscaffolds show Skeleton placeholders on their light page: their--color-skeletontakes a darker neutral stop, as the theme packages do. - When Node already uses a compile cache (
NODE_COMPILE_CACHE), the CLI leaves it as it is and no longer makes an emptynode-compile-cache-<uid>folder in the temp folder. - The contact-form template no longer scrolls sideways on a phone. Its section takes the full width up to 800px instead of its content's width, so a long field placeholder no longer sets the page's minimum width. On its own, the page looks the same at 768px and wider. Inside a padded layout region narrower than 800px, the section now stays within the padding where it used to run into it.
- CLI errors name a run to try. An option a command does not take now names the options the command takes, and the command as meant when the option points at one of them:
component [Table](/components/Table) --format jsonnamescomponent [Table](/components/Table) --json,--fullnames--detail full,--props-onlynames--props, andtheme --listnamestheme list. A word the CLI has no command for names the command the words point at: a whole command passed as one word, a command's plural, an option some commands take (listnamescomponent --list), a command deeper in the tree (verifynamesintegration verify;ejectnamestheme eject --help, since it needs a theme), or a name another command reads (info [Text](/components/Text)namescomponent [Text](/components/Text)); with no such command, it names near command names by Commander's own rule (at most three edits, and more than 40% of the name the same), soinfo [Text](/components/Text)namescomponent [Text](/components/Text)where it used to nameinit.doctorgiven a path namesdoctor --built <path>, and several paths in the project name the folder that holds them.upgrade --from <version> --listnamesupgrade --listand the migration from that version,templatewith--skeletonor--listand other words names each run alone, and an option given without its value prints the command's usage with that option in it. Every named run parses, and a call that does not itself name theexperimentalgroup gets no experimental command in its answer. A word that names no command followed by an unknown option (astryx describe [Table](/components/Table) --format json) now reportsERR_UNKNOWN_COMMAND, as the same call without the option does, instead ofERR_INVALID_OPTION; every other error code, and every exit code, is unchanged. - A theme module that throws from a microtask while it loads is a refused theme load (
ERR_THEME_LOAD, naming the error) on every supported Node. Before, Node before 24 answeredERR_UNKNOWN, and a theme loaded through the CLI's own Core (no Core in its folder, and each member of a--familybuild) could build with the exception dropped.astryx theme buildand the theme editor still need Node 22.15 or later, or 23.5 or later, to load a theme that imports a stylesheet or an asset, and so does a recorded theme that imports an asset, or a stylesheet that a module in another folder imports by a relative path. On an older Node those loads are now refused with a message that names the file and the Node versions that load it, and says that nothing was written, in place of Node's "Unknown file extension" or "Unexpected token" error. A recorded theme's other stylesheets still load there. astryx theme palette generaterefuses a palette config made with a newer Astryx CLI, whose recipe this CLI does not know yet, with the recipe it uses, the recipes this CLI knows, and the update step that fits where the CLI runs. The refusal keeps its error code.- The Order Detail template writes the discount with a true minus sign held to its amount (
− $15.00), not an en dash and a space that a narrow row could break between. - A long answer piped to a slow reader arrives whole. When a command ended in an error with an answer longer than 64 KiB, such as
astryx template <name> --jsonwith many suggestions, a reader like$(…)or| (sleep 1; wc -c)got only the first 64 KiB, so--jsoncallers got invalid JSON. Every command now writes piped output in full before it exits; short answers are as fast as before. - On a phone, the payment-form template's order summary keeps each price inside its card. An item's name and badge wrap onto two lines, and when even that does not fit beside the price, the price moves under them at the end of the line. Desktop is unchanged.
- The CLI orders names the same way on every machine. Build, search, discovery and the CLI's lists (such as
astryx component --list) broke ties with the host's locale, so a machine set to another language could pick a different template or print lists in a different order. They now use one fixed text order, and a lint rule keeps locale-dependent comparisons out of the CLI. astryx componentandastryx discover <package>/<Component>print the commands a component doc writes (with a{@command …}token, a{@link …}, or a bareastryx …code span) with the project's command, asastryx docsdoes, instead of a bareastryx …that may not run in the project.--jsonkeeps the bare command.astryx component [VStack](/components/VStack) --detail fullandastryx component [HStack](/components/HStack) --detail fullprint the props list once, under Props, instead of again under Components. The JSON is unchanged.astryx component <hook>prints the hook's parameters, whichastryx hook <hook>also prints: one line each in the default answer (name, type, default, required, and the description's first sentence) and the whole table at--detail full. The JSON is unchanged.astryx component <hook>prints what the hook returns, asastryx hook <hook>does: a Returns section at the default and full detail, and the returned fields in the brief signature. The JSON is unchanged.astryx component <name>no longer opens a component through one of its keywords. A keyword is a word to find a component by, not another name for it. A name that is clearly one component's keyword now gives the usual not-found error, with that component as the first suggestion. Exact names, names in another case, and file names open as before. The component doc type and the single-component authoring guide now define keywords the same way, and the guide has a section on choosing them.astryx component <Name>names a family's sub-components that have their own doc on one line, with the command that reads each, instead of a heading and a "see" line per sub-component. A sub-component with its own description or props keeps its section.astryx component <Name>with a name that is not a component now suggests the components of your project's integrations, not only Core's. A typo of an integration component's name (ZorbletCrdforZorbletCard), or its name without its package's prefix, gets that component as a suggestion, matched by the same rule as a Core component: name, keywords and description. Two adjacent letters swapped in a name (Butotn) now count as one slip, as a one-letter typo does, and so does one slip in a name typed as words (hover cradorhover-crdfor[HoverCard](/components/HoverCard)): that name comes before a component that only has the words as a keyword. A component whose name is part of the typed name now comes before a component that only has one of the typed words as a keyword, from any package (MetricCardsuggests Card, not InfoTip). Among names that hold every typed word, the one with the fewest extra words comes first (timelists TimeInput before Timestamp). Only a Core component still resolves by a close match, and the suggestion count rules are unchanged.astryx component tag-listno longer opens OverflowList: the name is also one slip from TabList, so the lookup lists OverflowList first, then TabList.- The computer-level agent text adds Astryx to a new project, or to an existing app only when the user asks for Astryx; an existing app that doesn't use Astryx keeps its current UI stack. Before, it told agents to add Astryx to any project without it, so an agent asked for one page in a plain React app could rewrite the app with Astryx.
- An option that answers a question in other tools (
--yes,-y,--assume-yes,--non-interactive,--no-interactive,--no-input) now gets a direct answer: no Astryx command asks a question, so the error says the option is not needed and names the same command without it (Run: npx astryx init). Onupgrade, which writes only with--apply, it names the--applyrun first and the preview run second (a--listrun keeps the plain answer). Before,astryx init --yeslisted init's options and pointed atinit --help, so an agent spent a step reading help before it ran plaininit. - Two content page templates now ask for confirmation before a destructive action: Refund on the detail page and Delete in each attachment's menu on the work item page. After you confirm, a demo message says what would happen; Cancel does nothing.
- The order detail, work item detail and component documentation page templates read correctly when they are shared as a file that runs no script. Their first paint is the narrow layout at every width, instead of a desktop side rail that squeezed the page into a narrow column on a phone; once script runs, wide screens still get the side rail. On a narrow screen the order and work item details now follow the main column instead of opening in a full-screen dialog, and the component documentation's section links stay on top as links instead of a picker.
doctor's fix for a missing Core, andtheme build's hint to install Core, now name Core at the same release as the theme hints. That is the Core release the project already names, in its dependencies or peer dependencies, or, when it names no Core at all, the release of the CLI that answers. Before, they named the newest Core. A project that followed both hints could get a Core that its theme's exact Core peer does not accept.- In dark mode, secondary text on a neutral fill (an unselected SegmentedControl label, AvatarGroup's "+N" count) now meets 4.5:1 contrast on the default surface and on a Card. The default dark
--color-text-secondaryis a little lighter:#B0B5BB, was#AAAFB5. - The dashboard page templates give screen readers clearer structure: each page marks its content area (
[LayoutContent](/components/LayoutContent)) as the main landmark, has exactly one level-1 heading, and has a heading outline with no skipped levels (set withaccessibilityLevel, so the look is unchanged).dashboardgains a visually hidden "Dashboard" title, anddashboard-comparison's decorative sparklines no longer take keyboard focus inside hidden content. No visual change. - Controls that did nothing in six dashboard page templates now respond with a demo message that says what would happen: Reload and both View more buttons on the analytics dashboard, Export on the comparison, scorecard and funnel dashboards, Export status on the program dashboard, and View more on the portfolio dashboard.
astryx component <name>keeps a suggested component whose keywords or synonyms are the typed name ahead of another command's hint for a near spelling, and leaves the hint out when such components fill the list (astryx component Comboboxlists Typeahead, Selector and Tokenizer, notastryx hook [useCombobox](/components/useCombobox)).- The text wrapping, word break, truncation, heading truncation, overflow list, context menu, bottom sheet menu and direction hook examples draw their demo frames and targets with theme colors instead of fixed grays, so they follow the app's theme and dark mode.
astryx discovernames an installed integration's docs the wayastryx docsopens them: a doc that adds sections to a topic by that topic's name, and a guide by its route. It listed each doc by the name on its file, so a doc such as a theme package's guide, which adds its sections totheme, printed a nameastryx docsdid not know.astryx discover <package>/<set>names an icon set's default look by its variant in text (default: outline) instead of printing[object Object], and leaves the line out when the default names no variant.astryx experimental icon --listno longer prints an emptydefault:line for such a default. The JSON is unchanged.- A section an integration adds to a topic, or to a guide by its route, now stays when another integration, configured later, replaces that topic or guide: whether it showed used to depend on configured order alone. A topic read also names, at its top, the sections other packages add to it, since an added section joins the end of a topic that can be long.
astryx docsnow names Core, the CLI, and the packages Astryx releases with Core such as themes, at the Core release your project uses, astheme addanddoctordo. In a project that pins Core 0.7.10, the step to add a theme showsnpm install -E @astryxdesign/theme-neutral@0.7.10. Before, it named no version, so npm picked the newest theme, which needs a newer Core than the project has, and the install failed. In a folder with no Core, on the docs site's pages, and in a step that first moves to another folder, the commands still name the packages with no version. The docs site's MCP endpoint names the Core release it documents.- Two packages that add a section with one title to the same docs topic or guide both keep it. Across packages, a section replaces another only when one carries an authored
idthat is the other's key or a title query the other's title answers. When one package's section holds the key another package's later section derives from its title, the later one is read by a key that starts with its package's provider id (its package name unless it sets one), such asacme-dune-theme-install, soastryx docs,--index, namespace reads and search show both. This includes titles that differ only in letter case: the later of two packages'InstallandINSTALLwas read asinstall-2and is now read by its provider key. Every other key collision keeps its numeric suffix. Sections of the topic itself still take a replacement from any package, the last configured winning. - The documentation page templates fit a phone: the overview page's hero gives its title the card's width, so in the default theme the title no longer breaks inside a word, and the design page's example actions and button previews wrap instead of running past their card. Wide screens look the same as before.
- The stored docs routes, and so the build id, are the same on every machine that packs the same files. How the machine's Node resolves module imports no longer changes which folders the stored routes list.
- The technical documentation page template's "Next steps" items wrap on a narrow screen instead of cutting off after one line, so a phone reader sees each item in full. Wide screens are unchanged.
- The technical documentation page template reads correctly when it is shared as a file that runs no script. Its first paint is one column with the section links on top at every width, instead of a desktop side rail that squeezed the article into a narrow column on a phone; once script runs, wide screens still get the side rail. Copy buttons appear only once the page runs, so a static copy shows no buttons that do nothing. On a phone the section links stay on top as links instead of a picker.
astryx docs <topic>opens a page typed in another spelling of its route: spaces, hyphens, slashes, dots and underscores all separate words, and word order does not count (docs tokens.tokens-coloropenstokens/tokens-color). When the typed words only name a page and no other command's entry matches, the miss suggests the pages whose title or declared keywords carry them, closest first (docs themingsuggests the Theming topic first), keeps a route the typed words name first, and never lists more than before; a namespace's children are ordered the same way.astryx docswith a mistyped topic or namespace (tokns,colr) now lists the one a slip or two away first, ahead of the other topics and namespaces.astryx theme buildandastryx doctorno longer offer to install a package named after a project folder, such assrc, for an import the project'sbaseUrlmaps to a TypeScript file written with a.jsextension (src/rows.jsforsrc/rows.ts). They now read such an import as the project's own file, as TypeScript does.- Outside a project,
astryx doctornow warns about an integration installed for the computer that has issues in its own files, and names them. Before, commands such asastryx searchandastryx discoverwarned about the integration and said to runastryx doctor, butdoctorpassed and named no issue. Issues that need a comparison with Core components are still not named there, becausedoctorreads no Core outside a project. doctornow says when an app does not load Core's component styles,@astryxdesign/core/astryx.css. In an app that uses Core's prebuilt styles, components render unstyled without them. Before, nothing caught it: the build,doctoranddoctor --builtall passed. Plaindoctorwarns when no project stylesheet or module imports them and no page links them.doctor --builtwarns when the output uses Astryx but no built stylesheet or page carries them. An app that compiles Core's styles from source with@astryxdesign/buildis not checked.astryx doctorno longer reports a theme as wired because a theme source or a generated theme file imports it: the theme editor's settings module, a theme build's output, or a theme source that imports a package theme only to extend it. Before, an editor theme built on an installed theme package (--like <theme>) turned the "no theme appears wired" warning into a pass while the app rendered no theme; now only the app's own imports of a theme, or a theme it passes to[Theme](/components/Theme), count.astryx doctor's theme font check now accepts a Google Fonts or Bunny Fonts stylesheet<link>in the app's page head as loading the families it names: inindex.html,public/index.html,src/index.html, or a Next.js root layout or_document(.tsx,.jsx,.js,.mjsor.ts, underapp/,pages/orsrc/). An app that loads a theme's fonts that way no longer gets the warning. A link inside a comment, one whoserelis notstylesheet, or one from another host does not count. When a package theme ships no font stylesheet, the fix names the page file whose<head>the link goes in.doctor's theme font check now counts a family as loaded when afamilyparameter of a font service URL in the theme's font stylesheet names it. The Google Fonts import in every Astryx theme's font stylesheet does this. Before, an app set up correctly with the neutral theme got a warning it could not act on: "External font imports prevent proof for neutral: Figtree." A family that nofamilyparameter names still gets that warning, as does a font service URL that names its families another way.doctor's theme font check now counts a family as loaded when any font stylesheet that the generated theme module imports loads it. A local theme built on neutral, such as one whose source extends neutral or a copy thattheme ejectmakes, names neutral's fonts but ships no font stylesheet of its own. Before,doctorwarned "Added themes name font families but import no font stylesheet (<theme>: Figtree (font stylesheet is not imported))", even when the app also added neutral and the module imported neutral's font stylesheet. A family that no imported font stylesheet loads still gets that warning.- With no update check recorded,
astryx doctor'snewest-releasecheck no longer says the check runs once a day after a command, which is true only for a copy installed for the computer. It now says that only that copy checks, that a project's own copy changes only when the project upgrades it, and that a tool that runs its own copy chooses its release. astryx doctor integration <check> <package>run in the folder of that package now says the package is the one in this folder, not one the project installs, and namesastryx integration checkfor checking the package you are making. Before, it said only that the package was not installed and to install it first.astryx doctor --built's purity check no longer flags the stylesheets the app's registered themes load. It reads them from the theme module the CLI writes (theme addand the theme editor), so an editor-made theme starts with no "imports the stylesheet" findings. Any other stylesheet import is still flagged.astryx doctor --builtno longer flags the setup stylesheet as page styling. A stylesheet that only imports Astryx packages' CSS (reset.css,astryx.css, a theme's CSS), as the getting-started steps write it, is read as wiring. A stylesheet with rules of its own, or an import from another package, is still flagged.astryx doctorno longer fails its private theme variables check in a Yarn Plug'n'Play project. For a built-in theme that the app installs as a package, the check now reads that package's own theme source, which is the copy the app uses, instead of the CLI's copy, whose icon import Yarn refuses to resolve.doctor's private theme variables check now loads each theme input with the Core the project installed when the CLI is installed for the computer. Before, in an app with Core and a theme package but no CLI in the project, the check failed for every theme input that imports@astryxdesign/core, as every Astryx theme package does. That CLI has no Core of its own: "Added theme inputs set private --_* variables directly (…: input could not be inspected …)". When the project's Core isn't installed yet, as in a fresh clone, the check now says that it did not inspect the theme inputs. Before, it failed for each input that imports@astryxdesign/core.- The editor template's transactions table keeps names readable on a phone. Each column now has a floor (name 180px, date and amount 120px, actions 60px), and its share of the width matches that floor. The table needs at least 480px; in anything narrower, such as a phone, it scrolls sideways instead of squeezing names to a letter or two per line. Desktop windows that give the table 480px or more do not scroll; the name column takes a larger share and the actions column a smaller one.
- In a project that pins
@astryxdesign/coreto one version, as Astryx starters do, the commands the CLI prints to add or upgrade Astryx packages (the once-a-day hint,doctor's fixes, the setup reminder, and the upgrade notice) save the new versions exactly too, such asnpm install -E @astryxdesign/cli@0.7.16. Before, with npm, following them replaced the project's exact pins with ranges such as^0.7.16, so a later install could bring a CLI from another release than the project's Core. - A run that prints its answer and then exits 1 records the code that answer carries in its debug event, as an error that
cliErrorprints does. A component batch with a selector that does not resolve records the first unresolved row's code (such asERR_UNKNOWN_COMPONENT);theme build --checkthat finds stale outputs recordsERR_THEME_STALE;upgraderecords the code of an error it reports in text mode, and theerrorCodeof a run that stops incomplete (such asERR_CODEMOD_PROTECTED), in text and in--json;initthat refuses its agent-docs path recordsERR_PATH_TRAVERSAL. Each code is recorded once the answer is printed, so an error that stops the answer first (a recorded theme that does not load) keeps its own code. Adebughandler saw these runs asERR_UNCLASSIFIED_EXIT. Output and exit codes are unchanged. astryx theme use <theme>opens its receipt with the default it set: "[ok] <theme> is now the app's default theme: themes[defaultThemeSlug] is <theme>.", or "[ok] <theme> was already the app's default theme; nothing changed." when it was the default already. The receipt's fields are unchanged, and the JSON is unchanged.- The payment form template's Remove link on each cart line now asks for confirmation first. After you confirm, a demo message says what would happen; Cancel does nothing.
- The
form-wizard-verticaltemplate declares its review banner icon asreview, which icon sets draw asinfo, the meaning the banner shows, instead ofcheckDouble. A project whose icon set draws template icons by meaning now gets that set's info icon in the banner. A project whose main set wraps@heroicons/reactkeeps the check badge unless it picks a variant, and copies without an icon set are unchanged. - The vertical form wizard's cover buttons keep their full labels on every phone width: the dropzone column moves under the cover before "Preview on device" would be cut.
- Buttons in form page templates that did nothing now show a demo message that says what would happen: Cancel in the workspace and audiobook wizards, Create workspace and Submit for review on a finished last step, Place Order on a complete payment form, and Save on the payment form's cart line.
- In a fresh clone (a project that lists
@astryxdesign/coreand a theme package, with nothing installed yet),astryx doctornow says to install the project's dependencies, such asnpm install, for a missing Core and a missing theme package. Before, its fixes added Core with no version and the theme package at the latest release, so following them replaced the project's versions with others. - In a fresh clone whose
package.jsonlists@astryxdesign/cli, the once-a-day hint,doctor, and the setup reminder now say to install the project's dependencies (such asnpm install), not to add the CLI again. Adding it again replaced the exact version the project lists with a range, such as^0.7.10. - File protection now decodes consecutive octal escapes in quoted
.gitattributespaths as UTF-8 bytes. Before, a rule such as"caf\303\251.js" linguist-generatedwas treated as separate code points and failed to protect the matchingcafé.jsfile; quoted and literal UTF-8 spellings now classify consistently. - In a Yarn Plug'n'Play project, the
astryxcommand installed for the computer hands each run to the project's own CLI: it starts again with the project's runtime, as Yarn starts a command, instead of answering with its own release and telling you to install a CLI the project already has. Commands the CLI prints there start withyarn astryx, not with ayarn dlxdownload of the CLI. - Palette recipe
astryx-oklch-v2: a gray family's color now fades toward white the way a gray scale's does, so a colored gray (a slate[#64748](https://github.com/meta/astryx/pull/64748)b, a warm[#78716](https://github.com/meta/astryx/pull/78716)c) gives the page and the cards on it only a faint tint instead of a clearly blue or cream page; its darker shades keep their color. v1, and so every shipped palette and existing config, is unchanged. The neutral dial's help says so, and names--color-background-bodyfor a clearly tinted page. - Two page templates no longer leave an empty column on wide screens. The product gallery's header (a heading and its intro) now fills two columns instead of three, and the two-column form's contact strip fills three columns instead of four, so it sits centered. Narrower widths are unchanged.
- Grid:
columns={{minWidth}}withoutmaxno longer overflows a container narrower thanminWidth. A lone column now shrinks to the container width, as it already did withmax, so a phone no longer scrolls sideways. In a container that takes its width from its content (an inline-block, or a flex item with no width), an uncapped Grid is now as wide as its content instead ofminWidth, as a capped Grid already was. - Page template headers on a phone: when a page title and its action do not fit one row, the action moves under the title instead of squeezing it, in the service-jobs table and the grouped issues table. Wide screens look the same as before.
astryx experimental icon new-set --fromrun again on a set whose library dropped an icon now removes that icon in every look from the generated module and its declarations. Before, the filled (or other variant) export stayed behind and named a library export that no longer exists, so importing the integration package failed.- In the Tool: IDE page template, the editor's and terminal's scrollbars no longer sit under the properties panel's resize handle. On desktop the editor and terminal keep a small gap before the handle, so the whole scrollbar scrolls; before, a press on the half of the scrollbar nearest the handle resized the panel. Mobile, where the panel is hidden, is unchanged.
- The incident console page template works on a phone and its buttons act. On a narrow screen its header controls wrap onto their own rows, and choosing an incident opens its details in a bottom sheet instead of doing nothing. The inspector's next-step button ("Mark mitigated", "Resolve", "Reopen") moves the incident to its next status, and "Escalate" and "Declare incident" confirm with a demo toast that marks where to connect the real action. Rows show each incident's start date and time instead of a relative time that grew stale. The template stays unready for now.
astryx initnext steps and thedoctortheme hint name the project's own install command (pnpm add,yarn add,bun addornpm install) instead ofnpm installin every project. An install command the CLI prints no longer adds a@"*"range to a package name.astryx init's theme step now names the theme at the project's Core release, astheme addanddoctoralready do. In a project that pins Core 0.7.10, it printsnpm install -E @astryxdesign/theme-neutral@0.7.10. Before, it named no version, so npm picked the newest theme, which needs a newer Core than the project has, and the install failed.doctor's hint for an app with no theme andtheme build's hint to install a missing theme follow the same rule.astryx init --useron a skills folder you cannot write (such as a read-only~/.agents/skills) now fails withERR_WRITE_FAILEDand a message that names the path, the reason, and what to change, instead of a bareEACCESline withERR_UNKNOWN.- Nine page templates fit a 320 px phone without their content scrolling sideways, and a tenth scrolls less. Their responsive grids now pair the minimum column width with a column cap, so a column narrower than the screen shrinks to fit instead of overflowing. The inline form wizard's checkbox descriptions now wrap instead of being cut to one line. Screens up to 1920 px wide look the same as before; above about 2,380 px the library's six category cards fill their row instead of leaving an empty column.
astryx docs global/problemsnow also explains the "installing CLI release" line outside a project, where the astryx command you started downloads its own Core once. Before, the page said only that a project's own CLI could not start, and told you to install the project's dependencies.astryx integration checkandastryx doctorname a theme module thattheme buildwrote (.js,.mjsor.cjs) and that imports TypeScript source, as built themes from a CLI before this one do (built_module_imports_typescript, anextnote with the weight ofrelative_import_not_shipped), with the file, the line, and the fix.astryx integration checkandastryx doctor integration validatenow resolve every relative import of the modules a package ships the way an app's bundler does, against the files npm packs (for an installed package, its files on disk). Run in the package's own folder, they used to pass an import such as./iconsthat the tarball leaves out, because the file was on disk there. Each import no shipped file answers is arelative_import_not_shippednote markednext, naming the importing file, the import, and that the file is not in the package. It failsintegration check --strict --nextnow; the next minor release makes it a warning, which fails--strict. When npm cannot be asked, an import whose file nofilesentry can reach is still a note, and any other is listed as not checked.astryx doctor's theme owners check now also reads a package theme's stylesheets, whose@importandurl()references it never followed, and warns that the built module loads but names a file the package does not ship. Type-only imports are skipped;./iconsresolving toicons/index.jsis fine.- The kanban-board page template stacks its lanes top to bottom at the full width below 768px, so a phone shows whole lanes instead of one lane and a cut edge of the next. A swipe that starts on a card now scrolls the board; a finger lifts a card with a long press and carries it to another lane. A mouse drags as before, and the layout at 768px and wider is unchanged.
- Keyboard users can reach two template controls. The kanban board's column info icons use InfoTip, so each is a named button that Tab reaches and Enter opens, where before Tab stopped on a hidden, unnamed icon. In the side-navigation shell, a conversation's options button sits in the row's actions slot and shows while focus is in the row, so Tab reaches it; focus returns to it after its menu or delete confirmation closes, and the conversation link keeps its status in its name.
astryx integration checkandastryx integration verifyhandle very large icon libraries (tens of thousands of exports). The check scans every file of the package for contribution metadata instead of stopping after 5,000 files with a warning that failed--strict. Verify reads npm's pack list from a file, so a package of any size no longer fails withENOBUFS, and both commands keep a bounded number of parsed modules in memory, so they run in Node's default memory. An icon set that re-exports icons from its own package name (export {X} from '<own package>') is now checked through the package'sexports, as Node resolves it, instead of being listed as not checked.- The messaging shell page template, still marked not ready, now works as an app. AppShell owns its side navigation of channels and direct messages, so on a phone the channels open from the navigation toggle. Picking a direct message shows that conversation, sending a message or a thread reply adds it to the page, a message's replies open its thread (in a drawer on narrow screens), and selecting a conversation clears its unread count. The page no longer uses raw elements or a local style object, and the actions without a real destination show a demo toast.
- Card, Center, Collapsible, Divider and Blockquote examples no longer overflow a narrow column: each keeps its demo width but now shrinks to fit. Wide columns look the same.
- TextArea, TextInput, Switch, SegmentedControl and TabList examples no longer overflow a narrow column: each keeps its demo width but now shrinks to fit (and the status-variant columns wrap). Wide columns look the same.
- Layout header, footer, content and panel examples and the chat layout examples no longer overflow a narrow column: each keeps its demo width but now shrinks to fit. Wide columns look the same.
- Toolbar, TopNav (and its item, menu and mega menu examples), Table, Step and Stepper examples no longer overflow a narrow column: each keeps its demo width but now shrinks to fit, and the custom-content stepper's two side-by-side fields wrap. Wide columns look the same.
- The AspectRatio examples other than its showcase, the Avatar, AvatarStatusDot, Grid, GridSpan, the clipboard, hotkeys, streaming text and container reveal hook examples, Markdown, OverflowList, Resizable and ScrollableArea examples no longer overflow a narrow column: each keeps its demo width but now shrinks to fit (and rows of avatars wrap); the Resizable showcase's sidebar can grow to two thirds of its card, so the handle stays inside a narrow card. Wide columns look the same.
- The payment form and checkout wizard page templates no longer squeeze their form beside the order summary on a narrow screen before script runs: the summary wraps below the form instead. Wide screens look the same.
- In a project, the update notice and
doctor's matching fixes now upgrade every Astryx package the project lists that is released with Core, such as its themes, beside Core and the CLI. Before, the command upgraded only Core and the CLI, so following it left a theme on the old release; its exact Core peer no longer matched, anddoctorreported it. - The npm commands that the CLI runs for itself now use npm's own
noproxysetting. These commands install a release into the CLI's per-user cache and ask the registry for versions. Before, when the shell'sNO_PROXYnamed the npm registry but npm's own settings sent the registry through a proxy, npm went straight to the registry. Then the first command that needed the cache, such asastryx componentoutside a project, waited until npm's time limit and failed. - The payment form's promo code "Apply" button keeps its full label on a phone; the promo field gives way instead.
- Page templates keep their text on a 320 px phone. The filtered table no longer scrolls sideways on a phone, buttons in three templates (the vertical form wizard's cover, the editor and the composition dashboard) keep their full labels instead of cutting off, the work item's success criteria and the report wizard's option descriptions wrap instead of cutting off after one line, and the canvas editor's document tabs show their full name in a tooltip when a name is cut. Wide screens look the same as before.
- Theme editor pictures show responsive charts drawn: each page draws in a window of its own until it is quiet, and its script is held while the whole page is pictured, so a chart no longer starts over and is pictured empty. The page stays laid out for the 1280 × 900 window.
- The theme editor's pictures and the render stylesheet cut read a media query's condition the way the browser does:
notbefore a condition in parentheses,or, and nesting. A rule under(not ((min-width: 768px) and (min-height: 500px)))no longer counts as matching in the 1280px picture window. - The principles doc says settings groups use Section, not Card, matching the Card and Section docs.
- ProgressBar and CircularProgress fills reach 3:1 against their track (WCAG 2.2 SC 1.4.11, non-text contrast). ProgressBar's status fills take the status text colors, and its neutral fill, like CircularProgress's, takes the secondary text color instead of the disabled one, which is the bar's track color in dark mode in Theme Neutral and Theme Stone and under 3:1 on the bar's track in every bundled theme in light mode. A disabled bar takes the same fill and dims its track and fill to half opacity, as a disabled Slider or Switch track does, and a disabled ring dims as a whole, center content included, so each reads quieter than a neutral one. A mark on any fill but accent takes the surface color; in Theme Butter and Theme Stone, a mark on a status fill takes that status's on-color. CircularProgress draws every variant on the muted background track, ProgressBar's base track, because some themes' status muted colors are the status color itself. In Theme Neutral, Theme Butter and Theme Stone a dark neutral or disabled fill takes a lighter neutral stop, Butter's and Stone's status fills take the theme's status colors, Stone's accent fill takes a blue stop that reaches 3:1, and the CLI's bundled theme templates match.
astryx doctor integration componentsno longer reports a documented string union that leaves out a value the code marks@deprecatedin every place the type takes it from.- When two installed packages both declare the same provider ID in their manifests, the warning and
astryx doctor's fix now say that if they are one integration installed under two names, keep one of the two dependencies, and otherwise change one package's providerId. When a provider ID comes from a package name, the advice is unchanged. - The not-found hint refreshes its name index after an imported doc dependency changes on the minimum supported Node version.
- A stop signal sent to the CLI's own process while it installs the release matching a project's Core, such as a time limit's SIGTERM, now stops the run. Before, the run went on once npm returned, answered, and exited 0 to a caller that had already given up: npm runs synchronously, so the signal waited for the install to end, and by then its handler was gone. The handler now stays until the signal is delivered, and the hand-off lets it stop the run before it answers.
- A release that failed to install is tried again at once when npm's registry changed since the failure, instead of waiting 2 or 10 minutes, and the reason names the registry npm tried.
- Remove six page templates that were never marked ready: not-found, access-denied, error-page, welcome-portal, run-console and review-workspace. Page templates will come from the design team instead. None of them was in a release, and no command offered them as a start.
astryx experimental rendercarries the.mts,.ctsand.cjsmodules a page imports, and--reversegives them back and follows their imports. The render loaded them but left them out of the file, so the page came back withexact: falseand those modules missing. A file that carries one says render format 2, so an earlier CLI that reads render formats names the CLI that reads it instead of calling the file damaged; every other file stays format 1.astryx experimental rendercarries every image, font and media file a carried module's strings or a carried stylesheet name by a relative path inside the folder that holds the carried files, also when the page did not show it in this render: a branch the page did not take, or a stylesheet rule no element uses. Such files now ship in the rendered file, up to 8 MB each, as a shown image does; a larger one, one whose bytes are not an image, font or media file, or one it cannot read, is left out with anot-embeddedwarning that names the file that names it. A name that climbs above that folder is not the page's file and is not carried, as--reversereads it too.--reversereads the same names with the same scan, so such a page used to come back withexact: falseand those files missing.- A page render that draws overlays open waits for React's queued work before it reads them, and no longer compares the page's markup turn after turn: a page whose overlays have settled is read at once, so the theme editor's sample page and sheet render as fast as before while each render stays the same every time. The theme editor's contrast checks reuse each part's token reads within a command.
- A page render that draws overlays open (the theme editor's sample page and sheet) reads each overlay once its update has finished. Before, on a busy machine it could read an overlay between two renders, so the same theme could render to different pages:
undothen left the sample page different from before the change. astryx experimental renderoutside a project carries the modules a page imports from above its own folder, and the files those modules import, as long as they are inside the current folder. A page restored with its neighbours (report-restored/app/report/page.tsxbesidereport-restored/components/) and rendered again by the command its file prints used to leave those modules out, so the new file came back withexact: false. Where the render reads the page'stsconfig.jsonandpublic/images does not change.astryx experimental renderrenders a page outside a project whose StyleX reads Astryx theme variables (@astryxdesign/core/theme/tokens.stylex), as many templates do. Such a page stopped with "The page does not compile: Could not resolve the path to the imported file", because the StyleX compiler looked for Core beside the page, where outside a project there is none. The compiler now gets the theme file the page loads from the CLI's own Core, and the page renders the same as it does inside a project.astryx experimental renderand--reverseread a folder or file whose name begins with two dots (..x) as one inside the folder that holds it, where they took it for the folder above. A page in such a folder keeps its own folder as the root of the files it carries, so the file it writes reverses; a file above it stays out, named in anot-embeddedwarning. The note at the top of a page rendered outside a project names the page by its path among the files it lists (app/x/page.tsx), where it named only the file (page.tsx) and pointed at it as the file to edit.astryx experimental renderand--reverseread path aliases from the config TypeScript reads for the page: the nearesttsconfig.json(elsejsconfig.json) at or above it, through itsextends(a path with or without.json, a package's config, or a list, the later one winning, with${configDir}), and, behind a solution-styletsconfig.json("files": []withreferences, as Vite sets up), the referenced project that includes the page. A page whose aliases live intsconfig.app.jsonor in an extended config used to fail, withERR_FILE_NOT_FOUND, or withERR_RENDER_MISSING_DEPENDENCYwhen the alias looks like a package name (@data/rows), althoughtscand the app's build found its imports.astryx experimental render --reversefinds the embedded source in a file whose script tag a minifier or another tool rewrote: an unquotedtype(<script type=application/x-astryx-source>), or an attribute beforetype. Such a file used to come back as a page rebuilt from its markup (text and layout only) instead of the exact source.astryx experimental rendergives a relative or aliased import with?rawthe file's text, and a.cssfile imported with?inlineits text (not added to the page), as Vite does by itself, however the import names it. It used to give a JSON file's object for?raw, fail on a text file such asnotes.txt?raw, and refuse a.cssfile with?inlineas CSS Modules. A package import with?raw, and a Sass, Less or package stylesheet with?inline, stay as before. Any other query loads the file as it loads without one, as before: an image, font or media file as its address (?url,?inline,?w=400), a module as itself.--reversegives back the files the render carries; a?rawfile of a kind a render never carries, such asnotes.md, is named in anot-embeddedwarning.- On Windows,
astryx experimental renderand the experimental theme editor now transform the page's own files. The renderer read every file as outside the project, because the module loader named files with forward slashes while the project path used backslashes, so no file was transformed. A page or theme that imported a stylesheet then failed withUnknown file extension ".css", and StyleX, image and JSON imports were not handled either. astryx experimental renderand--reversewrite in one step. A render writes the HTML file under a temporary name beside it, then gives it its name, so a reader or another run never finds half a file: two renders of one page to one file both succeed, where one could be refused because the file "already exists and was not written by a render". A restore writes its new folder the same way, so restores run at the same time each get a folder of their own, also when they restore with--outinto folders under one new folder, where some were refused, and a restore stopped part-way leaves no folder behind, so the same command works again. A run stopped between its write and its rename leaves a hidden temporary file or folder, which the next run to the same place, on the same computer and in the same container or sandbox, removes once that run's process is gone. A render still never replaces an HTML file this user cannot write, and the file it replaces keeps its permission bits; it now needs to make a file in the HTML file's folder, so a folder this user cannot write is refused, and the refusal names it. Every copy a restore writes, except the page at its target, lands in the one new folder, including a copy of the page that a path alias places; such a copy outside it is refused with nothing written.- In right-to-left pages, the settings dialog's Reset buttons, the inbox's Reply action and Send button, and the tree list settings example's Documentation chevron now point the right way: these icons mean back, reply, send or go into, so they mirror. Left-to-right pages look the same.
- In right-to-left pages, the canvas editor's artboard no longer goes blank and the progress dashboard's milestone timeline no longer draws its labels over the bars: both keep a left-to-right layout, as a design canvas and a chart should (the same page's scope burndown too). Left-to-right pages look the same.
- The dashboard scorecard template's trend charts keep their y-axis labels whole with a small font up to 16 px, wide fonts included: the labels are compact and in the series' own scale ("6M" and "1.4M" for values stored in thousands, matching the heading's "4,350k") instead of 6000 and 1400, and the axis gutter is 52 px instead of 40 px. The tooltip still shows exact values.
- The dashboard scorecard template fits a phone screen: its trend charts shrink to a narrow column instead of running past the screen edge, a chart's change line moves under its title when the card is narrow, the header's generated date moves to its own line instead of squeezing into a sliver, and on the narrowest phones Export moves under the period control instead of running past the edge. Tablet and desktop layouts look the same.
- Search: a family's root now comes before a part of its own family whenever the part adds nothing the query asked for, also when the part's name scores higher.
astryx search "code sample"lists CodeBlock before Code. The part still comes first when the query is the part's exact name (astryx search code), holds a word only the part's name has, or writes the part's name of two or more words as one word, as is or misspelled (astryx search "breadcrumbitm"keeps BreadcrumbItem first). The new order changes no match, score or reason. Thesearch()doc page now describes this order, so it also matches a few of those words (such as "family" and "root"), and such a query, insearchorbuild, counts one more match. - Search: a family's root now leads a part of its own family when the part adds nothing the query asked for:
astryx search tabslists TabList before Tab. A query that holds a word only the part's name has, in any plural form, such as "item" for ListItem or "statuses" for FieldStatus, keeps the part first. Scores, reasons and match counts are unchanged; only order inside a band moves. - Search: a match whose name of two or more words the query writes as one word now comes first, also inside a longer query.
astryx search "TableSortableTable with pagination",astryx search "table-sortable-table with pagination"andastryx search "tokens-color for dark mode"list that block or doc first. Words written apart stay plain words (astryx search "multiline text input"keeps its order), and so does a one-word name such ascard. A name inside a longer name the query holds, such as a block's display name or a doc's title, does not come first. Matches, scores, reasons and counts are unchanged;buildis unchanged. astryx searchreads another entry's name as that entry's evidence. A block no longer ranks above a component only because it uses components that match the query's words. A guide whose title sits in the query no longer takes the title's rank when the query also names a component the guide does not answer: it ranks by the words it matches, so a guide whose title is its only match yields to that component. Two cases keep the guide first: a component word that is also a doc's name (link,icon,themeorcalendar), which may be asking for the docs, and a guide whose own name is a query word.buildis unchanged.- Search: when matches of one domain tie for first place on score and on the query words they matched, the one whose own name holds more of the query's words now comes first, instead of the first by name.
astryx search "side navigation sidebar"lists SideNav first. A first result that matched the whole query, as a name, keyword or title, or whose title the query holds, keeps its place:astryx search "date picker"keeps Calendar first, andastryx search "how do i generate a palette"keeps the theme authoring guide first. A part of the first result never takes its place this way. Matches, scores, reasons and counts are unchanged; only the order inside one score band moves. astryx searchreads a one-identifier query written as a component's, type's or icon's name (PascalCase, such asThemeProvider) as its words also when all it matches is text that mentions it, including a code term or table cell a doc's keywords gather. The entry that mentions it stays in the answer, beside the entries its words find. In the lexical ranking, the entry that mentions it, and an entry one of its words names outright, come before every entry its words only match; search's learned order inside a score band still applies, soastryx searchcan list a words-only match above them. A prop's name (camelCase, such asautoFocus) keeps only the entries that mention it, as before, and other queries rank exactly as before.astryx searchreads a docs namespace page at the reader's grain. A word the page's text shares with a doc beneath it, which that doc answers at least as strongly, is that doc's evidence, so a namespace page that sums up its guides no longer ranks above the components, templates, hooks and guides it summarizes. Words only the page carries, and its name, title, description and declared keywords, still match it.buildis unchanged.- Secondary text now reads on every palette tint. The default light
--color-text-secondaryis[#445564](https://github.com/meta/astryx/pull/445564)(was[#4](https://github.com/meta/astryx/pull/4)E606F), so secondary text on a gray Card or any other--color-background-<hue>tint meets 4.5:1 over the surface and the page body. The dark value is unchanged. To keep the previous light colour, a theme can set--color-text-secondarytolight-dark([#4](https://github.com/meta/astryx/pull/4)E606F, #B0B5BB). - The settings dialog template's Delete my account button now asks for confirmation first. After you confirm, a demo message says what would happen; Cancel does nothing.
- The settings and settings-sidebar page templates no longer offer nav items that lead nowhere. In settings, choosing an item other than Profile no longer moves the selection while the Profile form stays; in settings-sidebar, Notifications, Taxes, Payments and Travel for work no longer open an empty page. A nav item with a section works as before; an item without one shows a demo message and keeps the current item selected, and the current item is marked as the current page for screen readers. The first screen looks the same.
- Settings page template on a phone: the search moves under the title instead of squeezing it until "Settings" breaks mid-word.
- Controls that did nothing in two settings page templates now respond with a demo message that says what would happen: the three Save buttons on the settings page, and Professional hosting tools on the sidebar settings page. The sidebar settings page's back arrow and drill-in chevrons now point the right way in right-to-left languages.
- The setup reminder (
Next step: run … init …, shown at most once a day in a project that has not runinit) now prints on stderr before the command's own output instead of after it. Agents often keep only the start of a long answer (2>&1 | head), so a reminder at the end was cut and the day used up without anyone seeing it. It still never prints under CI, in--json, or once the project is set up; a command that fails now shows it too. - The setup reminder now says why to run
initnow: "Astryx is not set up in this project yet. Next step: runnpx astryx initnow, before you write Astryx code. It asks no questions, prints the getting-started steps, and saves the Astryx guide to AGENTS.md." Before, it saidinitwould "install the Astryx agent prompt", which agents read as a file change the user did not ask for, so they kept working without it. The command it names is unchanged, and so are the places it prints. - Delete in two shell page templates now asks for confirmation first: a conversation's menu in the side-navigation shell and a row's menu in the theme showcase. After you confirm, a demo message says what would happen; Cancel does nothing.
- When the docs catalog withdraws an integration's docs because one doc fails its checks (such as a flat topic that sets
aliases),initandupgrade --applykeep that package's skill copies until the doc loads instead of removing them as leftovers, and when any of its docs does not load, its skills get one note saying so instead of areplacesfix. astryx component Flexnames Stack first. Stack's search card now listsFlex, the name Chakra UI and Mantine use for the same row-or-column layout part, so the lookup that misses suggests Stack before Layout.- A shipped doc's stored parse is used only when the installed zod release is the one that made it. With another zod release, the CLI parses the doc, so the answer is always what a fresh parse gives.
astryx swizzlewithout Core says what to do. Outside a project, it says the folder is outside a project and that swizzle copies source into an app project that installs@astryxdesign/core; in a project that has not installed Core, it says to install it. It no longer tells you to work inside the design system's own repository. The error code staysERR_CORE_NOT_FOUND.- The dashboard, dashboard-cohort-funnel, dashboard-composition, dashboard-progress and editor page templates, and the Table in Card block, keep their look with the Table bleed fix in Core: each Table is now the card's direct child, so it still reaches the card's top or bottom edge.
- Delete in two table page templates now asks for confirmation first: the support inbox's row, conversation and bulk Delete, and Delete issue in the grouped table's row menu. After you confirm, a demo message says what would happen; Cancel does nothing.
- The table page templates give screen readers more structure: seven pages that had no main landmark now mark their content as main,
table-tree's sidebar headings follow the page heading without skipping a level, and the icon-only status and actions columns intableandtable-groupedget visually hidden header names. No visual change. astryx template <name> <path>andastryx template --cdn <path>accept an absolute path inside the project root, also through a symlinked project folder. It is written exactly as its relative path. An absolute path outside the project is still refused withERR_PATH_TRAVERSAL. Forastryx template <name> <path>, the receipt says the path was written as its relative path (data.givenPathin--json), and the refusal names a command that writes inside the project and the command that prints the source without writing anything. In a Next app whosepageExtensionsincludetsx(the default), the named path is one Next builds and serves: a page goes to the App Router folder (app/<name>, orsrc/app/<name>, inside the route group with the root layout when that folder has none of its own), or, with only the Pages Router, to the page filepages/<name>.tsx; a block goes toapp/components/<name>with a rootapp/folder,components/<name>with only a rootpages/folder, elsesrc/components/<name>. Every other project getssrc/pages/<name>andsrc/components/<name>. When that path exists or another page already serves its URL, the name becomes<name>-2,<name>-3and so on. The path is quoted in the command when a shell would read it otherwise, as with a route group folder. Next refuses to build when itsappandpagesfolders are in different folders, and when two pages serve one URL. For--cdn, the receipt is unchanged, and the refusal namesastryx template --cdn cdn.template.html.- Dashboard templates show every chart label whole: the progress timeline's "Today" label gets room above the plot, and Y axes wide enough for their widest tick no longer clip it.
- Outside a project, when a tool runs the CLI for you,
template,buildandtheme ejectno longer name an integration the tool approves and installs as a missing dependency.renderalready gives the page that integration, so the page renders without installing it. Also,rendernow takes an approved integration only from the tool's package set itself. Before, it also took one from a folder above that set. - In a project with no Next route folder, the page path that
astryx buildandastryx templatename is now the file the copy writes (src/pages/<id>.tsx), not a folder holdingpage.tsx; a block's path is now its file (app/components/<id>.tsx,components/<id>.tsxorsrc/components/<id>.tsx) in every project. An import of the named path, such asimport Page from './pages/settings', now resolves, and a name an import already resolves to (a folder's index or a file with another extension) moves to<id>-2. Next App Router pages keep their route folder, and Pages Router pages were already files. - A
{@link …}in a template's description no longer prints as written.astryx template(the list,--skeleton, and a template read),astryx build,astryx searchandastryx component <Name> --blocksresolve it to the command that opens the doc it names, asastryx docsdoes: with the project's command in text, and as the bareastryx …command in--json. The JSON shape does not change. - A template doc's
{@command …}and{@pm …}tokens no longer print as written.astryx template(the list and--skeleton),astryx buildandastryx searchshow the command with the project's command in text, asastryx docsdoes, and as the bareastryx …command in--json; the JSON shape does not change.buildandsearchtext show every description's commands with the project's command too. A template's source still prints byte for byte. astryx template <name> ~/<path>reads~/as the home folder, as a shell does. A caller that passed~through unexpanded no longer gets a folder named~in the project: a home path outside the project is refused with the commands that work, like any absolute path outside it, and one inside the project is written there.template --cdnreads it the same way. To write into a folder that is really named~in the project, write it as./~/<path>.- A copy of the
canvas-editorpage template no longer carries two comments about its icon imports that no longer described them: one on aliasingFile, one on which Lucide icon draws the rotation angle. The template now names its icons by meaning, and its copy draws the same icons as before. - A page template's keyword now means one concept. When build chooses the start and its alternatives, a multi-word keyword counts only as the whole phrase (skipping stopwords and one-letter words inside it), so its single words no longer count for other templates. Core templates' keywords are migrated: lists of words are split into single keywords, terms that mean something different as a whole (such as "getting started" or "reading pane") stay phrases, and keywords that weren't true of their template are removed. The template-doc field reference says how to write keywords.
- Four Core page templates no longer list keywords for things their page does not render, so
astryx buildandastryx searchstop offering them for those ideas. AI Chat Conversation drops "citations", "reasoning" and "playground"; Kanban Board drops "swimlane" and "backlog"; Page Editor drops "drag and drop"; Theme Showcase drops "tokens", "palette" and "typography". The Page Editor and Theme Showcase descriptions now say what the page renders: blocks reorder with move up and move down, and the showcase shows sample product screens in the active theme. astryx doctorwarns on a{@link}in a template's description that names no doc, anddoctor integration validatelists it as anextnote, sointegration check --strictfails on it only from the next minor release.- 37 page templates (the tool templates other than
incident-console, the content templates other thanwork-item-detail, the form, gallery and hero, login, settings and AI chat templates, plusblankandtheme-showcase) give screen readers clearer structure: each marks its content area ([LayoutContent](/components/LayoutContent), or the page's[Center](/components/Center)root where it has no content area) as the main landmark, has exactly one level-1 heading in each state it shows (a phone section view, a sign-in step, the signed-in state), and has a heading outline with no skipped levels. Titles keep their look (accessibilityLevel, or[Text](/components/Text)rendered ash1); pages without a visible title get a visually hidden one. Also: icon-only columns ineditorandtheme-showcaseget visually hidden header names, anddocumentation-designnames each example's tab list. No visual change. - Action buttons that did nothing in four page templates now respond with a confirmation toast: Restock, Fulfill item, Create label, Refund and Send Invoice on the order detail page, the next-step action in the service-jobs detail panel, Dispute this line on the invoice line items page, and Format Document in the IDE workspace.
- Action buttons and menu items that did nothing in eleven more page templates now respond with a toast that names the demo action: Add to Cart and Buy it now on the product detail page, Publish in the page editor, the sign-in, plan, export and connected-app actions in the settings dialog, Sign In, Google Pay, PayPal and the promo code's Apply on the payment form, Save & exit, Crop image and Preview on device in the vertical form wizard, the social sign-in buttons on both login pages, Share in the file explorer, the AI chat landing page's settings menu and composer, and Pin, Rename and Archive in the side-nav shell's conversation menu. On the work item page, Add subtask and each attachment's Edit name their demo action, Cancel clears the comment, and Comment confirms it and clears the field. The settings dialog's search-result chevron mirrors in right-to-left layouts.
- 78 template buttons that did nothing when pressed now say what would happen, as the other template demo actions do: the example toolbar buttons of the
documentation-designpage template, and the buttons with no handler in the Button, ButtonGroup, Center, IconButton, Layout, MediaTheme, Section, Stack, Theme, Toolbar and VisuallyHidden example blocks, show a "Demo: …" toast. A destructive one (delete, archive, or a destructive-variant demo) first asks for confirmation; Cancel does nothing. - More template buttons that did nothing when pressed now show a
Demo:toast that says what would happen. Archive and Delete ask first with a confirm dialog, then show the toast. Overflow menu items run the same action as their buttons. Upgrade is a link. Fixed blocks: OverflowListShowcase, OverflowListOverflowDropdownActions, OverflowListCollapseFromStartList, OverflowListCappedToolbar, TooltipActionBarTooltips, BannerWithActionButton, BannerSectionVariant, BannerCollapsibleContent, useOverflowHookUsage, useContainerRevealHookUsage, useListFocusHookUsage, TopNavWithLogo, TopNavHoverMenu, TopNavMenuShowcase, TokenizerEndContent, StepContent, useOverlayHookUsage, OverlayShowcase, OverlayHoverReveal, ChatComposerFullFeatured, ChatComposerFooterActions and ChatComposerFlat. No pages change. - The Table Filter template and the Avatar and LinkProvider example blocks show a "Demo: …" toast for their demo actions instead of calling
alert(), so the click still responds when the page runs in a frame that blocks browser dialogs. - The technical documentation page template now teaches the real setup. Its AI setup prompt no longer asks for a style compiler, which contradicted the article's own precompiled-CSS step, and its theming example uses the real
[Theme](/components/Theme)component from@astryxdesign/core/themewith a theme package instead of aThemeProviderthat Astryx does not export. Its prerequisites now name React 19 or later, which Core requires. - Three menu items in two page templates now respond instead of doing nothing. In the grouped issues table, "Edit issue" and "Duplicate" confirm with a demo toast. On the kanban board, "Assign to me" confirms with a demo toast. Each toast handler carries a comment that marks where to connect the real action.
- Page templates now have no horizontal overflow on a 390 px phone, with touch or a mouse. In the service-health, data, funnel-and-cohort and program-status dashboards and the kanban board, the header controls now wrap onto a second row instead of widening the page past the screen edge, and on the data dashboard a section heading's hint is no longer squeezed into a narrow column beside the heading. Desktop layouts are unchanged. A check builds every ready page template into an app and runs it in a 390 px phone emulation, with touch and with a mouse, so a template that widens the page past a phone's screen fails before release.
- The
dashboard-scorecardanddashboard-progresstemplates no longer wrap whole page sections in cards, as Card's own guidance says: the scorecard's goal list, and the progress page's summary panels and workstream table, sit in plain page sections under their headings. Repeated items keep their cards: the scorecard's metric tiles, trend charts and commentary notes. - The
dashboard-scorecardanddashboard-progresstemplates draw their trend lines as straight segments between the measured points, so a line no longer bends between measured points. - With longer, translated labels at phone width, the form wizard, vertical form wizard, technical documentation and table templates keep their buttons in full: their header, footer and toolbar rows wrap instead of cutting labels or pushing controls off screen. The canvas editor's header keeps its save note and Export at full width, and the badge and stack direction examples wrap their rows. In English at 390 and 1280 px only the form wizard's last step changes: Back and "Create workspace", which were cut, now show in full. On narrower phones, English rows that were already tight wrap instead of cutting a label or running past the edge: the technical documentation's AI assistance row from about 375 px (its More options menu button moves to a second line), the vertical form wizard's header from about 330 px (Save & exit moves to a second line), and at 320 px the form wizard's Back and Next (its Cancel moves to a second line just below 320 px). The badge and stack direction examples wrap in columns narrower than about 295 and 335 px.
astryx theme buildnames an import through a path alias (@/lib/c,~/lib/c) as one the theme loader does not map, never as a package to install; expands a quoted glob to the theme sources it matches in its suggestion; and counts the fonts macOS and Windows ship, from one table by platform, as system fonts in its note on fonts named but not loaded.astryx theme buildrefuses a blank or whitespace-only--out(it wrote files named by the spaces alone), and its note on fonts named but not loaded leaves out the families a local theme's own font stylesheet loads (<slug>.fonts.cssbeside the source, the stylesheettheme addimports).astryx theme buildandastryx doctoralso treat Segoe UI Light, Semilight, Semibold and Black as system fonts, the faces Windows installs as families of their own, so neither reports them as not loaded.astryx theme buildwarns, at its line and with the same output as before, custom properties that read each other (a token with a fallback reading itself, two tokens, a half of a [light, dark] pair, tokens and local tokens, a part's own custom property), a pseudo-element near a known one (as that one misspelled), a pseudo-element missing from the CLI's selector data (as possibly newer than the CLI), a pseudo-element inside:is(),:where(),:not()or:has(), a pseudo-class after::highlight(),:window-inactiveafter any highlight but::selection, a token name that does not start with exactly two dashes, and an empty token value. A pseudo-class after::search-textor::scroll-marker-groupis no longer warned. A child theme's own build names the file and line of a value the theme it extends writes. A null value's warning says what it builds: a null property leaves the base theme's value, while a null token is kept by the browser as the token's value, so most properties that read it act as if they were not set (text keeps the surrounding color, a background goes transparent) and a font family reading it falls back to the browser's default font.astryx theme buildcounts the fonts macOS and Windows ship for Chinese, Japanese and Korean (such as PingFang SC, Hiragino Sans, Microsoft YaHei and 微软雅黑) as system fonts, so it no longer names them as fonts the theme does not load.astryx theme buildwarns a[light, dark]pair with any half that is no color (a size, a duration, a word that is no color name), not sizes only, sincelight-dark()takes colors only. A value the build cannot place on a line of the theme file is named as computed in it, and the theme it extends is named only when it holds that very value.astryx theme buildreads a font family name as CSS reads it (Gill\ Sansis Gill Sans), names as not loaded a family the theme holds in its own property and reads withvar(), and builds a theme bound withletorvarthat is never assigned again as it builds aconst(one assigned again is refused naming that, not as an icon registry it sets).astryx theme build: a doc module given as the theme (oceanTheme.doc.mjs, or a file whose default export is a doc such as{type: 'theme', name, description}) is refused withERR_THEME_LOAD, naming it as a doc and the theme source beside it to build, and nothing is written.theme buildof a missing file in a folder whose files another command generates (their first comment says which command writes them) says the file is generated and names that command, instead of offering a blank theme template.doctorstill compares such a local theme's outputs with its source, and its fix for a stale or missing one runs the exact command that writes it, never atheme build.doctor's fix when the themes folder cannot be read names the theme the message names (for a generated one, its command), never<slug>. A font stylesheet's local@import(a file beside it,url(faces.css), or a package stylesheet such as@fontsource/inter/index.css, resolved from where the stylesheet really is) is followed and its fonts proven; a URL import is an external font service, and a local import doctor cannot follow, or one past the files it follows, is a warning, never a failure. The help and docs sayeditor show <name> --pngtakes pictures of real components.astryx theme build: building a theme the theme editor made now also says that the build does not write (or, with--check, does not check) the theme's app copy insrc/themes/<theme>/, which the app imports, and names theastryx experimental theme compilecommand that builds the theme and writes the copy.astryx theme build: a plain-object theme with notokens, a name alone (export default {name: 'p'}) or a name and component styles, builds as an empty theme over the base instead of ending with "Cannot convert undefined or null to object".themeBuildFamily(astryx theme build --family) builds each member as it is at that build. Before, a second family build in the same process, such as a tool or a test that builds in process, built a member file changed since the first build from the module the first build had loaded.astryx theme buildnames a misspelled field at the line that writes it when the theme object is a member of a const (all.a), an element of an array, a branch of a ternary, an objectObject.assignmerges, or adefineTheme()argument written any of those ways.astryx doctornames each cause when a theme package's built module both imports TypeScript source and has a stylesheet that names a file the package does not ship. Plain themes whose bases extend each other in a cycle are refused naming the cycle, instead of a stack overflow or a silent merge.astryx experimental themeremoves a render folder a killed command left as soon as its maker is known gone (same machine, no such process), not only once it is ten minutes old.astryx theme buildno longer sets the page root's color scheme. A built theme stylesheet used to declare:root { color-scheme: light dark; }, so a site that loads it withoutreset.css, and sets no scheme of its own, followed the reader's device: for a dark-mode reader its native controls, links and page canvas turned dark around its own light content. A theme now follows the page's scheme; it still pins it where the page or the Theme provider forces a mode (html[data-theme="light"|"dark"]), and a--familybuild drops the same rule from each theme's scope. Apps whose page scheme comes only fromreset.csssee no change, while an app that sets its owncolor-schemeonhtml(in its own CSS layer, as the Tailwind setup does) now keeps it. To follow the device with theme CSS alone, add reset.css orhtml { color-scheme: light dark }.astryx theme build: its font notices name the typography recipe, written with the project's own runner in text output, and it compares real paths in the disk's own case, so a theme reached through a differently cased path is not reported as missing or as another file.astryx theme buildandastryx doctorgive each file that says a tool generates it (@generated,@partially-generatedor[Code](/components/Code) generated … DO NOT EDIT.in its leading comments) one note with the count and that tool (--familyand doctor give one per file, however many themes extend it), instead of a warning per setting it writes that does not show as written: that file is not where the fix goes. The build's note reaches text,--json,--checkand--familyoutput, andsettingIssuesstill lists each setting; doctor's note names thetheme build --check --jsoncommand that lists them. A hand-written theme that a generated one extends keeps its own warnings.astryx theme buildno longer replaces a file it did not write at its default outputs beside the source. A file of your own named like an output (brand.cssorbrand.jsbesidebrand.ts) used to be silently overwritten; now the build fails withERR_FILE_EXISTS, names the file, and writes nothing. At the default outputs, a file an earlier build wrote is still replaced, an output of the CLI before it was named Astryx included. At a path--outnames nothing changes: only a file with the current build header is replaced, as before. Beside the source, an output another theme source built there is replaced with a warning naming both sources, as at--out. To migrate a project that keeps its own file under an output's name, build to another place with--out(for example--out dist/brand.css), or move or rename your file. The--outrefusal no longer suggests building beside the source, which could replace such a file.astryx theme buildandastryx doctorno longer warn that a theme's font does not load for Noto Sans, Noto Serif and Noto Sans Mono (system fonts of Android, ChromeOS and Linux) or Cantarell, Ubuntu and Ubuntu Mono (system fonts of Linux). A system font stack that names them needs no font package.astryx theme build: the import hint is given only for a load failure that is an unresolved import, and@fontsource-variable/<name>is read as loading<Name> Variable, the family that package declares, not<Name>.astryx theme build: a theme module that throws from a microtask it queues while it loads is a refused load (ERR_THEME_LOAD), not a crash; a listener a theme module adds toprocess(process.on('exit', …),beforeExit) goes with its load, so it no longer sets the command's exit code, prints after the--jsonenvelope, or keeps the command from ending.--outnaming a stylesheet's source map (p.css.map) is refused, and a slip after.css(p.css.bak) is told the stylesheet name meant (p.css, notp.css.css).astryx experimental theme compilerefuses a theme whose own values throw when read (atokensgetter or Proxy) as the build does, with no stack trace orERR_UNKNOWN.astryx theme buildwarns, at its line and with the form that works, more part keys a browser drops or Core misreads: a vendor property written without its dash, a pseudo name in capitals, something after a pseudo-element, two pseudo-elements, an escaped pseudo name, the custom property--, an empty key, and a block under a key that nests none. The output is the same as before. A--familybuild with such a key in a member builds, with each warning naming the member's file, where it stopped on an unknown error before. A default export that is a Promise of a theme is named as one, instead of a theme without a name.astryx theme build(andastryx experimental theme compile, which builds the same way):- A theme that gives null for a part or a style key's block is refused at the line that gives it, never a crash. A null property or token value keeps its meaning (it is written as it is) and is warned at its line.
- A style key no element carries is warned: a value a closed prop never takes (
size:xxlon Button, which takes sm, md and lg) and a pseudo-class written as a style key (':hover', which goes inside one:base: {':hover': …}). - A named pipe, a device or a socket where an output or
--outgoes is refused at once, never opened. --out out/.cssis told to give the stylesheet a name. An--outthat starts with an unexpanded~is warned: the build writes in the project's~folder, as before, and the warning names that folder and the home folder path to give instead.- A theme with no name is refused as one, at its line.
- Apple Color Emoji and Noto Color Emoji count as the systems' own fonts.
astryx theme buildwarns, at its line and with the same output as before, more values a browser drops: a part property that builds dash-first without a vendor prefix (Color), a token or part value that is no text (an object, a boolean, NaN, an array in a part), a [light, dark] pair with a missing half or another count, a token that reads itself, and a token'svar()that no token sets. A pseudo-class after a pseudo-element that takes one (::file-selector-button:hover) is no longer warned, and only:hoverand:activein capitals are. A warning about a value the theme takes from the theme it extends no longer gives a line of the file that extends it, and a--familybuild names it once, at the member that writes it. A tokens map spread from a defined theme's tokens no longer trips over Core's own private copies in it.astryx theme buildreads a base theme that the same file defines as a const, and that the theme'sextendsnames (directly, or throughdefineTheme(...)or a wrapper), as the theme it extends, not as the theme itself: a setting the base's variant beats is named, and the theme's own lookup never reads that base. A base that a call returns (extends: makeBase()) or that a helper's object names is still read as the theme's own.theme buildthrough a CLI installed for the computer now writes the same files as a CLI installed beside Core. It reads the component docs and types of the Core it builds with, which is the project's. So a theme that gives a component a custom variant gets its.variants.d.tstype declarations. Before, that CLI read them only from a Core beside it, which it does not have. It wrote no variant declarations, anddoctorandtheme build --checkreported a theme built by another CLI as stale. The built module's doc comment now namesastryx theme buildrather than the command that ran the build, so builds through different package managers or tools write the same module.astryx theme buildnow writes a built theme module that loads in any bundler and in plain Node. A local module the built module imports (an icon registry, a component icon slot value, or the helpers they import) that is TypeScript or JSX is compiled to JavaScript named after its source (icons.tsx→icons.tsx.js) in a folder beside the built module named for it (w98.modulesbesidew98.js, whatever--outnames the stylesheet), at the place each source has under the folder that holds the theme and its compiled sources, so every compiled module has a path of its own:import { icons } from './icons'withicons.tsxbeside the theme becomesimport { icons } from './w98.modules/icons.tsx.js', and a helper it imports becomesw98.modules/helper.ts.js. Each local import names its file with its extension. Before, the built module kept the TypeScript import, so an app whose bundler does not compile TypeScript fromnode_modules(a plain Next.js app) failed to build after it added the theme. The compiled modules carry the build header,--checkcompares them, and a file of your own at a compiled module's path is never replaced (that import stays as written, with a warning saying so). A theme with no local module writes the same outputs as before; package imports stay as they are.--familybuilds compile each member's TypeScript registry the same way, in a folder named for the family key.astryx theme build: a family build names a file it replaces, and builds that would not load say so.- A family build over a file with no build header at the
--family-keyname (an output of a CLI before 0.6.7, or a file of your own) still replaces it, now with a warning naming the file. Another theme's outputs there are replaced with a warning naming that theme. - A family member whose icon registry is imported without its extension (
import {icons} from './icons') builds, as it does on its own. - An icon registry that imports an asset (
import check from './check.svg', a.png, a font) builds; the asset loads as its URL, as a bundler gives it. - With
--outin another folder, a relative icon registry import that nothing answers to from there is warned, with the--icons-specifierthat names the registry from there. - A theme file that exports two named themes and no default warns which theme it builds and which it leaves out.
- An empty or blank
--icons-specifieris warned (the built module would import from"");astryx experimental theme compilerefuses it, and an empty or blank--out, before building.theme build --out ''still writes beside the source.
- A family build over a file with no build header at the
astryx theme build: what a theme module leaves running no longer decides the command, and three source layouts build.- A callback a theme module leaves running that calls
process.exitafter the module loaded is ignored with a warning; one that setsprocess.exitCodedoes not set the command's; one that throws is a warning, not a crash after the result. - A family root may import the family's own stylesheet (
import './k.css'for--family-key k), and a source its own stylesheet with a query (import './p.css?inline'): a first build from a clean checkout writes it. - A project in a folder whose name holds
#,?or%20builds a theme that imports a stylesheet. - What a theme module changes for the whole process while it loads (the working folder, a built-in object such as
JSONorObject.prototype) is put back when the load ends. --outnaming a TypeScript declaration file (p.css.d.ts) is refused with the stylesheet name to give, instead of writing CSS into it.
- A callback a theme module leaves running that calls
astryx theme build:- A plain-object theme (
export default {name, tokens}) goes throughdefineThemeas adefineTheme(…)call does: a[light, dark]pair is written aslight-dark(), and Core's media-surface rules are written. One withextendsand no tokens builds as the empty theme over its base. - A spread of a package theme (
{...neutralTheme, name}) is refused naming the spread and the form that builds (extends: neutralTheme), not aniconsfield the file does not set. - A stylesheet the theme source imports (
import './brand.css') is named in a warning: the built outputs do not carry it, so the app imports it. - What a theme module changes while it loads in
console, a global (Buffer) or the file mode mask is put back when the load ends, so the command prints its result and writes readable files.
- A plain-object theme (
astryx theme build: a theme file is read for its theme, and nothing it does while loading breaks the command.- A Sass, Less, Stylus or PostCSS stylesheet a theme module imports loads as an empty module, as a
.cssimport does. - An import that the project's tsconfig
pathsorbaseUrlmaps (@app/c,lib/c) is named as a path alias, never offered as a package to install. - With
--outnaming another stylesheet, the built module's usage comment names the stylesheet written. - When a build of several files stops at a failure, the error says which outputs the files before it wrote, in text and
--jsonalike. - A default export that holds themes (
export default {light, dark}) is named as such. - A theme module that calls
process.exitwhile loading is refused by name;--checknever passes without its verdict. - A value a theme module throws that is not an Error is shown as it is.
- What a theme module prints goes to stderr, so
--jsonoutput stays valid. - A timer a theme module leaves running no longer keeps
theme buildor--checkfrom exiting.
- A Sass, Less, Stylus or PostCSS stylesheet a theme module imports loads as an empty module, as a
astryx theme build:- A plain-object theme a theme extends (
const b = {name: 'b', extends: neutralTheme, …}; export default {name: 'p', extends: b}) is made withdefineThemefirst, so its own base, typography and[light, dark]pairs are kept, and one with no tokens builds. - A misspelled field is named wherever the theme object comes from (a member, an array element,
Object.assign), without a line where the source does not write it as one. - The warning for a stylesheet the theme source imports names a package stylesheet by the specifier the source wrote, and is given by the editor's compile too.
- A plain-object theme whose getter throws is a failed load (
ERR_THEME_LOAD) naming the file and the field, notERR_UNKNOWN.
- A plain-object theme a theme extends (
astryx theme buildwarns, at its line and with the form that works, a part key it cannot write as intended: a pseudo key that leaves a parenthesis, bracket, quote or comment open (a browser then drops the rules after it), a pseudo key that is no selector, a selector list such as':hover, :focus'(only its first member is scoped to the part), and a custom property with capitals (written in kebab case, sovar()of the name as written reads nothing). The output is the same as before. A missing input near a theme source in the same folder (a missing extension, a one-letter slip) is offered that source.- An import written as a template literal with nothing put in it (
import(`./icons.ts`)) is read as the string it holds by these commands:astryx theme build --watchfollows it, the built theme module carries it,astryx doctor's shipped-import check judges it, andastryx templatelists a package imported that way in its install line when the project lacks it. Before, such an import was skipped. astryx theme buildreadsvar()in any letter case when it warns about a token that reads itself, tokens that read each other, or avar()no token sets, and it follows a loop through the token definitions Core sets on the theme's root (--font-size-2xl: var(--text-heading-1-size)). A misspelled pseudo-class (:hovr) is warned with the one it is near. The output is the same as before.astryx theme buildwarns a misspelled field in a theme aletis reassigned to or a dynamic import loads, at its line; warns tokens given as aMaporSet, whose entries it does not read; and stops at the field, with a message, on a token object that has no text form (made withObject.create(null)), never with Node's own text. A BigInt in a plain theme's type scale no longer ends the build.astryx experimental themereads a boxed token (new String('red')) as the text the build writes.astryx theme build: a theme file is read for its theme, and what its code leaves behind no longer decides the command.- A family build over a file at the
--family-keyname lists the replace warning in--jsontoo, as the text does. - A
process.exitCodea theme module sets is not the command's exit code. - A theme module importing a
.postcss,.stylusor.sssstylesheet loads it as an empty module. - What a theme module prints after it loaded (a deferred log) goes to stderr, so
--jsonstays valid. - A theme module whose top-level await never settles is refused (
ERR_THEME_LOAD, naming the file), not ended by Node with exit 13. - A theme source may import the stylesheet its own build writes, which a first build from a clean checkout now writes; a missing stylesheet it does not write is refused by name.
- Every handle a theme module opens (a timer from
node:timers, a file watcher, a server, a message port) is let go once it is loaded, so the command exits. - A promise a theme module leaves rejecting is a warning on stderr, not a crash after the result.
astryx experimental theme compilenames a value a theme twoextendsup refuses in the file and line that hold it.
- A family build over a file at the
astryx theme buildwarns, at its line and with the same output as before, a fielddefineTheme()does not take (component:,tokenz:,ondark:,onDark.localTokens,typography.body.fontFamily), with the field it is near; and a BigInt, a function or a Date value, naming what it writes. A BigInt no longer ends the build with an unknown error. A surface token that loops through a token Core sets on that surface is warned once, at its line, and Core's own surface token is no longer named as one from the theme it extends.astryx theme buildwarns a[light, dark]pair of sizes (['4px', '12px']), whichlight-dark()does not take, and a pair half that reads a token nothing sets, as it warns the same CSS written as text. A var() name with a letter beyond ASCII (var(--café)) is read as CSS reads it: no false warning in the build, and no refusal inastryx experimental theme.astryx theme buildwarns a misspelled field that reaches the theme input through a spread ({...shared},onDark: {...dark}, an imported object), or in a theme the file imports and then exports, at the line that writes it; a BigInt typography value held in a const is named too; and a[light, dark]pair whose half is empty or a number, whichlight-dark()does not take, so the browser drops the value. A boxed primitive in a part (padding: new String('4px')) is written as its text, as a token's is, instead of as JSON text with its quotes.astryx theme buildwarns a misspelled field wherever the theme's sources write its input: an input held in a const,defineThemeimported under another name, a theme a file re-exports from another module (named with that module's file and line), and anonDark,onLightortypographyblock held in a const; a method written as a field (onLoad() {}) is warned too, and so is a BigInt typography value. A TypeScript type assertion such as<any>1in a.tstheme no longer costs every warning its line. A BigInt inside a part's array or nested block no longer ends the build: it is warned by what is written, and a value that holds itself stops the build at its line. A symbol, or a tokens object that holds itself, stops the build at its line instead of with a raw error. A boxed string (new String('4px')) is judged by what is written: no warning as a token or a pair half.astryx theme build --jsoncarries in itswarningsthe--outwarnings the text run prints (a stylesheet name that is not .css, an output of another theme source it replaces, a folder the theme editor made), names a folder it cannot write with its fix instead of a temporary file's error, and names anextendswritten as a helper's call or a conditional as what it cannot follow instead of an inline icon registry. Its note on fonts named but not loaded also names the families of a component'sfontshorthand (font: '600 14px Lora, serif'). [fix]astryx theme build's full font help leaves out, family by family, each family the theme's own<slug>.fonts.cssloads; before, it printed the whole list unless every family was loaded.astryx theme build --watchrebuilds when a file a theme brings in with TypeScript'simport x = require('./file')changes, as it does for any other import.theme build --checkanddoctorno longer call a local theme's outputs stale just because another CLI release built them, or the CLI ran under another command name. Each output's header still names the CLI release that built it, and a built module still names the build command, but those lines no longer have to match. Before, every update of the CLI that answers marked every local theme stale. So did building under one command name and checking under another, although a rebuild changed only those lines. That CLI can be a global install, or a tool that runs the CLI for you.- A theme that gives a Card, a Dialog or a menu corners of different radii (
borderRadius: '12px 12px 0 0'or a corner longhand such asborderStartStartRadius) now reaches what those components hand each corner to: a full-bleed Table or a bleeding List in a Card or a Dialog takes each corner as the container draws it, focus ring and row fills included, and the rows of a pointer menu (DropdownMenu's popover and sub-menu flyouts, and ContextMenu), sub-menu rows included, take the menu's shape less its padding; the touch sheet's list rows, and a drilled-in sub-menu view with its own header or footer, keep their own corners. An elliptical corner (8px / 4px) reaches a full-bleed Table; a List and menu rows subtract the padding from it, so they keep square corners there. A default Card, Dialog or menu inside a themed one keeps its own corners. Before, these children kept square corners, or took the first corner's radius at every corner when the CLI theme editor wrote the radius. The theme pipeline writes each corner to its own private variable for components whose derivedborderRadiusentry sets the newcornersflag. A radius of one value draws as before. - When an app adds a theme from a package it has not installed,
theme addanddoctornow name the install that works. They use the project's package manager. For a theme package that Astryx releases with Core, they name the project's Core release, saved exactly when the project pins Core. A project with no Core yet gets the release of the CLI that answers. Before,doctornamednpm install <theme>@latest, andtheme addnamed the package with no version. Each Astryx theme names Core's exact release as its peer, so in a project on an older release, npm refused the install.doctoralso no longer adds--package @astryxdesign/clito the theme add command, which named the CLI as the theme's package. astryx theme buildgives one warning, at its line, for a part's variants written as avariantsmap of values to blocks (variants: {variant: {secondary: {…}}}), naming the style keys that write them ('variant:secondary': {…}), instead of three warnings that never showed the working form. The output is the same as before.- The theme showcase template's inventory table keeps product names whole on phones: the Item column's floor grows from 80 px to 160 px, and in a narrow column the name moves under its thumbnail instead of breaking letter by letter. The table scrolls sideways in its own region as before. Wide screens look the same.
theme build(with or without--checkor--family),integration verifyanddoctorload a theme that extends a base theme whose module imports its own stylesheet, such as a package's./themes/<slug>entry that loads the theme's CSS. Node stopped on that import withUnknown file extension ".css". On Node 22.15 and later, a stylesheet that any module of the theme imports now loads as an empty module. Node resolves each stylesheet import from the module that writes it, so a missing stylesheet still fails. On Node 22.13 and 22.14 nothing changes: a theme build (theme build,integration verify,doctor's freshness check) still stops on any stylesheet import, and a read of a built theme module (doctor,component) still loads only a stylesheet whose import resolves from that module's folder.- A plain table's rows keep the text colour around them in Butter, Y2K and Gothic; only a striped table's even rows take the stripe's text. Inside a coloured card in dark mode, every second row of a plain table read white on the pastel card, at 1.15:1 to 2.12:1. Those themes' striped-row rule now reads the row's
stripedstate, in their packages and in the copies the CLI bundles. - On a phone, TopNav's end content is never wider than the bar, so an end item that can narrow, like a search field, narrows and the menu button stays in view. The Shell Nav template's search now narrows on a phone instead of pushing the menu button off screen at 375 px.
- The per-user cache of transpiled TypeScript stays small and fast however many folders load the same files. Copies now live in
astryx/transpiled, named for each file's text and settings, so the same file in many folders shares one copy, unless its text containsmeta. Each new copy trims only its own subfolder, so no run reads the whole cache. Before, a machine that ran many projects or tests in fresh folders could fill the old single folder with hundreds of thousands of copies, and the next theme command spent minutes reading it. Projectdoctornow names that old folder and the command that removes it. - An unknown command names the command meant when its words come from another command line.
astryx add theme matchanamestheme add matcha, notintegration add theme matcha;astryx eject buttonnamesswizzle [Button](/components/Button), nottheme eject button;astryx templates listnamestemplate --list, not a template calledlist. A short table of other tools' words names the command that does their job:migrate --from 0.6.0namesupgrade --from 0.6.0,add buttonnamesswizzle [Button](/components/Button)andcomponent [Button](/components/Button),add settings --path <file>namestemplate settings <file>,props [Card](/components/Card)namescomponent [Card](/components/Card) --props, andbrowse integrationsnamesdiscover. A suggestion keeps the options in reach of the command it names, including the program's own (--json,--base), and names an input the run still needs as a placeholder (upgrade --from <old-version>). A suggestion is never run for you. - A manifest key the running CLI does not know is no longer an integration issue. Everyday commands stop printing "has 1 integration issue(s)" for an integration published against a newer CLI, and project
doctorno longer lists it.doctor integration validateandintegration checklist it as anunknown_manifest_keynote, which fails nothing; a key one letter from a known one is anextnote with its fix. - Outside a project,
astryx upgradewithout--fromnow leads with the reason: the folder is outside a project. It says to run upgrade with--from <old version>in the app's folder. Before, it led with "Missing required --from", so adding--fromin the same folder got a second refusal. astryx upgradereads a.tsfile as TypeScript without JSX and a declaration file as declarations, as TypeScript does. A type assertion (<[Item](/components/Item)>value) in a.tsfile, or a declaration without a value (export const limit: number;) in a declaration file (.d.ts,.d.mts,.d.cts, or an arbitrary-extension declaration file such asstyles.d.css.ts), no longer stops the run with a parse error, and a codemod changes such a file like any other. A.tsxfile and JavaScript read as before.- Outside a project,
astryx doctor integration validate <package>now checks the copy of the package that the folder uses, an integration installed for the computer included. Before, it looked only in thenode_modulesat or above the folder and reportedpackage_not_found, thoughastryx doctornames this command for an integration installed for the computer that it cannot load. A copy that the other commands skip for its peer ranges is checked too, with a note that says why:cli_peer_version, or the newcore_peer_versionwhen only its@astryxdesign/corerange excludes this CLI's release. - The StyleX setup docs name
@stylexjs/unplugin(stylex.vite()) for Vite. Under Vite,@stylexjs/rollup-pluginfails onastryx.css, so a page template that uses StyleX stayed blank. The note on such a template now points to the setup section. - The work item's subtasks wrap instead of cutting off after a few words on a phone, and each task's due date and assignee move under its title there.
Performance
- A mistyped
astryx componentname answers faster on repeat runs: the Core docs its suggestions read are kept between runs, so the answer no longer reads every Core doc again. (#12538) - A run that loads no project, other than
hook, and whose--basenames no other package, such asastryx --version,--helpormanifest, no longer loads the base resolver. Core's base declaration reads Core's package name from a small module of its own, so it loads no provider-identity code. Output is unchanged. - A run that keeps many values trims the per-user catalogs folder once, when it ends (a command that fails trims it as it exits), instead of after each value. A first
theme buildon a fresh cache keeps about 270 values and is about 130 ms faster. Every answer is unchanged, and the folder keeps the same size limit. upgradeskips a codemod for a file that holds a backslash when the file's escapes spell none of the codemod's words, as it already did for files with no backslash. Before, any backslash anywhere in a file (a\nin a string, a\din a regular expression) sent the file through every codemod's parse, so a scan of a typical app parsed about a quarter of its files several more times than needed. An upgrade from 0.6.8 answered 24% to 55% sooner across the apps measured; ranges that run mostly older codemods gain less, because those codemods still run on every file. Output and written files are unchanged.upgradebinds jscodeshift to each parser once per codemod instead of once per file, which built a new copy of jscodeshift's helpers for every file. An upgrade over a 240-file app runs about 150 ms faster. Output does not change.- On Linux, in a project whose integration takes the CLI's debug record, every command finishes about 11 to 17 ms sooner. The record names the locale and time zone the process's Intl uses, and asking Intl for them first loads ICU's data at the end of the run. The answer is now kept beside the kept gathers while the environment values, the Node and ICU versions and the time zone files it comes from are unchanged. Elsewhere, and on other systems, it is asked as before. The record's values do not change.
astryx discoverwith no query asks the project's discover sources for their catalogs while it reads the installed packages, instead of after. With a large integration whose source asks a remote catalog, the list came back about 0.4 seconds sooner. Output does not change.- A command that keeps catalogs keeps the parse of each shipped doc it reads, by the doc's text, so a later read of that doc does not parse it again. The doc parsers build their schemas only when they first parse, not when the CLI loads them. Output is unchanged.
docskeeps the CLI's own docs tree between runs, while every file it was read from is unchanged. In a project where an integration can load,docsand its topics start about 30 to 65 ms sooner. Where none can load,docskeeps nothing and nothing changes.doctorstill checks the tree's files themselves. Output does not change, except thatdoctor's row for the per-user cache now names the docs tree among the entries it holds.doctor --built <path>now reads doctor's kept checks back asdoctordoes, once the per-user cache folder exists: the CLI took the path after--builtfor a subcommand, so those runs checked the docs again every time. In a project whose integrations add docs, a warmdoctor --builtis about 200 ms faster; in a Core-only project the difference is within noise. The build itself is still checked on every run. Check results do not change; the cache row counts the kept checks.doctor --builtreads source files faster: it parses each file without attaching comments to syntax nodes, blanks comments in one pass, and walks a file's syntax tree forrequire()andimport()calls only when its text can hold one. On a 240-file app the source scan takes about a third less time. Output does not change.- Once the per-user catalogs folder exists,
astryx doctorkeeps what itsbutton-actionscheck finds while every folder the check listed, every file it read and every package it looked up are unchanged. A warmdoctorin a project that has not changed then skips that check's scan: it no longer parses the project's pages for buttons again. Every answer is unchanged. - Once the per-user catalogs folder exists,
astryx doctorkeeps what itscore-propscheck finds while every folder the check listed, every file it read, and the TypeScript, Core and project config it used are unchanged. A warmdoctorin a project that has not changed then skips that check's scan: the check no longer parses the project's pages or reads Core's types again. The check also loads its parts only when they are needed, so a project without TypeScript no longer loads the component reader. Every answer is unchanged. astryx doctorreads its kept docs checks back after an edit to the app's source. They run before the scans that read the app's source (its theme wiring and, in a project that names an icon set, its placeholder icons), so what they keep no longer depends on the app's files. Right after an edit,doctorin a project with an app finished about 230 ms sooner. Output does not change.- A kept value from an exact codec is stored as the JSON text its exactness check already read, so storing it no longer writes, parses and compares the value a second time. A run that keeps template discovery stores it about 15 ms sooner. A value that does not read back exactly is still never kept. Output does not change.
- A machine's first
searchorbuildrun, and its firstcomponent,template,theme,discoverordocsrun in a project where an integration can load, now keeps what it gathers, and Node's compile cache is written from the first run. With the CLI installed in the project, the second command on a new machine (most often the same session's next one) reads them instead of gathering again: about 1.7 s faster forsearchand 0.8 s forcomponentin a project with an integration. A global copy with no Core beside it starts installing its Core after its first run, which changes what the next run reads, so it reads from its third run, as before. Answers do not change;doctor's "Kept catalog cache" row counts the entries the first run now keeps. - A run through
@astryxdesign/cli/hostnow keeps what it gathers, as a run of theastryxbin does, so a tool that carries the CLI answers its secondsearchfrom the kept catalog: about 0.47 s instead of 1.4 s. A kept entry names the package sets, integrations and command name the host passed, so a hosted run and a bin run in the same folder never read each other's answers. Answers do not change. astryx integration checkandastryx doctor integration validatein a package's own folder keep npm's list of the files the package packs. They read it back while the package's folders list the same entries (names, types and where each link points), and package.json, the ignore files npm applies in the package and in each folder above it, any package.json above it, and the npmrc files npm reads are all unchanged. Which files npm packs never depends on what they hold, so a run after an edit inside a file, saved in place or by renaming a new copy over it, skips npm. That took seconds for a large package: each check there finished about 2.6 seconds sooner. A package that bundles dependencies, or has a link in its folders, is asked every time. Output does not change.integration checkanddoctor integration validateask npm once what a package's own folder packs, instead of once for each check that asks, and the authoring checks insideintegration checkno longer run the shipped-import check, whose notes they never read. In a large package with afilesfield,integration checkfinishes in about 10 seconds instead of 27, anddoctor integration validatein about 9 instead of 12.5. Output does not change.component --listkeeps its list between runs in a project where an integration can load, like template discovery's records, so a repeat list answers sooner there (about 220 ms with a large TypeScript integration). A new, removed or edited component, doc or integration lists again on the very next run.- Which integration component answers to a Core component's name is kept between runs with the component list, so
componentin a project whose integration replaces Core components no longer loads every one of that integration's component docs on each run: about 40 to 60 ms faster per call in a project with a large integration. It is decided again whenever a doc'sreplaces, the package's CLI range, the integration's components folder, its configuration or its manifest changes. Output does not change. - A kept catalog entry now names the kept entries it builds on and stores only the file states they do not hold. A run checks each kept entry once, however many entries build on it, so an entry checks no file that the entries it builds on already checked. A warm
component,searchortemplatein a project with a large integration checks about 3,800 fewer files; output does not change. - In a project with an integration,
astryxcommands that read back what they kept (component,search,template,docs,buildand others) finish about 10 ms sooner. A kept gather no longer checks the CLI's own files one by one: as the per-user cache record already says, the CLI's build id stands for them, and now so does the folder the CLI runs from, so a copy installed in another folder, such as a patched one, keeps its own entries. In-place edits to an installed CLI stay unsupported; deleting the per-userastryx/catalogsfolder clears what was kept. A package in the node_modules folder inside the CLI's is still checked, as before. Output does not change, exceptastryx doctor's cache row, which now names the folder beside the build id. doctorkeeps its scan of how the app wires its themes between runs, like its docs checks, so a repeatdoctoranswers about 20 to 35 ms sooner. An edit to the app's source, a theme or a theme package scans again on the very next run.- The theme build loads jiti, which transpiles TypeScript theme sources, through the module loader's lazy CommonJS loader, instead of importing jiti's ES module entry whenever any command loads the theme API.
componentin text anddoctorno longer load jiti and start about 15 to 30 ms sooner.theme buildstill loads it, but no longer through the ES module entry, which made Node scan jiti's whole CommonJS bundle for export names; it starts about 15 to 30 ms sooner too. Output does not change. - The CLI reads a project's lockfile only for an Astryx package the project has not installed, and reads it once per lookup for all such packages. In an app whose
node_modulesholds the Astryx packages it declares, no command parses the lockfile. With a large lockfile (2 MB in our measurement), that saves about 50 ms per command and about 200 ms perdoctorrun. - In a project with an integration,
astryxcommands that keep what they gather (component,search,template,docs,doctorand others) load the installed CLI's own modules by their path in its folder, without Node first checking that each file exists and where it really lives, so they finish sooner. astryx doctorstarts about 6 to 10 ms sooner, and a first lookup in a project whose integration imports the CLI's API about 15 ms sooner. Doctor's theme checks and the codemods' parser loaded postcss as they loaded, so every importer of the CLI's API loaded it too; they now load it only when they read a stylesheet. Output does not change.astryx componentand theastryx themecommands start about 5–10 ms sooner again. The theme build module they load loaded postcss at once, through the module that reads a built theme's imports; postcss now loads only when a stylesheet's imports are read. The font stylesheet reader uses the same first-use postcss. Output does not change.- What the CLI keeps between runs is checked against what each check it made returned, and no more. A check whether a file is there is checked by whether it is still there, and a real-path lookup by the path it answered. An edit to a file the CLI only checked for, or only resolved, no longer makes the next run work its kept data out again. A file whose content any kept step read is checked by its stamp, as before, and so is an ignore file a check looks for before it asks npm what a package packs. Output does not change.
- A command that reuses kept data hands each kept list of what it read to the run's records once, instead of once for every step that reuses it, and works out the CLI-file states a derived value keys on only when one is asked for. In a project with a large integration,
component,docs,doctor,search,templateandtheme listfinish 4 to 14 ms sooner. Output does not change. - A warm
astryx searchreads back from its kept entry table only the word lists the query names, not every list, so it allocates less and spends less time collecting garbage. Every answer is unchanged. searchanswers sooner: a name or keyword word that starts with another letter than a query word is no longer expanded into its plural and stem forms to compare them, since every form of a word keeps its first letter, and an entry's description words are read only when a spelled-out name needs them. Output is unchanged.astryx searchloads its icon-section code only where icon features are on, so a search in a project without them no longer loads it. Each such search is about 6–8 ms faster, and every answer is unchanged.astryx searchandastryx builduse the scores they already worked out for each word of a request when they order the results, so a long request ranks sooner. The results do not change.searchlowercases each candidate's names, keywords and prose once per run instead of on every term and synonym, and scores a one-word query once instead of twice, so a warm search answers up to about 20 ms sooner, most for one-word and typo queries. Results are unchanged.- The published CLI stores Core's component list and imports at publish, and uses them while the installed Core's files are unchanged, so
component --listanswers about 30 to 60 ms sooner in a project with no integrations. Another Core version, or a change to any Core file or folder the list reads, reads Core live, as before. - The published CLI reads its own shipped docs as already checked against their schema at publish, instead of checking each one on every read, so
docsanswers about 25 ms sooner. A doc that was edited or is not shipped is checked as before. Output is unchanged. - The published CLI stores search's catalog at publish, and uses it in a project that adds nothing to a catalog while the CLI's and Core's files are unchanged, so a machine's first
searchanswers about 350 ms sooner and its firstbuildabout 290 ms sooner. The catalog is gathered live, as before, in a project with an integration, a package that adds docs or blocks, or a local theme; with another Core version; and after a change to any file or folder the catalog reads. Output is the same. astryx templateworks out the components its "Read the components it uses in one call" line names in one pass: a name the component list holds under Core or a configured integration needs no lookup, a chart library's import needs none, and the names it does look up share each folder listing and doc read. In a project with an integration, a template answer is about 0.3–0.7 s faster again. Every answer is unchanged.astryx templatekeeps what it reads from a template's source to name the components it uses, by the source's text and the parser's release, so a warm answer no longer parses the source to name them. Every template answer is unchanged;doctor --json's kept-catalog message names the new kept value.astryx integration checkandastryx doctor integration validategather the parts of each source file the template walks judge once per check, instead of walking the file's whole syntax tree again for every template that reaches it. For a package with many templates that share helpers, each check finished about 0.4 seconds sooner. Output does not change.search, component lookups,build,doctor,integrationandtheme listno longer load Node's zlib module, which they never use;theme addloads it only to unpack a shared theme's.tgz. Those commands are about 2 ms faster, and every answer is unchanged.astryx theme buildof a theme with a local TypeScript or JSX module, such as an icon registry, finishes about 200 ms sooner when the module has not changed since the last build. The JavaScript it compiles from the module is kept beside the kept gathers and read back while the source, the compile options, the imports it rewrites and every file of the Babel that compiled it are unchanged, so such a build loads neither@babel/corenor its TypeScript and JSX plugins. A first build, and a build after an edit to the module, compile as before. The written files do not change.astryx theme buildof a theme whose part styles hold pseudo-class keys (':hover','::before') or whose tokens hold names without two dashes finishes about 20 to 30 ms sooner on a repeat build. What its css-tree checks of those keys and names find is kept beside the kept gathers and read back while the keys and every file of css-tree's code and data are unchanged, so such a build loads no css-tree. The build's warnings, errors and written files do not change.theme buildreads each Core component doc at most once per run. A theme whose component overrides name prop values (such asvariant:ghostorsize:sm) was checked against up to three views of Core's docs (the theming targets, the known prop values, and the components a new value augments), and each view read and checked every doc again. Such a build now finishes about 50 to 110 ms sooner. A theme with no such overrides reads the docs once, as before. Output does not change.- In a project where an integration can load,
theme buildkeeps what it checks a theme against in Core's component docs between runs, while every doc and folder they were worked out from is unchanged. It works them out before it reads the theme, so they do not depend on the theme: building a theme again, with or without an edit to it, finishes about 120 to 150 ms sooner. A Core-only project keeps nothing and works out only what a build needs, as before.doctor's row for the per-user cache names the new entry; output does not change otherwise. theme buildkeeps the transpiled code of the theme sources it loads in the transpile cache the CLI already uses for integration manifests and TypeScript docs, so a build of an unchanged theme no longer transpiles it again: about 150 ms faster per build. An edited theme is transpiled again. On systems with user ids, that cache is the per-user one, which now stays within the same size limit as the kept catalogs: once it has grown, a run removes its least recently used transpiled copies, never one written in the last day or read in the last day where the file system records reads.doctor's "Kept catalog cache" row now names that limit. Other output does not change.- The first
theme buildafter a CLI upgrade reads back the JavaScript it compiled from a theme's local TypeScript or JSX modules, as long as the upgrade leaves the code that compiles them and Babel's installed files as they are, so it loads no Babel compiler. For a theme with an icon registry, that first build is about 0.15–0.3 s faster, and about 0.4 s when Node's compile cache is empty too. An invalid browserslist setting in the project no longer makes that compile fail. Every other answer is unchanged. - The theme entry loads the theme build, add, eject and targets code on its first call, so a
componentread that only resolves the project's theme no longer loads it. Output is unchanged. - A
theme buildof an unchanged theme reads back what its check of settings that do not show as written parsed last time, and loads no css-tree. A warm build of a theme with component styles is about 46 ms faster. Every answer is unchanged. astryx integration checkandastryx doctor integration validateparse each of a package's source files once for the walks that follow each template's imports, instead of once for every template that reaches the file. For a package with many templates that share helpers, each check finishes about a second sooner. Output does not change.- A warm
astryx componentorastryx templatelookup that misses in a project with only Core answers about 55–60 ms faster, because template discovery is now kept for those commands. Every answer is unchanged. (#12585)
Documentation
- The agent docs
astryx initwrites, and the computer-level skill, name the Astryx prop names that differ from other libraries in the workflow's third step: buttons, badges, tokens and tabs take their text inlabel(Text, Heading and Link take children), booleans start withisorhas, and every input takesvalueandonChange. An agent that writes props before it reads a component now writes these right far more often. Runastryx upgradeorastryx initto refresh a project's agent docs. - The AI Chat Landing template's keywords name its greeting, its suggestion cards and its composer.
astryx searchnow finds it for an idea about a greeting, andastryx buildlists it as an alternative start for more ideas that name a greeting, suggestions or a composer. - The
ai-chatpage template now gives its dead buttons and menu items a behavior: the composer's send, mention and attach buttons, the document version menu, and the document's share action now show a toast saying what the real app would do there ("Demo: … would … here"), and Copy copies the document to the clipboard (desktop and narrow screens). No layout or styling changes. - The
build()API description says a whole-page idea that would start on the app shell starts from the closest page template. - The
buildAPI doc and the build kit's comments say that for a whole page the page-pick model chooses the start from the ranker's list and its own word tables, so the start can differ from the ranker's first template. - The
themerow of the bareastryx docslist says what the topic is in one sentence; the theme editor's how-to lines (make or change a theme, look after each change, a denser or roomier app, one kind of part, a starter app with no app yet) are now the first sections of thethemetopic, each shown whole whereastryx docs themeopens. - The theme authoring doc shows
defineTheme({palette})withthemePalette()from@astryxdesign/core/palette.astryx theme palette generateand the theme editor's colors give the same output as before: the CLI now runs a copy of the palette engine and its token mapping generated from Core's source. - The Astryx skill the CLI writes for agents on the computer, and the Claude Code and Codex plugin skill made from it, now say to start a page with
astryx build "<what the page is for>", and to start anything else withastryx search. - The Astryx skill the CLI writes for agents on the computer, and the Claude Code and Codex plugin skill made from it, now say to pin
@astryxdesign/cliexactly when the project pins@astryxdesign/coreexactly. Before, agents added the CLI at Core's version with a^range beside an exactly pinned Core. - The
[useContainerReveal](/components/useContainerReveal)usage block says the actions stay visible under a coarse primary pointer (a phone or tablet), not on any touch device, matching the hook's behavior on a touchscreen laptop used with a mouse. - The documentation, technical documentation, design documentation, order detail, work item detail and library page templates now list keywords in the words their users use for those pages, so
astryx searchandastryx buildfind them for more ideas. The template authoring guide now asks authors to describe each page that way. - The content page templates now give their dead buttons and menu items a behavior: in
course-detail,documentation,documentation-technical,detail-pageandwork-item-detail, the buttons, cards and menu items that did nothing now either work or show a toast saying what the real app would do there ("Demo: … would … here"), the documentation banner's Get started is a link, and toasts that claimed an action had happened now say it would happen. Refund ondetail-pageand Delete inwork-item-detail's attachment menus are left unwired, because an irreversible action needs a confirm step. No layout or styling changes. - The typography docs say what Core builds, in one rule: a heading with no
familytakes the body's whole font list; with its ownfamily, only its ownfallbacks;fallbackswith nofamilybuild nothing.TypographyConfig, itsheadingfield,defineTheme'stypography, thefonts-and-assetsdoc page and the theme template say it; thefont-setuppage says a heading with no family uses the body's and points tofonts-and-assetsfor the rest. - The debug event's
project.integrationCountis documented as what it counts: the integrations the project's astryx.config names, not integrations loaded from dependencies the config does not name. astryx docs use-a-themenow says how to make dark mode the default: passmode="dark"to the root[Theme](/components/Theme). A server-rendered app also sets<html data-theme="dark">, so the first paint is dark.astryx docs --helpshowsastryx docs skillsandastryx docs skills/astryxamong its examples, and thedocscommand reference says whatskillsandskills/<name>read.astryx docs cli/skill-placessays where to keep the Astryx guidance for AI agents: the AGENTS.md block in a project (the default, read by every agent), a project skills folder when a team keeps its guidance as skills, and the computer skill for agents outside a project, with theinit --tocommand, file, and saved record for each place and how each is kept current.astryx init --helplinks to it.- The
themetopic has a section on publishing a theme so other teams can use it (ship it in a package; another team runstheme add <name> --package <package>), in English, dense and Chinese, and its summary no longer calls its steps "sections", so a search for a section or a scoped section theme finds Section and MediaTheme first again. - The agent block and the theme docs send a denser or roomier app to the theme (
astryx experimental theme editor set <name> spacing tight, orroomy), as they send colors, instead of gap and padding changes page by page. - The response types reference says
astryx experimental theme editor showleaveslookout when no picture was taken, as the result does, instead of returning it as null. - The response types reference describes the change result of
astryx experimental theme editor setandundoas it is:missedcounts the misses the change leaves andmissedPartsthe parts they are on, and an undo of a setting listed more than once names the other entries it removed (alsoRemoved). - The agent block and the theme docs say a change to one kind of part (the sidebar, its selected item, the gaps in a form) is a theme change too, not props or styles on one page, and that
astryx experimental theme editor how "<ask>"names theset … --on <part>line for it. - With no app yet, the agent block, the theme docs and
astryx experimental theme --helppoint toastryx experimental theme preview app <dir>, which makes a starter app that shows the theme, instead of building an app by hand. - The export guide says that the exported file's CSS keeps only the web font faces its page, stylesheet or script can use, and that text the file cannot know (typed text, text built from character codes, and dates, numbers and date-field placeholders in the reader's or the page's locale) draws in the next font of its font list.
- The export guide's column-floor advice says a table heading wraps like its cells, so a column's floor must fit the longest word of its heading.
astryx --helpnow describesexportin theexperimentalgroup as "one self-contained HTML file from a page built with Astryx components (not for other pages)". Agents can now tell from the help whatexperimental exportmakes and which pages it is for.- The hero and gallery page templates' call-to-action buttons (Get started, Learn more, Explore in
centered-hero,gallery-hero,product-galleryandside-gallery) are now links to#, so they behave as the links they stand in for instead of doing nothing. The Get started arrows incentered-heroandproduct-gallerynow point toward the end of the line in right-to-left, as ingallery-hero; nothing else changes in layout or styling. - Hook docs for
[useChatDictation](/components/useChatDictation), soastryx hook [useChatDictation](/components/useChatDictation)andastryx searchreturn it, and a[useChatDictation](/components/useChatDictation) — Voice inputexample block: a start and stop control that stays off when the browser has no speech recognition. - Hook docs for
[useChatPasteAsToken](/components/useChatPasteAsToken), soastryx hook [useChatPasteAsToken](/components/useChatPasteAsToken)andastryx searchreturn it, and a[useChatPasteAsToken](/components/useChatPasteAsToken) — Long pasteexample block: a composer that uses a threshold of 40 and a Pasted note label. - Hook docs for
[useSpeechRecognition](/components/useSpeechRecognition), soastryx hook [useSpeechRecognition](/components/useSpeechRecognition)andastryx searchreturn it, and a[useSpeechRecognition](/components/useSpeechRecognition) — Transcriptexample block: a headless control that shows whether the browser can listen and the interim transcript. - Hook docs for
[useSyntaxTheme](/components/useSyntaxTheme), soastryx hook [useSyntaxTheme](/components/useSyntaxTheme)andastryx searchreturn it, and a[useSyntaxTheme](/components/useSyntaxTheme) — Keyword colorexample block: the word const painted with the keyword color of the GitHub Light syntax theme. - The internationalization guide says provider
overrideschange Astryx wording across an app, and that a component is reworded through its own prop for that string, such asplaceholderorcancelLabel. The InternationalizationProvider overrides example applies its override to every Selector in the app, and shows one Selector rewording its own placeholder through its prop. - The IDE page template's description now says what its middle pane is: a single read-only code pane, not tabbed documents.
astryx init --helpis about half as long: each option and exit code keeps what an agent needs to run it (what it writes, what it refuses, the error codes), and the rare cases (file deletion on--remove-agents, the--userlink details, the five soft exit-0 cases) move toastryx docs cli/commands/init.- Markdown's anatomy now says when its Image part shows alternative text: for an empty image URL, while an unsafe URL renders as source text. Its guidance adds two don'ts: plugins cannot cross a Server Component boundary, and Markdown does not sanitize renderer output. Prop docs now describe
density,isStreaming,onLinkClick, andcomponents;inlinePluginskeeps its own description instead of lending it toplugins;contentWidthnames its 680 default; and thecontentAlign="start"description now says inline start instead of left. TheonLinkClickdocs say that a customlinkrenderer does not receive the handler. - The messaging shell template notes what must hold before it is marked ready: build keeps the default app shell for parts and edits whose words the template does not use, and the page-pick model is retrained to include it.
- MetadataListItem's prop docs now list
xstyle,className,style,ref, anddata-testid, and say which element each one reaches: the labeldtwhen the item is side by side, or the wrapper when it is stacked. Thedata-testiddocs say that a side-by-side item puts-labeland-valueon its two cells. - MobileNav's prop docs now list
label,xstyle,className,style,ref, anddata-testid, and thelabeldocs say what names the drawer when it is not set. MobileNav's Chinese and dense prop text now reaches the docs: it was written where the doc compiler does not read it for a doc with two components, so those docs showed the English text. The Chinese text no longer marksisOpenandonOpenChangeas required; inside AppShell the drawer reads them from context. - MobileNavToggle's docs now say every case where it renders nothing: above the mobile breakpoint, without an AppShell mobile context (AppShell's, or an
AppShellMobileContextyou provide), and when AppShell has no mobile navigation (no side or top nav,mobileNav={false}, or amobileNavnode). - MoreMenu's prop docs now list
isMenuOpenand say that withoutsizethe trigger takes the surrounding size (from a SizeProvider, ButtonGroup, or Toolbar), elsemd. The Chinese docs gainisMenuOpenandonOpenChangeand the note on where hostdata-*attributes land. astryx docs layoutandastryx docs tokenscarry the core rules on the namespace page itself: layout names the frame, structure, spacing and breakpoint rules with a three-region example, and tokens shows the StyleX import and the tokens most code needs, so one read is enough to start.- NavHeadingMenu's docs now document NavHeadingMenuItem and its props (
label,description,icon,href,onClick,isDisabled,ref,xstyle), addrefto the menu, and say thatminWidthwins over the size's minimum width. New best practices name the WAI-ARIA menu pattern and its keys, say to name a standalone menu, and explain how a disabled row stays reachable. - The npm descriptions of
@astryxdesign/coreand@astryxdesign/cliname Astryx, so a search for "astryx" on npm lists them with the other Astryx packages. - The install page now says that registry calls use Astryx's own short retry and timeout, not npm's fetch-retry or fetch-timeout settings: one retry after a 2-second wait, and at most 30 seconds per request.
- A new experimental guide,
astryx docs cli/experimental/share-a-page, walks through making a shareable page: write it with Astryx components, render it to one HTML file, share or upload that file, and turn the file back into source to change it. - The shareable-page guide (
astryx docs cli/experimental/share-a-page) names the layouts that go wrong on a phone in a file with no script, and how to write each one: a Badge beside text in an HStack (StackItemstaticandfill, as its example now does), a Badge on its own line in a VStack (<[StackItem](/components/StackItem) crossAlignSelf="start">), a long string ListItem label (pass an element), and a table wider than the screen (the file cannot scroll it sideways: keep it within about 310 px with shares that match the floors orpixel()columns, each floor fitting its column's longest word and header, padding included). It also suggestsisWrapped, which shows long CodeBlock lines whole.astryx experimental render --helpand its doc now point to the guide. - Some controls in the app shell page templates did nothing when clicked. Now
shell-nav's Run project and Share,shell-top-nav's Search products, Sign in and Checkout, and intheme-showcasethe chat's Export, Close, Attach and Voice input buttons, Add item, the list and grid view buttons, and the inventory row menu's Edit, Duplicate and Move to each show a toast saying what the real app would do there ("Demo: … would … here"). No layout or styling changes. astryx docs layoutand the scaffold guide say that a short form keeps its own 640 column, even when the page starts from a template with a wide frame or a multi-column grid.astryx docs stylingandastryx docs typographystate their core rules on the namespace page itself, with one short example each, so one read is enough to start; each page still points to its guides for the details.- The table page templates now give their dead buttons and menu items a behavior: in
table-inbox,table-tree,table-grouped,table-pageandtable-filter, the buttons and menu items that did nothing now either work or show a toast saying what the real app would do there ("Demo: … would … here"), and toasts that claimed an action had happened now say it would happen. Delete actions are left unwired on purpose, because a destructive action needs a confirm step these templates do not have. Text fields, form inputs and some menus are not part of this change. No layout or styling changes. astryx theme remove --helpstates its exit codes plainly: removing the only added theme exits 0, removes the generated module and prints the lines the app root must drop; removing the default fails only while other themes are still added, and the line says to choose another default withtheme usefirst. Agents read the old line, "is the default while other themes are added", as "the default can never be removed" and added a theme nobody asked for.- The tool page templates now give their dead buttons and menu items a behavior: in
canvas-editor,file-explorer,ide,kanban-boardandeditor, the toolbar buttons, menu items and view switch that did nothing now either work or show a toast saying what the real app would do there ("Demo: … would … here"), and toasts that claimed an action had happened now say it would happen. Text fields, form inputs and some menus are not part of this change. In right-to-left layouts, canvas-editor's Undo and Redo arrows now mirror. No other layout or styling changes.
Other Changes
- Internal: the technical documentation template's Copy prompt button uses Core's useClipboard instead of calling the clipboard API directly. Pages look and behave the same.
- Internal: the editor template sizes its sidebar with LayoutPanel's width prop instead of an inline style. Pages look the same.
- Internal: the shell-nav template registers its Cmd+K and Ctrl+K shortcuts with Core's useHotkeys instead of a hand-written key listener. Pages look and behave the same.
- Internal: the docs namespace view and the
astryx docs --depthlist share one rule for the [experimental] mark. Output is the same. - The computer-level skill, the project skill and integration skills render their SKILL.md through one function, so their frontmatter and hash line stay the same shape. The files are byte-for-byte unchanged.
- Internal: a theme-editor source comment names Citation as its example of a title drawn as the part's own text. Consumers see no change.
Contributors
Thanks to everyone who contributed to this release:
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 insrc/themes/<theme>/is written exactly astheme buildof its source writes it (the build header names that source), sotheme build --checkandastryx doctorread 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 insrc/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, andwiringthen 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
fonton a part (small,1rem,700) is suggested asfont-sizeorfont-weight, never as a family. - A relative color that keeps its channels (
rgb(from red r g b)) andlight-dark()with the same color twice are read as that color. Acolor-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.
- The editor also reads the current specifications' grammar from
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.5emand150%suggest1.5. headingsin other letters or as a weight number suggests the word meant (BOLDis bold), and a weight number the nearest weight rung (800and900are 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 moreorlessat 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 boldis size 1rem with the family bold).
- A negative percentage the current CSS grammar ranges at 0 or more is refused on a part (
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-1and1.5EMare numbers, and acolor-mix()share like50.%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.
- 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 (
astryx experimental theme editor: weights on phones, and values read as CSS reads them. (#11419)- Heading and text weights (the
headingsweight dial,--text-*-weighttokens) 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.pxandrgb(255. 0 0)are refused (with1pxsuggested where that is all), and+4pxand4e+1pxare taken. vibrancysuggests the value meant (MOREis more,70%and7e1are 70), and no value when the theme has no color to saturate.- The
headingsresult lists its weights in words, not[object Object]. - The whole-theme and role
fonttake 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.
- Heading and text weights (the
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). Avar()fallback is checked wherever it sits (insidecalc(),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), andtext-size 20px,2e1,+20and1.25remsuggesttext-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
fontdial thatsetwould refuse (a CSS keyword such asinherit, 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 pxand16pxxsuggest16px,1,5remsuggests1.5rem.text-sizesuggests the nearest size it takes:20 pxand125%are 20, and a size past either end is that end.
- A part value's
astryx experimental theme editor:font mathis accepted as the CSS generic family it is; the generic families are read from the CSS grammar. With an exact--font-size-baseset,how 'bigger text'steps that token (14px to 17.5px) instead of offering atext-sizethe 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.setrefuses avar()loop that closes through a token in the theme's own<theme>.theme.ts.shownotes 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'sfont-familyis 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.
- An exact token refused only for how its value was typed (a trailing
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
showand 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: pointersets 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.
NaNpxandInfinitypxare refused as not numbers;1e3pxis 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-2is a 2px border width androunded-fulla 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, asset,showandundodo. (#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-mutedis 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--andX: offsay 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)undoleaves 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.showbuilds 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
setandshow. corners 2e1pxand+4pxare sizes. A state is refused for padding on a part whose padding Core sets from the plain value only.--state disabledalso matches a wrapper whose input inside is the one disabled.how <part>lists the statessettakes there.newsuggestions keep every option given;--liketwice is refused. More suggestions run as printed in JSON. The merge snippet's paths start from the generated themes module's folder. The help namesexperimental theme compileto 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 (--onlykeeps it to one member of a group).focus-withinis taken on a part that holds content. A one-mode value that is not a color is refused for that reason first. (#11378)showleaves 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:showbuilds a change in a module the theme source imports, and an unreadable build with a broken source line says what to put back.compileof an editor theme from a subfolder names the run from the app root.--state disabledreaches 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 Cornersreads the setting name in any case, and a near name (undo t corner) suggestsundo t corners, never a bareundo tthat 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 redsuggests--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 saysundosteps back to the settings from before the last change, and that the last change itself is not kept. A correctednewkeeps every other option given, with--likein another case read as the built-in theme it names. (#11378)astryx experimental theme editor:--state disabledreaches the control inside only on a part that holds one control (a typeahead), never a radio list, input group or field.corners none,sharp,zeroand0%are square;spacing nonenames the tightest rung. Undoing a part's state setting names the group's setting for the same state.focus-withinis 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.jscounts when onlyx.tsexists. Asetrefused 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 namenewtakes (my-neutralfor 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.newon an existing theme suggestsset <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,setandundosay the token changes are not listed, and never that the change shows nothing. (#11419)astryx experimental theme editor showfollows every local file the theme source reads, as the build resolves it (./toktotok/index.tsx,./c.cjstoc.cts,./j.jsxtoj.tsx), including your own files in the theme'stokens/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 templatein 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.undorefuses an--onlythe setting was not made with, matches a value whatever its comma spacing (rgb(255,0,0)), andundo <theme> mode/basesays 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, andshowno longer says it built a theme its source cannot carry. (#11419)astryx experimental theme editor: a bare number on a length (padding 4) suggests4pxwith every flag kept, never the property's reset value. A part named by its class (.astryx-card) or its component (<[Card](/components/Card)>) suggests the part. What the buttons and surfaces dials write is read from the build, so an exact property under them is named insetandshow, and undoing it names the dial that applies. An unknown state suggests the one meant (pressedis 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 withrequire()orimport 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 checkboxesnames the checks group ashowdoes.corners sharperandspacing roomierstep from the value now. A state in another spelling (focusVisible,focus_visible) is that state.Whenthemesin 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 … --overwritenever replaces a theme editor file under another spelling of its name (themes/t/T.theme.tson a case-insensitive disk, or through a link).undo <theme> modeorbaseon 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
basesuggests 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--likeorbasesuggests only a base the app has installed, and with none near,base noneand the installed bases.undo <theme> baseormodeafter a change and its reverse says it is back at the value the theme was made with.newrefuses 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, andundobrings them back. A hand-edited part property value its CSS grammar refuses is named, like a dial's.showbuilds again when an output is missing or was edited by hand, ascompile --checkfinds them. (#11419) When your own<theme>.theme.tsdoes not parse,set,undoandshowrefuse before writing or removing anything (the palette files undertokens/stay), withcatof the file; a failed change that removed thetokens/folder puts it back. A build temp file left by a command stopped mid-build is swept after ten minutes.astryx experimental theme editor showrenders 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, inshowandcompilealike. 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 (andcompilerefuses 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 andls -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)../tand.\tname the themet. 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 smallreadscornersas the theme), with its usage and--help. (#11419)astryx experimental theme editor: a settings file whoseliftedfield 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.tssets itself, which wins over the dial, so a change that does not show is explained. (#11419)astryx experimental theme editor showrenders 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 withls -la <file>, never with an--outthe 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), andnewwith the typed name only after. An empty theme name ('',-, an unset variable) says the name is empty and names the themes here instead ofnew my-theme. (#11419)astryx experimental theme editor: a token your own<theme>.theme.tssets 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-leveltokensdo. A preview page with text added after its render stamp is rendered again. Theeditor showdocs 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 inshow(two copies of React, a component that throws) is refused withdoctorand "Nothing was written" wherever it happens; outputs thatshowmade 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 apackage.jsonof their own are refused, naming the workspace's apps that use Core with thecdto run from, so no theme lands outside an app.undo <theme> radius-elementandundo <theme> paddingsuggest 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__,toStringand the like), given as a value, a scope, a state, a flag or ahowquestion, gets the same refusal as any other unknown word instead of anERR_UNKNOWNcrash. Every word table the editor reads with typed text now answers only for its own entries. (#11419)astryx experimental theme editorfinds 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 thecdto 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-headingis accepted in either order, and the saved settings no longer leaveshowand everysetrefusing; a loop within one part or within the whole theme is still refused. An exact accent (or other fill color) given asvar()of another token, a two-colorlight-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.tsdeleted by hand is written again byshowor the nextset, which say so, andcompileof it suggestseditor show.text-sizeandtypename 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!importantsays it is not used and suggests the value without it, and the font dial reads a pastedGeorgia, serif;or a comment as the font meant. (#11440)astryx experimental theme editorreads the tokens your own<theme>.theme.tssets from what the build made of it, so any way of writing the file counts (a namespace import, a renameddefineTheme, 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 avar()that names no design token (and has no fallback) is named byshowand every later command, with theundothat removes it, assetrefuses it; it is never built. Thefontdial reads any run of spaces or tabs inside a family name as one space, sofont 'Open Sans'names Open Sans. (#11440)astryx experimental theme editor: a Yarn Plug'n'Play workspace (its.pnp.cjsat 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 itscd, never an install into the repository; a suggestednew my-<name>is a free, valid name, and names the user's ownmy-<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 afont:shorthand) is read as the family list it names, for thefontdial and exact font tokens. Avar()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;shownames 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. Aftercompileof an edited theme file,showreads the build as current whencompile --checkwould, instead of building it again. (#11453)astryx experimental theme editor:undo <theme> headings Tracking(orTRACKING,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 sheetsshow --sectionmade as out of date (insheetStale) instead of deleting them; a link in the theme folder whose target is gone is named with where it points, bysetand byundoalike, 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 thefontdial and exact font tokens, with how to load a file (@font-faceor 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, avar()with a fallback as its fallback, andlight-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 of6px, 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--modeis on those tokens, and a font your file sets throughtypographyis seen as the file's. (#11453)astryx experimental theme editor:--pngwrites 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. Anewrefused 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 namesshow <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, soOpen<no-break space>Sansnames Open Sans. A dial's value pasted with its property name (border-radius: pill,font-size: 18px;for text-size,color: #e11d48for 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), byset,showandundoand byexperimental theme compileand--check. A state rule your theme file sets on a part (:hover) is named like a variant: inset,show(with no contrast caveat for a setting that does not show) andundo.compileof a theme whose saved settings hold a value the editor refuses names theundothat 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 asvar(--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 14ptsuggests the size in pixels,type largeortype 18pxsuggests text-size (never corners),modelists 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,showandundosay so and suggestnew <theme>, which makes it there, instead of calling it a theme the editor did not make. (#11468)astryx experimental theme editor:newandshowend withwiring, the steps that put the theme into this app:astryx theme add <theme>for its app copy (a one-mode theme'smodefor the<[Theme](/components/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](/components/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, andexperimental theme compileof 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, andtheme use,removeandlisttake it as any local theme;newandshowsay so inwiring. The first time the copy is written (bynew, or by the first build of a theme made before), the result names its files (appCopyin 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 avar()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, stateHover) 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,removeandejectgiven an editor theme with no app copy yet name the same stepseditor newandshowgive inwiring(build it once, thentheme add <theme>, and a one-mode theme'smodefor the<[Theme](/components/Theme)>). A color change stopped before its settings were saved no longer leaves its color config andtokens/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: adark-onlyorlight-onlytheme keeps both halves of its colors, and its mode is the one the app's<[Theme](/components/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(orlight-only) says to give the app's<[Theme](/components/Theme)>mode="dark"(or"light"), and the wiring aftertheme addsays 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 newends with how to look at the theme after each change:editor show <name> --pngwritesthemes/<name>/preview.pngandsheet.pngfrom real components and changes nothing in the app; open the pictures and check them against what was asked. (#11500)astryx experimental theme editorreads the page-wide tokens of your own<theme>.theme.tshowever they are written (inline, a const, a spread,as constorsatisfies), from thedefineThemethe build loads, never a sibling theme in the same file; a value it cannot read in the file comes from the build. Theexperimental theme template --overwriteandcompile --outhelp 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 (
overflowkeepsoverflow-wrap,transformkeepstransform-origin,flexkeepsflex-direction), and a part'sbackgroundkeeps reaching its variants whenbackground-blend-modecomes 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,tabsand other plurals name the part, with the set command.- Word hints keep the value given:
shadow noneisbox-shadow none,rounded 8pxiscorners 8px,bold falseisfont-weight normal.
- A shorthand set after its longhands replaces only the longhands it really sets, read from MDN's data (
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.
- 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:
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-colorfor the destructive button after a baseborder).
- 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 (
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)paddingon 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
paddingshorthand'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.
paddingon chat-composer takes one length, as Core reads it inside calc(): a length, a variable such asvar(--spacing-3)(Core's own default), orcalc(),min(),max()orclamp()giving one. Several values, a bare number or a percentage is refused with one that works.
- 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
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
--stateon 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
0is written as0pxon parts where Core calculates with it (card, section, dialog, drawer, bottom-sheet);initialandunsetleave the padding to Core's own default. - A hand edit to the settings file that
setwould refuse is reported by the nextsetwith the command that removes it, ascompiledoes, 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 as0px;initialandunsetname the part's own default padding from Core. - A hand-edited padding on one part is reported when a
setchanges padding on another part too.
- 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
compileandcompile --checkpass. - 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.
- 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
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.tssets on a part's plain rule, a variant or a state wins over an editor padding there (padding 20px --on cardunder 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(andrevert) on parts whose padding Core keeps in its own variables is taken likeinitialandunset, and the result names the default it means.
- A padding your
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 tighton Neutral gives 24px, 27px and 30px, where small and medium both ended at 24px). The dial's help says control heights follow it.
- 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 (
astryx experimental theme editor: every picture--pngtakes 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. Anewrefused for its name leaves out of its suggestion a vibrancy that would change nothing (no color given), and says so. The--pnghelp 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 withnoUncheckedIndexedAccess,noImplicitOverrideandnoUnusedLocals.add --pathrefuses 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, andCOM¹-style device names. The free folder a URL conflict suggests is one whose URL no other page serves.preview appleaves 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. Theseeline after an editor change now leads with a look that changes nothing in the app (the editor's ownpreview.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 onnoUncheckedIndexedAccess, 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 undopoints itsseeline 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, byseeand bypreview list, instead of suggesting a new one.preview add --themetakes a pasted label (theme: t,name: t) as the theme t; an editor command given one refuses it and suggestsshow t. A change the editor could not render says why in itsseeline instead of pointing at apreview.htmlit 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 colorson a theme with no generated colors says how to get them.preview listmarks a page whose file is gone and notes a change that was stopped part way, andaddwrites a missing page back as added. Running a stoppedpreview removeagain finishes it and exits 0.basePathis certain only when set as a literal on the exported config at the top of next.config; one set in anifor 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 stopsnext buildwhen Components is the first page. next.config is read the way Next loads it:.jsbefore.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:addrebuilds the theme whenever its build is not current (an output missing, or a build that does not match the settings), the same rulepreview appuses, so the route never imports a missing file. A pasted--theme 'theme: t'names the theme t. AdistDirwith a subfolder blocks only that folder.remove --pathon a folder with no preview names the preview there is, with its remove. Thepreview apphelp says that with--themeCore 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,listandappgive each page's URL. Every editor change carries aseeline: first a look that changes nothing in the app (the editor'spreview.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--pnghelp says it needs a Playwright or a Chrome and adds a few seconds. (#11490)astryx experimental theme preview: a--paththat 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 forpreview appand for a--pathoutside the routes folder too.preview removeleaves 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 colorseton a theme whose preview has no Colors page says whichpreview addadds it.preview removetakes away the empty folders the preview's firstaddmade, never one that was there before. The Overview reads its font line again when the theme changes while the page is open. Thepreview appstarter lists@types/node, so its firstnpm run devinstalls 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--templatecommand. 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--pathinto each, and a--paththat 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 pagebuildranks 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 rootstyles/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()andrequire()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|colorsadds 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 namespreview removefor a preview already inside. Atheme-preview.jsonentry that leads outside the folder (../) is reported as damaged byaddandlist.removedrops 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 withnoUnusedLocalsbuild. A refused--themesays exactly what leaving it out does in this app: the theme the preview keeps wearing, or the one theme underthemes/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 removerefuses 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 listwith no preview says whyaddwould refuse the folder instead of suggesting it.removetakes away the empty foldersaddmade outside the routes folder too. Every page-template list suggestion names the command the way the app runs the CLI, in--jsonas 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 onfont systemor its own fonts fetches nothing it does not use.preview addnames every page it writes again, the Colors page included, when the preview switches theme. (#11419)astryx experimental theme preview:add --pathrefuses 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 thepreview appstarter, so the Overview shows the family it names.preview listtext 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, andhowreads "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. showwhose render fails puts back every output it touched, removing one it made new and restoring the palette files intokens/.how "not dark enough"/"not light enough"asks for darker or lighter, not for one mode.
- 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 (
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-leftorpadding-rightset beside another side, as a keyword (initial) or as math (calc()), reaches that side. showwhose render fails leaves a folder you put intokens/alone.- When another command holds the theme, the suggestion to run again names the call's own command with every option it got (
--only,--likeand each dial ofnew,--png), never the arguments of the process the API runs in; a preview command waiting on another namespreview list.
- A card
astryx experimental theme editor: everyseta refusal suggests is now checked the waysetchecks it, without writing anything, and a suggestionsetwould refuse is left out. Suggestions carry what was asked instead of a fixed example.headings light --on headingoffersheadings lightand weight 300 on one level.text-size large --on cardoffers that size on the card. A number token reads the number meant (700pxis 700,1,5is 1.5,calc(1rem+2px)gets its spaces). A word dial given a number offers its own words, or the nearesttypepreset for a scale ratio. An invalid color is never copied into the text color token. A color property refuses avar()fallback insidecolor-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>writesexperimental.iconVariantbesideexperimental.iconSet, in one write, and refuses a variant the main set does not declare; without--variantit 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) addsvariant,previousVariant,looks, andthemeMap. A copied template imports each icon in that look where its set has it, reports the look asicons.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), andintegration checkholds it tomap.astryx doctorfails when the main set does not declare the variant, andexperimental icon --listshows the variant and each set's look. A CLI before 0.7.16 refuses an astryx.config that setsexperimental.iconVariant, sousewarns 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, failsintegration checkuntil it runsexperimental icon add --variant <variant> --from <module> --allagain; the finding names that run. Projects that do not setexperimental.iconSetsee no change. (#11499) astryx experimental theme editorcounts a base theme as installed only when the project installs it, in itsnode_modulesfolders or through Yarn Plug'n'Play, as the app's bundler sees it. A theme found only throughNODE_PATHor Node's global folders is no longer taken as installed:newandset baseoffer to install it instead of writing a theme the app could not build. (#11444)
New Features
astryx doctorwarns when the@astryxdesign/corepeer range of a loaded integration, other than the packages of added themes, whichtheme-core-peersalready 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. Asetupexample 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. Inastryx component <Name> --json, every example carries itskind. Any other value fails to load with a message that names both kinds.astryx docs authoringexplains when to usesetup. (#11434) - Add Table infinite loading with
[useTableInfiniteScroll](/components/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 buildstarts 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
cdto the nearest existing folder (text and--json, codeERR_PROJECT_REQUIRED) instead of a stack trace;--help,--versionanddocsstill 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 dandtheme 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--jsonenvelope 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 documentedout,check, andiconsSpecifieroptions; whattheme buildhands a batch, family, or package-check build now travels through the CLI's own internal path, sotheme buildandintegration pack-checkbehave 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 validateandastryx integration checkname 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,doctorortemplate --listfail until the folder was cleared. (#11474) astryx theme palette generateandgenerateTonalPalette()honordarkChromaTaper, 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 keepsedgeMultiplierof its in-gamut chroma throughthroughStop, then recovers along a smoothstep to the standard recipe atrecoverAtStop;familyMultiplierssets 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 rendersays 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--familyand--family-keyin 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 thecdone), so the suggested check reads the output you asked about. (Minimal change to shared code:buildSuggestiongains an optional shape for a glob or a family run, and the build command passes--outto a group's preflight.) (#11461)- On Windows,
astryx theme buildprints 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 droppedsrc/, so the snippet readimport { oceanTheme } from './\themes\ocean/ocean';, which is not a valid specifier (and\tis a tab in a JS string). It now reads./themes/ocean/oceanon every platform. (#11288) - From a project subfolder,
theme templateandtheme ejectprint a build step that works from that folder (cd ../.. && … theme build theme.template.tswhen the file is above it), and a blank template path is refused withtheme 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 --outwarns that it replaces another source's output only once every output may be written, reads a backslash in--outas 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 withtheme buildstill works, as released, and now warns (once per--watchsession), namingexperimental 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(orexperimental 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,--outand--icons-specifierit 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(andexperimental 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 asthemes/ocean/ocean, is imported as../themes/ocean/ocean, not./themes/ocean/ocean, which does not resolve from src/. Thetheme build --familysnippet uses the same paths and says the same thing in its header. (#11471) theme buildandexperimental theme compilerefuse a theme that sets a private--_*variable: the build fails withERR_THEME_INVALID(exit 1, a JSON error envelope) and writes nothing, a--checkincluded. 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 templaterun from a folder inside a project reads its path from that folder within the project root, and with no path writestheme.template.tsat the project root, as its help says; a backslash in the path separates folders, as fortheme eject;astryx init --features theme, run below the project root, writestheme.template.tsat that root too, because it uses the same template step. Outside any project (nopackage.jsonin 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, ornpm init -yfirst);--jsonstays silent. A staletheme build --check(andexperimental theme compile --check) result carriescode: "ERR_THEME_STALE"besideupToDate: false, the code it exits 1 with. A file at an--outpath that the build did not write is left alone with its real reason and, when one exists, an--outpath 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.--outinto 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);--jsonstays silent, and--watchprints it once per session, not on every rebuild. (#11389)theme build --check(andexperimental theme compile --check) names every output the build writes as checked, the.css.d.tsstylesheet types too. When the only missing output is a.css.d.tsstub, 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;--jsonstays silent and the result is unchanged. Every output the check failed on before still fails it, a missing.d.tsor.variants.d.tsincluded.theme ejectinto a subfolder of a folder the theme editor made (themes/g/sub, wherethemes/g/g.settings.jsonexists) 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);--jsonstays silent and the receipt is unchanged. (#11410)- The dashboard page template typechecks in an app with
noUncheckedIndexedAccess(it renders the same), soexperimental theme preview add --template dashboardno longer adds a type error to a strict app.themeBuild()no longer takes internal hand-off options fortheme build --watchor the private-var exit code;--watchstill warns once per session about a theme editor folder. (#11420) astryx theme template --overwriteno 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
dependenciesentry or a peer not marked optional) is missing (a broken install) is now reported as that package's integration issue:component,template,theme,discoverandsearchprint the usual one-line warning, anddoctor'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 --listused to answer "unknown option"). (#11486) - A dry run of
astryx upgradeno longer tells you to review a.astryx-conflictfile it has not written. When a copied ShadCN composition conflicts with a newer release, the dry run now says that--applywrites 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,
docskeeps the integration check results it gathers, with the theme records they include, so a repeateddocscall 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 namesdocsamong the commands that keep what they gather. (#11483) - Once the per-user cache folder exists,
doctorkeeps 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 laterdoctorskips 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, anddoctor --helpno 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,manifestandbloganswer 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 listand 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,themeandsearchskip 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>andbuildskip 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 --listfinds 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
docsanswers about 45 ms sooner anddoctorandtheme listabout 10 ms sooner. An edited or unknown descriptor is parsed as before. Output is unchanged. (#11496) experimental themecommands read each folder of Core's sources once while they build Core's component docs.experimental theme preview appandexperimental theme preview adddo 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 initwrites (its one theme line, which also keeps extending an imported theme before ejecting one to fork it), one added line inastryx 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 thethemecommand's help and summary nameastryx experimental theme editor new <name> --like neutral, theneditor set/editor how,theme add <name>to wire it, andeditor show <name> --pngto look at each change.theme ejectadds 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, elseneutral), andtheme palette generateadds one line,experimental theme editor set <name> accent <color>. (#11500) - Hook docs for
[useOutlineFromDOM](/components/useOutlineFromDOM), soastryx hook [useOutlineFromDOM](/components/useOutlineFromDOM)andastryx searchreturn it, and a[useOutlineFromDOM](/components/useOutlineFromDOM) — Articleexample 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
classNameandstyle, and thelabeldocs say thatposition: 'start'places a label at the inline start of its value, not on the left. (#11391) astryx docs styling/tokens-and-setuphas a Next.js with webpack section. It showsexperimental.optimizePackageImports: ['@astryxdesign/core']innext.config.mjsand recommends a component entry, such as@astryxdesign/core/[Button](/components/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 thatastryx experimental theme preview appcopies has the same setting. No API changes. (#11305)- A new example block shows
[useTableColumnsVirtualization](/components/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.jsonwithout 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-accentand 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 inheritand 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.
- Undo never deletes the generated color file (
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()andround()are accepted where the type they give fits;sqrt(4px)andmod(10px, 3s)are refused.- Which system fonts need no install comes from the list
astryx theme buildwarns by, unchanged; the editor only knows which of them ship on one system. font morenames the commands that work.- Math inside a color is checked too (
rgb(calc(1px) 0 0)is refused), andcolor-mix()needs a share of at least one color.calc(1fr)is refused, since math takes nofr. - 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
fontshorthand 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.
- A dial typed in other letters (
astryx experimental theme editor: per-mode part colors with commas, both-mode values and everycolor()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.
- A part color set for one mode, then the other, keeps a color that holds commas (
astryx experimental theme editor: font shorthands on a part split whole, and color mixes read. (#11350)- A CSS
fontvalue 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 (boldisfont-weight bold), never tofont-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.
- A CSS
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
0is accepted. - An exact
--color-text-secondaryreaches 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. moreorlesspast 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.
- An installed
astryx experimental theme editor: whatsetaccepts 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
!importantor 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.
- A setting that the theme could not load is refused when you set it, such as a font with
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.
filterandbackdrop-filtertake only values the browser reads;filter bananais 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)andpadding 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.
fontrefusesvar()and names the role's token that takes it.font geist-sansis thegeistpreset, andtext-size Mediumsuggestsmedium.- 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 fontno longer says a body font moves the headings.
- Math in
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
howworks 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.
undois suggested only when there is a change to undo. - When
font --on bodyalso changes the heading font (the theme sets no heading font),how fontsays 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=Geistreads 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.
howfrom 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 propertysetaccepts. 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.
- A CSS property named in the question is set as named, with its value checked against the property's grammar:
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" setstext-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-widthand--color-borderon 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.
- A border or outline value is complete or goes to the right longhand: "card border 2px" sets
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 disabledstyles a disabled button, link or tab the way Core marks it (aria-disabledas 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. compileof an editor theme finds the theme from the file, from any folder, and never mistakes asrc/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 moreat pill andlessat square write nothing. A corner word onbuttonsorsurfacesnames the corners dial. - A bad property value suggests a value the property takes (
no-wrap→nowrap), in the same scope. --state disabledis refused on a part that is never marked disabled.focus-withinis refused where nothing inside takes focus.how <part>lists only statessettakes 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 failscompile --check, andpreview app --themecopies a build that matches its settings without building it again.--state disabledon 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
setchecks 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 moreandlessread the base theme's radius in any unit. A saved corners value must be a rung or a pixel size.undo <theme> baseandundo <theme> modego back to what the theme was made with.undo <theme> headings weight|trackingremoves that half. A value given toundois compared assetreads it.undo <theme> <thing> <part>names--on <part>. A blank--on,--when,--stateor--modeis 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
backgroundwins over an olderbackground-coloron 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.tsthat no longer extends its settings is refused, andshowsays so. A built-in theme's name is refused fornew. A theme written by hand or ejected gets a clear refusal from the editor. In both cases the refusal gives a command that works. showrebuilds a damaged build and says so, andshow --section --pngphotographs the section's own sheet. A damagedpalette.config.jsonis made again from the settings, and its text is kept aspalette.config.damaged.json. The preview route compiles for names likeb-2.preview.htmlis 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--jsonwith its help.--detail compactand--denseprint the status line alone.compilerefuses the editor's own settings files and--familyfor an editor theme.compile --checkchecks an editor theme by the editor's rules, and waits for a change in progress. The editor's builds write the same headers ascompile. Compile errors and stale checks name the experimental commands and never change text that you typed.add,use,removeandejectexplain what an editor theme is.
- Saved settings are checked on load as
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
showmarks the part setting as not shown. - A word for a value names that value (
surfaces elevatedsuggests raised).how baselists 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,
showstill 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.
compileholds 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.
- 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.
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
showreports the radius the build writes. - CSS values are checked against the property's grammar, so valid values such as
12pt,stretchandenv()are taken, a value that is only avar()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-treefor these checks. It adds about 2.09 MB unpacked to the install (css-tree 1.36 MB and itsmdn-data0.73 MB), and loads only when the editor checks a CSS value; no other command loads it, and startup is unchanged. showsuggests installing React only when React is missing, and the busy message says how long the other command has held the lock.
- 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
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 bynewwith its name. Your own files stay, the damaged file is kept, andundosteps back to the earlier settings. showrebuilds 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:
newwith the theme's name makes it again and keeps the file. Anewthat 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.
showworks 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 --watchbuilds an editor theme again.
- Settings of the wrong shape are recovered like damaged ones:
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 stoppednew'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
--statethat a part never takes (disabled on a card, which is never marked disabled) is refused and says what to do. undonames 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.
- The undo history is never deleted by a recovering
astryx experimental theme preview:addrefuses a folder whose URL the app's own route handler or page already serves, including aroute.tsorpage.jsxin the folder itself and aroute.tsin a route group.add --pathandapprefuse Next's build folder (.next/,out/or thedistDirnext.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. ApageExtensionslist built from a spread no longer refuses the app; the result notes that only running the config tells.basePathanddistDirare 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 addornpx install. - A change stopped before its route was written is undone, so
listshows only the pages the route shows. A refusal says what finishing a stopped change wrote.editor setnames 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 --pathat a folder that holds the app suggests a plainremove.- Suggested
--pathandpreview appfolders are written from the folder the command ran in. preview app -appsays to put the folder after--.
- Install suggestions name npm when nothing says which package manager the app uses, never
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.basePathis 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.
--pathat the project root, insrc/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
removestops, deleting nothing, whenpage.tsxwas changed by hand, since it imports the pages. - A formatter run no longer counts as a change by hand.
editor setandshowname 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 --themewaits 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,howanswers 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 listmarks a theme whose folder is gone (themeMissing). After a damaged step record, a page file in no record is named, never deleted.--pngwith 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)removedeletes 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.addrefuses a folder that holds a package.json, a URL another page already serves, an app whose next.config leaves outtsxpage files,src/app/whileapp/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 showandpreview apprun 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.
listsays when the theme is gone. Base themes count as package themes, installed or not.--templatetakes any case.preview apprefusespublic/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 nextpreview addorpreview 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 appprintscd ./-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 thebasePathnext.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 whosepageExtensionsleaves outtsxnow suggests commands: the same add oncetsxis listed, orpreview appfor a new app of its own. (#11350)astryx experimental theme editorreads 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 listastryx theme buildalready uses. (#11350)- Six newer standard properties (
timeline-trigger-rangeand its relatives) are accepted. An outline style in capitals (SOLID) is accepted.
- Six newer standard properties (
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 nologo, the check uses package.jsonmarketplace.logo.astryx integration checkadds 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, andpackage_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--strictor--next. The new "Get your package ready to list" section ofastryx docs authoring/ship/checksshows how to add both. (#11278) integration verifyadds an information line, in text output only, after a successful pack whose manifest isastryx.integration.ts: the CLI transpiles it on first read on each machine, so shippingastryx.integration.mjsloads faster (pointing atastryx 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 plainastryxcommand 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/jition Linux,~/Library/Caches/astryx/jition 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
searchorbuildkept 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 plainastryxrun kept: it gathers every time, asdoctorsays, 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 swizzlereportsERR_WRITE_FAILEDwhen 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 --outwarns, 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--checkagrees with it from every folder; the source a header names is matched exactly. Builds to the default paths beside the source are unchanged. An--outpath that does not end in.cssstill 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 aftertheme ejectandtheme templatequote their paths, andtheme templateon a file--overwritewould refuse names a free path instead (its receipt addsoverwritableandalternative). A damaged generated theme module names how to rebuild it (delete it, thentheme addeach theme it held), a default that is not added namestheme usewith an added theme, and a folder where the module goes is refused in plain words. A--familymember 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 buildandtheme listnames a command that works.theme useandtheme removeof a theme that is not added suggesttheme add <slug>only when that theme exists, andtheme listotherwise; removing the default namestheme usewith another added theme. Unknown slugs intheme addandtheme ejectsuggest whole commands for the closest themes,theme targetswith 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 intheme build, without absolute paths, and indoctor, followed by the rebuild command of any other stale local theme.theme useortheme removeof a theme that is not added and that more than one package provides namestheme add <slug> --package <package>for each.theme build --checktext lists the checked outputs, as the JSON does. (#11346) theme buildrefuses one of its own outputs (.css,.d.ts,.js) or a file of a kind no theme module has (a plain.cssfile) 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 ejectfrom a subfolder forks into the project'ssrc/themes, astheme listandtheme addread it, and reads a relative path from the working folder.theme targets .astryx-switchreads the class as the output prints it. Theexperimental themecopies no longer reword text you typed that holdsastryx theme …. (#11323)theme build --watch(andexperimental 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 ejectrefuses the local themes folder itself, which madetheme listandtheme addfail 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), sotheme list,theme buildandtheme addfind it as that theme; a backslash in its path separates folders.--packageontheme add,theme listandtheme ejectalso 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 ofthemeorexperimentalsuggests whole commands, closest first, andtheme editor/theme previewpoint atexperimental 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
buildkeeps 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
searchandbuildstart a little faster. Every answer is the same. (#11316) component,template,theme,discoverandsearchkeep 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)searchandbuildkeep 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;doctorlists the folder and its size, and deleting the folder clears it. (#11251)searchkeeps 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/parseronly when it parses a contribution's source, so a run where nothing else loads the parser, such ascomponent <Name> --jsonorhook --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 --jsonno longer loads the theme API, which onlycomponent's text output needs, so commands that never need them start faster. Every command prints the same output. (#11242) search(andbuild, 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,themeanddiscoverno 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.
searchandbuildprint the same output faster. (#11240) astryx manifestreads 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 loadsmanifestprints 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)doctorreads 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'sdoctorreports the same thing. (#11232)buildreads 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 --froma 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)upgradeskips 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](/components/useThemeName), soastryx hook [useThemeName](/components/useThemeName)andastryx searchreturn it, and a[useThemeName](/components/useThemeName) — Active themeexample 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
refdocs now say that the ref reaches the list element, with or without a header. (#11277) astryx docs authoring/ship/publishingrecommends shippingastryx.integration.mjsrather than.ts(and.mjsdoc 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
pnpmdirectly, which Windows installs as apnpm.cmdbatch file that cannot start without a shell, so the setup stopped withspawnSync pnpm ENOENTbefore any test ran. It now runs the build throughcmd.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 discoverlists[WeightedSVGIcon](/components/WeightedSVGIcon)among@astryxdesign/lab's components: an experimental SVG icon whose drawing follows the surrounding font-weight. (#7918)astryx experimental theme editor howanswers 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.jsonare 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 …)andcolor(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--onsuggests what the part really reads. vibrancy moreat 100 andlessat 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 withundoorset, 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 fromeditor 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 newvibrancy <0-100>setting (more/lessstep 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 assetand applied in one build. The experimental copyexperimental theme palette generateis gone;theme palette generateis unchanged, andeditor setlists it as the command it replaces. Help, results and errors say "colors" and "shades" instead of palette, family and stop;showlists each color with its seed and the shade each token uses, with the generated files last (colors,colorNotes,vibrancyandcolorFilesreplacepalette). Component families are now groups:how --list groups, and thegroupfield insetandhowresults.how colors(orhow 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 addwith 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 themeand 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|darkand--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, anERR_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.jsonholds the settings;<theme>.settings.tsis generated from it;<theme>.theme.tsextends it, is written once, and keeps your own edits; the CSS and JS are built by the same build asastryx 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 containersand--on menusstyle 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), andeditor 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 addwrites one route into the app's routes folder (theme-preview/inapp/orsrc/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 byeditor, 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 thebuildranking picks for it (--top);--templateadds one.preview listandpreview removemanage 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 (--themecopies a theme in for the pages to wear) and prints the install and dev commands. - Experimental copies of
astryx theme.compile(the copy oftheme build),list,add,remove,use,eject,template,targetsandpalette generaterun the same functions with the same flags and JSON. Each experimental command doc names the stable command it will replace in a newreplacesfield, shown in its help as "Will replace: astryx theme build".
- Checked changes.
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,emtracking, numeric weights, written-out shadows and "40px tall" are kept. No color is picked when the question gives none. - "In dark mode" carries
--mode darkto 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--themeare refused, for every subject. The default theme is the one an editor command changed last, not the newest settings file, andthemeChosenBysays 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
howsuggests 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 assetchecks it: a command thatsetwould 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" givescorners 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--whenand--stateflagssettakes, or says why no flag reaches it; lists every statesetaccepts; 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;
--listtakes the kind anywhere, singular or plural,--list=tokensand a filter that starts with--, and refuses--listgiven 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;
--atgives 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. setrefuses 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.
- Every command
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
newleaves no trace. A link anywhere inthemes/or the theme folder is refused, and never followed or removed. A palette.config.json the editor did not write is kept.showfinds 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 asupgradefinds 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 isERR_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 withERR_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 codeERR_THEME_BUSY, naming the lock. - Every name the name check accepts builds (
brand-2). Names are at most 64 characters.newrefuses a link or a file where the theme goes, a stray word, a flag given two values, and an empty--like;--headingstakes a weight and a tracking; a refused flag suggests anewcommand. - Settings edited by hand are checked on load, and so is the step
undogoes back to. A saved value the editor no longer accepts names theundo <theme> <thing>that removes it, and that command works; a stepundogoes 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-sizetakes 10 to 32 pixels.fontrefuses values that would not build.vibrancyis 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.
- 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
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.
--whenmust be one property and value, and on a group it must belong to a member, as--statemust. An empty or repeated--on,--when,--stateor--modeis refused, and so are extra words afterundoandshow.undo <theme> <thing> <value>removes the setting only when that is its value. Scope flags without a thing are refused.undo <theme> baseandundo <theme> modeset them back to their defaults. A stored setting this Core does not know can still be removed.showbuilds the theme again when its settings were edited by hand or built by another CLI;--sectionwritessheet-<section>.html, not over the full sheet, and takes any case. A setting listed twice is refused.spacingscales the base theme's spacing; a corners step starts from the base theme's radius or the whole-theme setting;corners pillkeeps checkboxes square;headingsrefuses--mode;fontrefuses--whenand--stateand 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 inshowgive each mode its own exact value. - The copied
themecommands nameexperimental themecommands in their refusals.editor newandeditor howno 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-mutedwith--when status:erroron a banner,--color-icon-pinkon an icon) is taken. A part name such asconstructoris 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()andcolor-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
undothat 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,undoandshowgive 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
showbuilds 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 newneutral,success,warning,dangerandinfodials) writes the color as a family inthemes/<theme>/palette.config.json, in the shapetheme palette generatereads, and runs the same generator to writetokens/<theme>.palette.tsand 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.showreports the palette, which stop feeds each token, and the contrast behind each choice;how paletteexplains it;undo <theme> accentremoves 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:--onand--modeare refused, with the exact-token command to use instead. (#11134)experimental theme preview addchecks 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 appchecks 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>andeditor showsay near the top when the font's package is not installed, with the exact install line; once it is installed, the nextsetorshowmakes 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.
--pathat the project root, insrc/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
removestops, deleting nothing, whenpage.tsxwas changed by hand, since it imports the pages. - A formatter run no longer counts as a change by hand.
editor setandshowname 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 --themewaits 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 insrc/no longer turns on the Pages Router. A preview an older release wrote intopages/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).
removenames 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. --pathis refused when it is a file, inthemes/,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--templateis refused; a block passed to--templatesays it is not a page and suggests page templates as commands;--topis 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
--themenames the closest editor theme. list,removeandpreview apprefuse 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/ornode_modules/, files, dangling links and odd names are refused; a folder with only.gitcounts 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.gitignorecoversnode_modules, and the open line is quoted.
- Preview pages go in
astryx experimental theme editor how --listis now a switch, as--listis 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--listalone lists the kinds. Reading a built theme no longer writes a temporary file intothemes/<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, andmatchedsays which words of the description it covers; only a description no page relates to is refused, and its suggestions repeat--themeand--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. Settingvibrancynames 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.newlists the mode it applied with the other settings.showprints 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.hownames 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 basepreview addsays which pages were there already and are written again (refreshed).howgives each token a value of its own type (--color-border "<color>",--border-width 1px; only theborderproperty 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.showlists corners or spacing set on a part or group, with what its parts get beside the whole-theme value (partValues).neutralnames the base theme's page background and the command for a white page.typesays what it still sets whenheadingssets weight or tracking;typeandtext-sizekeep 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 frompreview addquote the options they repeat, such as a--pathwith 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.howkeeps the fill when a color word belongs to it ("a dark card with a thin border", "colored buttons with a border").shownames the radius token each part's corners really read. Theneutralnote 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>printssettingandremovedas its JSON does. (#11168)astryx experimental theme: fixes from a full review. (#11173)preview app --themecopies 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--overwriteoption 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), andundosays 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).shownames the radius token each part reads, or says it is unknown.howanswers 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.headingsnow keeps heading weight and letter spacing whatever order it andtypeare set in;typesays what it no longer sets, andshowmarks a setting another one partly hides. A steeptypescale (editorial, display) keeps text below the base size at its standard sizes, so small text stays readable.showlists 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.neutralno longer tints the page background (--color-background-bodystays the base theme's).setaccepts every token a color,type,headings,corners,spacingortext-sizewrites, so a dial's notes never name a tokensetrefuses. When the components cannot be rendered (two copies of React, say),new,setandundosave the change and say "saved, not checked" with the cause and the codeERR_THEME_NOT_CHECKED, instead of failing after writing;howsays what it could not check instead of listing no readers. A font that is not installed names the closest font that needs no install.howanswers 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, andhow --listwith 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 --groupis nowshow --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
documentandshare; a copied template shows a placeholder for each. Only the experimental icon commands, the icon-set lists inintegration checkand Doctor, two icon definitions' search words, and the icon-set guide change. (#11090)- Authoring receipts.
experimental icon new-set,add, andmapend with one line when the set leaves template meanings unmapped: how many there are, the most used first with their template counts, and themapcommand to run. The JSON addstemplateMeanings: {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--setnames, else the project's main set, else the only set of the icon-set package you run it in.--setis now accepted with--definitions.integration check. Each set'siconSetsentry addstemplateMeanings, 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 --frominto a set with no icons says the set was created, not refreshed.add --variant <look> --allnames 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 (fromicon useand 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.saveadds the word "floppy disk", andbankreads "building library" instead of "library".
- Authoring receipts.
- 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'iconsdeclarations, 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, andwallet. 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
keptwith the reason.
- 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:
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 withERR_UNKNOWN_COMPONENTand the same name suggestions, but its message now says the name is an example block, thatastryx template <ExampleName>prints its source, and whichastryx component <Parent> --blockslists it. (#11153)astryx searchno longer counts a component or hook keyword that is another entry's name as a match for that entry, sospinnerlists 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.buildreads keywords as before. (#11162)astryx templateandastryx buildread a template's needs from its real imports only. Words in comments, strings and JSX text no longer count as packages, so templates such asform-wizard,form-wizard-verticalandtable-treeno longer ask you to installNext,Distributionorcanvas-editor. A path alias such as~/libor#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 --overwritereplaces 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 --overwritenever 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>.cssinto the folder; a build never replaces its source, or a file at a path--outnames 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--outnames a file that a CLI before 0.6.7 wrote, the build says so: delete that file and run the same build again. Twotheme add,useorremovecommands at once keep both changes. A theme whose local folder or package is gone no longer blocksuse,addorremoveof other themes; it is left out with a note; one broken local theme folder no longer hides every other theme fromlistandadd.addsays which owner it chose when a local theme shadows a package theme. An option without its value isERR_MISSING_ARGUMENTwith the command's usage, andastryx 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=1turns 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,-handhelpprint 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) searchandbuildread 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;templatedoes 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-shotastryx theme targetsand 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
labelto TopNav andaria-labelto SideNav. SideNav has nolabelprop; it has a translated default name, andaria-labelrenames 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 docssay 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 thatastryx theme listshows the themes that are available. (#11089) - Add hook documentation and interactive table cell truncation example block for
[useTruncation](/components/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 discoverlists 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 declareicons, and the icon-set guide change. (#10959)- Main set and backups.
astryx experimental icon use <main> --backup <set>(repeatable, order kept) writesexperimental.iconSetas a list, the main set first; with no--backupit writes the plain string as before. The receipt addsbackups, the installed sets the list leaves out (unlisted), and the command that adds them (next).experimental icon --listshows theorderand each set'sroleandrank, 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, andusewarns when the project's CLI range admits one. - Copied templates follow the list.
astryx templatetakes 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
MissingIconcomponent 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 inicons.placeholder. - Doctor. With the opt-in, the
icon-setscheck 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 newicon-placeholderscheck 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 checknotes an icon a template imports but does not declare (template_icon_undeclared), in a package whose templates declareicons: 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 --nextand leaves--strictas it was. A generic renderer (a bare[Icon](/components/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.
- Main set and backups.
New Features
- The CLI adds a
BaseTypeaheadMenublock: 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](/components/useDirection), detailing render-time direction handling and CSS logical properties best practices. (#10547) - InternationalizationProvider has a calendar example: the provider's
calendarprop shows a[Calendar](/components/Calendar)and a[DateInput](/components/DateInput)in the Japanese or Buddhist calendar, and the value stays a Gregorian ISO date. Both calendars work withoutTemporal. (#10135)
Contributors
Thanks to everyone who contributed to this release: