Repository navigation
Update Versions - #769
Open
github-actions[bot] wants to merge 1 commit into
Open
Update Versions#769github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
github-actions
Bot
force-pushed
the
changepacks/main
branch
2 times, most recently
from
October 8, 2026 06:20
7652386 to
e97ad4e
Compare
github-actions
Bot
force-pushed
the
changepacks/main
branch
18 times, most recently
from
October 24, 2026 12:29
91cef8f to
f92f58d
Compare
github-actions
Bot
force-pushed
the
changepacks/main
branch
6 times, most recently
from
November 2, 2026 10:59
d7cc06b to
aacd59c
Compare
github-actions
Bot
force-pushed
the
changepacks/main
branch
4 times, most recently
from
November 14, 2026 11:12
c8f5311 to
ae27cf3
Compare
github-actions
Bot
force-pushed
the
changepacks/main
branch
7 times, most recently
from
November 17, 2026 03:15
53e1ed5 to
f6ff7a9
Compare
16 of 20 tasks
github-actions
Bot
force-pushed
the
changepacks/main
branch
16 times, most recently
from
November 19, 2026 08:10
ca16ba9 to
c9683fc
Compare
github-actions
Bot
force-pushed
the
changepacks/main
branch
from
November 19, 2026 10:09
c9683fc to
73d63f3
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changepacks
@devup-ui/binding@0.1.0 → 0.2.0 - bindings/devup-ui-binding/package.json
Minor
Patch
v1.0.83, notv1.0.83,). A newlicenseBannerplugin option (defaulttrue) and thesetLicenseBanner/isLicenseBannerengine functions turn the banner off; both engines emit identical output.cssprop now compiles aconstthat chooses among style objects, as inconst rules = on ? { color: 'red' } : { color: 'blue' }; <div css={rules} />. Before, it becameclassName={rules}with no CSS. When onlycssprops read the binding, each object (or array, or CSS text) compiles in the declaration to the classes Emotion would give it, with numbers read aspxas Emotion reads them. The choice with? :,&&,||or??still runs at runtime.&&gives an empty class when its test is falsy. The prop reports a build error instead of passing on a class in two cases: when other code also reads such a binding, and when it reads what a call to a function of the module returning a style object gives. A parameter, or a call the build cannot see into, is still passed on as a class.cxmerges the styles of classescss()gives in argument order, socx(blue, red)is red as in Emotion instead of following stylesheet order. New build errors:withComponent()given a target the build cannot render (Section.withComponent(make())), as the styled component compiles to a plain function with nowithComponent; an@emotion/reactimport with no Devup UI equivalent (ThemeContext,withEmotionCache, a default or namespace import) while@emotion/reactis aliased, naming the export; and@emotion/css/create-instanceloaded by an import, re-export,require()orimport()while@emotion/cssis aliasedcreateSession(),selectSession(id)anddropSession(id)exports on the WASM and native engines: a session is an engine state of its own (numbering, sheet, theme, settings and module resolver), and every call works on the selected one. Session 0 is selected from the start.selectSessionanddropSessionthrow aTypeErrorfor an id that is not an unsigned 32-bit integer, and anErrorfor an unknown session or for dropping session 0css({ borderTopWidth: 2 }, { borderWidth: 1 })keeps onlyborder-width. The boundaries are css() arguments, a spread among Box props or style object keys (a prop after a spread, a later spread), and css()/styled composition. Within one level, the keys of one object literal (css(), styled objects, each nested selector or breakpoint object) or the Box props between two spreads, key order is no "later wins" signal: both are kept and the sheet, which writes a longhand after its shorthands, lets the longhand win, socss({ borderTopWidth: 2, borderWidth: 1 })keeps border-top-width and<Text backgroundClip='text' bg='linear-gradient(...)' />keeps its gradient text. The earlier longhand's atom is dropped only when both are static and unconditional at the same selector, breakpoint, layer and style order; a conditional or dynamic value keeps both and the sheet order decides. globalCss keeps every declaration in the order written. No new build errorsborder-widthcame afterborder-top-widthandplace-itemsafteralign-itemsand the shorthand won. Each property now sorts right after the last shorthand covering it (allfirst); unrelated properties keep their alphabetical order. This applies to every path that writes the sheet: StyleX, Box props, css(), styled and the compat APIs. No new build errors.mdxfilename as the JavaScript module (with or without JSX) an MDX compiler makes of it instead of rejecting the extension, the Vite plugin extracts.mdxin aposttransform, and the webpack and Rsbuild plugins in apostloader; Next.js with Turbopack and the Bun plugin still leave MDX untransformedpathin the engine itself, as WASM does, instead of relying on the JavaScript adapter alone: both reportmalformed module resolver result:pathmust be a non-empty stringat the import that requested it;before}: StyleXdefineVars(),createTheme(), typed-variable@property,positionTry()andviewTransitionClass()rules, and the variables the runtimecreateTheme()GlobalStyledeclares, now separate declarations with;only between them, as the rest of the generated CSS already does. The CSS is equivalent and slightly smaller.span: {...}and'h1, h2': {...}select descendants instead of styling the element itself or being dropped, a bare pseudo-class, pseudo-element or media shorthand name such ashoverstays that selector as in the selectors prop, and:,::,[and&keys keep applying to the element. Style properties, Devup UI shorthands such asp, string values and JSX props keep their meaning.globalCss, its own stylesheet and the class names handed out in it are dropped, and it leaves the bucket it collapsed into. The engine gainsremoveFile(filename)(native and WASM), which Vite calls on adeletewatch change, webpack and Rsbuild on the removed files of a watch run (webpack watch mode also saves the pruned state), and the Next.js Turbopack coordinator when an edited file is extracted again. Atoms in a stylesheet other files share stay, as nothing records which file added them; they style nothing once no module uses them$tokeninside a responsive array now readsvar(--token)instead of the token's first raw value:px={['8px', null, '$containerX']}showed the mobile16pxat index 2 where the theme sets--containerXto32px, andw={['$containerX']}ignored theme variants such ascompact. The slot still emits one class at its own breakpointstylisPlugins,shouldForwardPropandnamespaceof StyleSheetManager from an aliased package, and spread props on it;stylisPluginsof createCache() from @emotion/cache while @emotion/react or @emotion/styled is aliased, and createCache() options that cannot be read at build time (not an object literal, spread options, a computed key, createCache used other than by calling it, or @emotion/cache loaded other than by an import of its default export). createCache() with literal options such askeystays acceptedshouldForwardPropthe element it renders as its second argument, not v5's validator, so a predicate calling that argument ((prop, valid) => valid(prop)) is now a located build error instead of output that throws at runtime;typeof element === 'string'is read from the target the component is declared with. Conditions an extended component repeats from its base, such as styled-components'theme, are merged once. The build still evaluatesshouldForwardProponly for props it can name (those the styles read and those the predicate names) and adds no code that runs it, so a prop a spread or caller passes reaches the element even when the predicate rejects it; the styled-components migration and limitations docs list this as a known difference.styledcarries astyledComponentIdproperty, set once per file by a small helper, and the compatisStyledComponentreturns true for it as styled-components does instead of always returning falsestylednow pass props on as styled-components v6 does: withoutshouldForwardProp, every prop reaches the rendered element, a DOM tag included, even one the styles read, except$props,asandtheme. Before, a prop the styles read was kept off a tag unless it was a valid HTML attribute, as Emotion does; Emotion's components keep that filtering..withConfig({ shouldForwardProp })still decides, composed with a wrapped styled component's own, and when several.withConfig()calls set it the last one wins, as in styled-components.StyleSheetManager'sshouldForwardPropstays a build error: keep props off the element with$transient props or.withConfig({ shouldForwardProp }).styled['div']andstyled[`div`]compile asstyled.divdoes, in tagged templates and calls and before.attrs/.withConfig, for Emotion, styled-components and Devup UI's ownstyled, keeping Emotion's numbers as pixels. A computed tag the build cannot read (styled[tag]) or that nostyled.member could spell (styled['my-element']) stays a located build error<Global styles>takes acss()class holding rules under selectors, an array of rule objects and classes (false,nullandundefinedskipped) and a function of the theme whosetheme.a.breads becomevar(--a-b); Emotion'stargetand styled-components'componentIdbecome a stable class on the element that extending components render too; and alabel:declaration in CSS text is dropped instead of written as invalid CSS. New build errors: atargetorcomponentIdthat is not one class name written as a string;defaultPropsassigned to a styled component, which compiles to a function component whosedefaultPropsReact 19 ignores; a<Global>class with declarations of its own or rules no plain selector names, a spread in a<Global>array, and a<Global>theme function reading the theme other than astheme.a.bthemeprop given to one element of a styled component whose styles read the theme (<Card theme={{ brand: 'teal' }} />) was kept on the element but never reached its CSS, which reads the theme as CSS variables. New build error: athemeattribute on an element of a styled component whose styles read the theme; wrap the element in aThemeProviderwith that theme instead(size) => ({ width: { default: 100, ':hover': size } })), each condition taking its own variable; a computed condition key may read adefineConsts()constant ([constants.wide]); atypes.*()variable indefineVars()registers@propertywith itsdefaultas the initial value; a'--global'key keeps its name andcolors['--global']reads it;positionTry()andviewTransitionClass()bindings read as their names increate(), two of them in one file no longer share a name, and a dashed ident on an anchor, timeline or position-try property stays a name instead of becomingvar(--name);viewTransitionClass()takes thegroup,imagePair,oldandnewgroups and styles their pseudo-elements. New build errors: atypes.*()variable without adefault,types.integer()given a fraction, an unknowntypes.*helper, and aviewTransitionClass()key other thangroup,imagePair,oldandnewor a group that is not an object of declarations...stylex.include(base.root)instylex.create()now overrides the included one, as StyleX merges them:{ ...stylex.include(s0.a), color: 'blue' }kept both the included red and the blue class, and red could win by stylesheet order. The included namespace's keys are merged where the spread is written, so a later key or a laterinclude()replaces what came before, andstylex.props()resolves such a namespace per key like any other. A dynamic (arrow function) namespace has no keys and is still only prepended. No new build errorsstylex: { styleResolution }, StyleX's babel plugin option of the same name, and the engines take it through the newsetStylexStyleResolution().'property-specificity'stays the default.'application-order'gives a staticstylex.create()key thenullresets StyleX's table lists for the longhands it covers (and reads its aliases,marginStartasmargin-inline-start), so the key applied last wins instylex.props()and within a namespace.'legacy-expand-shorthands'splits a shorthand into its longhands at build time as StyleX's table does (padding: '1px 2px'intopadding-top,padding-inline-end,padding-bottom,padding-inline-start). A later key of a static namespace now replaces an earlier one of the same name. New build errors under the two non-default policies only: a shorthand givenfirstThatWorks()fallbacks,allunderapplication-orderand alistStyleStyleX cannot sort underlegacy-expand-shorthands; an unknownstyleResolutionis a configuration error (StylexConfigError). Devup UI's own APIs ignore the option@stylexjs/stylexoutsidecreate,props,attrs,keyframes,defineVars,createTheme,createThemeContract,defineConsts,positionTry,viewTransitionClass,firstThatWorks,includeandtypes(such aswhen,envordefaultMarker), imported by name or read as a member of the package imported wholewhen.ancestor(),when.descendant(),when.anySibling(),when.siblingBefore(),when.siblingAfter(),defineMarker()anddefaultMarker()at build time, as@stylexjs/babel-plugindoes, instead of reporting them as unsupported: awhen.*()call becomes the:where(...)condition key StyleX writes, its rule writes the class twice to keep a pseudo-class's specificity and sorts before the pseudo-classes in StyleX's order,defaultMarker()is the classx-default-marker, anddefineMarker()names a class after its file and export that importing modules read too.@devup-ui/reacttypeswhen,defineMarker,defaultMarkerand markers inprops(). Pseudo-classes nested in each other are now written in the order StyleX sorts them, so:hoverinside:focusreads:focus:hover. New build errors: awhen.*()call whose pseudo-class is not a string literal starting with:or[(or is a pseudo-element, or an unclosed attribute selector), whose marker is not a marker or a class name, or that names another relation; adefineMarker()call with arguments or not bound to a named export of the module's top level; adefaultMarker()call with argumentscardand a shadowcardboth declared--card, so one replaced the other in:root. New build error:theme: color token 'card' and shadow token 'card' both become the CSS variable --card: rename one, raised when the theme is registered for any two of colors,lengthandshadow(names compared after dots become dashes, sogray.100andgray-100clash too)oxc_sourcemap10, whichoxc_codegen0.159 now uses), napi 3.16 and typescript-eslint 8.73. Extracted CSS and class names are unchanged.@vanilla-extract/css-utilsis aliased by default and itscalccompiles to the strings the package builds (calc.add/subtract/multiply/divide/negate, chainedcalc(x)with.toString()or template interpolation, nested operations only parenthesized). A.css.tsstylesheet evaluates it without a module resolver, so its operands may be anything the stylesheet computes; elsewhere each call is written as its string and its operands must be literals, module-levelconsts holding a literal or othercalcresults.@devup-ui/react/compat/vanilla-extract-css-utilstypes it, and css-utils-literal-only reads its calls as the build does. New build errors: acalcoperand outside a stylesheet the build cannot read, acalcread without being called, acalc(x)used as a value without.toString()(also in a stylesheet), an export other thancalc, and a namespace import,require()or re-export of the package outside a stylesheet. SetimportAliases: { '@vanilla-extract/css-utils': false }to keep the packagestyle(rule, debugId)andstyleVariants(..., debugId)add a class named after the debug ID (root-0-0,tone_primary-0-1) that styles nothing, so the readable class list shows which style it came from; builds without debug are unchanged, andkeyframesstill ignores its debug ID@vanilla-extract/cssis aliased:@vanilla-extract/recipesand@vanilla-extract/sprinklesloaded byexport … from,export *,require(),import x = require()orimport()(an import already was);@vanilla-extract/dynamicloaded in any of these ways; andglobalKeyframesimported from@vanilla-extract/css, which failed with a bareTypeError: not a callable function@devup-ui/binding-darwin-arm64@0.1.0 → 0.2.0 - bindings/devup-ui-binding-darwin-arm64/package.json
Minor
Patch
@devup-ui/binding-darwin-x64@0.1.0 → 0.2.0 - bindings/devup-ui-binding-darwin-x64/package.json
Minor
Patch
@devup-ui/binding-linux-arm64-gnu@0.1.0 → 0.2.0 - bindings/devup-ui-binding-linux-arm64-gnu/package.json
Minor
Patch
@devup-ui/binding-linux-arm64-musl@0.1.0 → 0.2.0 - bindings/devup-ui-binding-linux-arm64-musl/package.json
Minor
Patch
@devup-ui/binding-linux-x64-gnu@0.1.0 → 0.2.0 - bindings/devup-ui-binding-linux-x64-gnu/package.json
Minor
Patch
@devup-ui/binding-linux-x64-musl@0.1.0 → 0.2.0 - bindings/devup-ui-binding-linux-x64-musl/package.json
Minor
Patch
@devup-ui/binding-win32-arm64-msvc@0.1.0 → 0.2.0 - bindings/devup-ui-binding-win32-arm64-msvc/package.json
Minor
Patch
@devup-ui/binding-win32-x64-msvc@0.1.0 → 0.2.0 - bindings/devup-ui-binding-win32-x64-msvc/package.json
Minor
Patch
@devup-ui/wasm@1.0.83 → 1.1.0 - bindings/devup-ui-wasm/package.json
Minor
Patch
Devup.xfor a name the package compiles being read like the named import. New build errors, located at the use: what a barrel re-exports but the build cannot read (an unresolvableexport *or module, a namespace of modules re-exporting the package) is an error where its name is used instead of a runtime crash, and a namespace member read by a key the build cannot know (Devup[key]), written, or destructured in a form it cannot follow (a rest, a computed key, a default value, a nested pattern, an exported declaration, or members mixed with ones that stay at runtime) is an error that names the members to read. A namespace passed on whole (Object.keys(Devup), spyOn(Devup, 'css'), export default Devup) is left as it isg(f(1)).d(3).toString(), no longer overflows the 2 MiB stack of a test thread while Boa parses the instrumented stylesheet. Release builds and the published packages are unchanged. No new build errorsimport { type DefaultTheme, ThemeProvider }now leavesimport type { DefaultTheme }on the package instead of a value import that made it a runtime dependency, and animport typedeclaration is left as written.spin.getName()on akeyframes()binding becomes the generated keyframes name instead of a call on a string that threw at runtimev1.0.83, notv1.0.83,). A newlicenseBannerplugin option (defaulttrue) and thesetLicenseBanner/isLicenseBannerengine functions turn the banner off; both engines emit identical output.cssprop now compiles aconstthat chooses among style objects, as inconst rules = on ? { color: 'red' } : { color: 'blue' }; <div css={rules} />. Before, it becameclassName={rules}with no CSS. When onlycssprops read the binding, each object (or array, or CSS text) compiles in the declaration to the classes Emotion would give it, with numbers read aspxas Emotion reads them. The choice with? :,&&,||or??still runs at runtime.&&gives an empty class when its test is falsy. The prop reports a build error instead of passing on a class in two cases: when other code also reads such a binding, and when it reads what a call to a function of the module returning a style object gives. A parameter, or a call the build cannot see into, is still passed on as a class.&:hover ${Child}] as a rule key) gets a short marker class, which only such components get, and the selector reads it as .marker; a component extending it, or an element inlining it for its css prop, keeps the marker. Selectors written without & now nest under the component as stylis nests them (ul { ... } is & ul, a selector list nests each selector, :hover applies to the component itself) instead of becoming global rules, and rule-object keys starting with ., #, [, *, >, + or ~ are read as nested selectors instead of propertiesimport { CacheProvider } from '@emotion/react'is redirected there instead of keeping @emotion/react as a runtime dependency; the cache it configures holds styles Emotion inserts at runtime, which Devup UI writes at build timebackground: ['red', 'linear-gradient(...)']) declares each value in order as a browser fallback, as those libraries do, instead of being read as Devup UI breakpoints; numbers get px as the library gives them. Arrays holding runtime values stay as writtenp { color: green; }, { p: { color: 'blue' } }]} the later blue wins, where before the class's rules sat outside the layer and always won. No new build errors.${mixin}; color: red;outside the css prop composes the mixin by styles, so a later declaration replaces the mixin's, and a css...template is a known style a later css() composes. Inline css() calls inside css() arguments (css(css({ ... }), { ... }), css(cond && css({ ... }), base)) are composed with the other parts, the later winning, instead of being compiled to a class of their own. No new build errorscxmerges the styles of classescss()gives in argument order, socx(blue, red)is red as in Emotion instead of following stylesheet order. New build errors:withComponent()given a target the build cannot render (Section.withComponent(make())), as the styled component compiles to a plain function with nowithComponent; an@emotion/reactimport with no Devup UI equivalent (ThemeContext,withEmotionCache, a default or namespace import) while@emotion/reactis aliased, naming the export; and@emotion/css/create-instanceloaded by an import, re-export,require()orimport()while@emotion/cssis aliasedcreateSession(),selectSession(id)anddropSession(id)exports on the WASM and native engines: a session is an engine state of its own (numbering, sheet, theme, settings and module resolver), and every call works on the selected one. Session 0 is selected from the start.selectSessionanddropSessionthrow aTypeErrorfor an id that is not an unsigned 32-bit integer, and anErrorfor an unknown session or for dropping session 0export const B = Box,const c = css; export { c as cc },export const D = Devupandexport const C = Devup.cssin a barrel (the barrel module exports them as re-exports of the package, and what imports them follows them),export { Box }after an import,export default Box,const D = Devupnamespace aliases, andconst inner = cssdeclared inside a function. A css() or keyframes() const that a function reads before its declaration compiles. New build error: a css()/keyframes() const read before its declaration runs (outside a function) is located and says to move the declaration above its first readcss({ borderTopWidth: 2 }, { borderWidth: 1 })keeps onlyborder-width. The boundaries are css() arguments, a spread among Box props or style object keys (a prop after a spread, a later spread), and css()/styled composition. Within one level, the keys of one object literal (css(), styled objects, each nested selector or breakpoint object) or the Box props between two spreads, key order is no "later wins" signal: both are kept and the sheet, which writes a longhand after its shorthands, lets the longhand win, socss({ borderTopWidth: 2, borderWidth: 1 })keeps border-top-width and<Text backgroundClip='text' bg='linear-gradient(...)' />keeps its gradient text. The earlier longhand's atom is dropped only when both are static and unconditional at the same selector, breakpoint, layer and style order; a conditional or dynamic value keeps both and the sheet order decides. globalCss keeps every declaration in the order written. No new build errorsborder-widthcame afterborder-top-widthandplace-itemsafteralign-itemsand the shorthand won. Each property now sorts right after the last shorthand covering it (allfirst); unrelated properties keep their alphabetical order. This applies to every path that writes the sheet: StyleX, Box props, css(), styled and the compat APIs. No new build errors.mdxfilename as the JavaScript module (with or without JSX) an MDX compiler makes of it instead of rejecting the extension, the Vite plugin extracts.mdxin aposttransform, and the webpack and Rsbuild plugins in apostloader; Next.js with Turbopack and the Bun plugin still leave MDX untransformedpathin the engine itself, as WASM does, instead of relying on the JavaScript adapter alone: both reportmalformed module resolver result:pathmust be a non-empty stringat the import that requested it;before}: StyleXdefineVars(),createTheme(), typed-variable@property,positionTry()andviewTransitionClass()rules, and the variables the runtimecreateTheme()GlobalStyledeclares, now separate declarations with;only between them, as the rest of the generated CSS already does. The CSS is equivalent and slightly smaller.span: {...}and'h1, h2': {...}select descendants instead of styling the element itself or being dropped, a bare pseudo-class, pseudo-element or media shorthand name such ashoverstays that selector as in the selectors prop, and:,::,[and&keys keep applying to the element. Style properties, Devup UI shorthands such asp, string values and JSX props keep their meaning.globalCss, its own stylesheet and the class names handed out in it are dropped, and it leaves the bucket it collapsed into. The engine gainsremoveFile(filename)(native and WASM), which Vite calls on adeletewatch change, webpack and Rsbuild on the removed files of a watch run (webpack watch mode also saves the pruned state), and the Next.js Turbopack coordinator when an edited file is extracted again. Atoms in a stylesheet other files share stay, as nothing records which file added them; they style nothing once no module uses them$tokeninside a responsive array now readsvar(--token)instead of the token's first raw value:px={['8px', null, '$containerX']}showed the mobile16pxat index 2 where the theme sets--containerXto32px, andw={['$containerX']}ignored theme variants such ascompact. The slot still emits one class at its own breakpointstylisPlugins,shouldForwardPropandnamespaceof StyleSheetManager from an aliased package, and spread props on it;stylisPluginsof createCache() from @emotion/cache while @emotion/react or @emotion/styled is aliased, and createCache() options that cannot be read at build time (not an object literal, spread options, a computed key, createCache used other than by calling it, or @emotion/cache loaded other than by an import of its default export). createCache() with literal options such askeystays accepted&in a styled or css template is scoped to the component instead of becoming a global rule (.child {}and> p {}select descendants,:hover {}and::before {}the component), and a rule nested in a selector list applies under each of its selectors;contentkeeps the quotes of its strings (content: 'x',content: "");paramsgo on the pseudo-class that takes them, so_groupNthChildgives:is(...):nth-child(2n) .aalso when nested; a bareselectorskey is a pseudo-class name, an attribute of the element or a descendant selector ('div p','> p'), under a parent too, and keeps the case of class names;::part(),::slotted(),::highlight(),::picker()and the view-transition pseudo-elements get two colons. New build errors: a_nameprop or selector key that names nothing (_notASelector,selectors={{ div: ... }}), and a string under a selector that is not CSS text (_hover="external-class")shouldForwardPropthe element it renders as its second argument, not v5's validator, so a predicate calling that argument ((prop, valid) => valid(prop)) is now a located build error instead of output that throws at runtime;typeof element === 'string'is read from the target the component is declared with. Conditions an extended component repeats from its base, such as styled-components'theme, are merged once. The build still evaluatesshouldForwardProponly for props it can name (those the styles read and those the predicate names) and adds no code that runs it, so a prop a spread or caller passes reaches the element even when the predicate rejects it; the styled-components migration and limitations docs list this as a known difference.styledcarries astyledComponentIdproperty, set once per file by a small helper, and the compatisStyledComponentreturns true for it as styled-components does instead of always returning falsestylednow pass props on as styled-components v6 does: withoutshouldForwardProp, every prop reaches the rendered element, a DOM tag included, even one the styles read, except$props,asandtheme. Before, a prop the styles read was kept off a tag unless it was a valid HTML attribute, as Emotion does; Emotion's components keep that filtering..withConfig({ shouldForwardProp })still decides, composed with a wrapped styled component's own, and when several.withConfig()calls set it the last one wins, as in styled-components.StyleSheetManager'sshouldForwardPropstays a build error: keep props off the element with$transient props or.withConfig({ shouldForwardProp }).styled['div']andstyled[`div`]compile asstyled.divdoes, in tagged templates and calls and before.attrs/.withConfig, for Emotion, styled-components and Devup UI's ownstyled, keeping Emotion's numbers as pixels. A computed tag the build cannot read (styled[tag]) or that nostyled.member could spell (styled['my-element']) stays a located build error<Global styles>takes acss()class holding rules under selectors, an array of rule objects and classes (false,nullandundefinedskipped) and a function of the theme whosetheme.a.breads becomevar(--a-b); Emotion'stargetand styled-components'componentIdbecome a stable class on the element that extending components render too; and alabel:declaration in CSS text is dropped instead of written as invalid CSS. New build errors: atargetorcomponentIdthat is not one class name written as a string;defaultPropsassigned to a styled component, which compiles to a function component whosedefaultPropsReact 19 ignores; a<Global>class with declarations of its own or rules no plain selector names, a spread in a<Global>array, and a<Global>theme function reading the theme other than astheme.a.b$props,themeand the props their style functions or attrs read are kept away from a tag unless it takes them as attributes, andshouldForwardProp(Emotion options or styled-components withConfig) is evaluated at build time. AshouldForwardPropthe build cannot evaluate is a build error naming the file, line and code, with the forms it accepts. An element using a styled component the file defines drops props the component neither reads nor passes on; spread props are passed as writtenasprop names, defaulting to the tag or component they were defined with, and passforwardedAson asas, as styled-components and Emotion do;asused to reach the rendered tag as an attribute.Component.withComponent(target)on a styled component the file binds to a const builds a component rendering the same styles and attrs astarget(a tag name or a component JSX can name), where it used to call a method the generated function does not have and throwthemeprop given to one element of a styled component whose styles read the theme (<Card theme={{ brand: 'teal' }} />) was kept on the element but never reached its CSS, which reads the theme as CSS variables. New build error: athemeattribute on an element of a styled component whose styles read the theme; wrap the element in aThemeProviderwith that theme instead(size) => ({ width: { default: 100, ':hover': size } })), each condition taking its own variable; a computed condition key may read adefineConsts()constant ([constants.wide]); atypes.*()variable indefineVars()registers@propertywith itsdefaultas the initial value; a'--global'key keeps its name andcolors['--global']reads it;positionTry()andviewTransitionClass()bindings read as their names increate(), two of them in one file no longer share a name, and a dashed ident on an anchor, timeline or position-try property stays a name instead of becomingvar(--name);viewTransitionClass()takes thegroup,imagePair,oldandnewgroups and styles their pseudo-elements. New build errors: atypes.*()variable without adefault,types.integer()given a fraction, an unknowntypes.*helper, and aviewTransitionClass()key other thangroup,imagePair,oldandnewor a group that is not an object of declarationsstyleattribute text ("--a:" + value), as StyleX does for spreading onto non-React targets, instead of a style object; stylex.props() keeps the object React takes. The attrs() return type declaresstyleas a string...stylex.include(base.root)instylex.create()now overrides the included one, as StyleX merges them:{ ...stylex.include(s0.a), color: 'blue' }kept both the included red and the blue class, and red could win by stylesheet order. The included namespace's keys are merged where the spread is written, so a later key or a laterinclude()replaces what came before, andstylex.props()resolves such a namespace per key like any other. A dynamic (arrow function) namespace has no keys and is still only prepended. No new build errorsstylex: { styleResolution }, StyleX's babel plugin option of the same name, and the engines take it through the newsetStylexStyleResolution().'property-specificity'stays the default.'application-order'gives a staticstylex.create()key thenullresets StyleX's table lists for the longhands it covers (and reads its aliases,marginStartasmargin-inline-start), so the key applied last wins instylex.props()and within a namespace.'legacy-expand-shorthands'splits a shorthand into its longhands at build time as StyleX's table does (padding: '1px 2px'intopadding-top,padding-inline-end,padding-bottom,padding-inline-start). A later key of a static namespace now replaces an earlier one of the same name. New build errors under the two non-default policies only: a shorthand givenfirstThatWorks()fallbacks,allunderapplication-orderand alistStyleStyleX cannot sort underlegacy-expand-shorthands; an unknownstyleResolutionis a configuration error (StylexConfigError). Devup UI's own APIs ignore the option@stylexjs/stylexoutsidecreate,props,attrs,keyframes,defineVars,createTheme,createThemeContract,defineConsts,positionTry,viewTransitionClass,firstThatWorks,includeandtypes(such aswhen,envordefaultMarker), imported by name or read as a member of the package imported wholewhen.ancestor(),when.descendant(),when.anySibling(),when.siblingBefore(),when.siblingAfter(),defineMarker()anddefaultMarker()at build time, as@stylexjs/babel-plugindoes, instead of reporting them as unsupported: awhen.*()call becomes the:where(...)condition key StyleX writes, its rule writes the class twice to keep a pseudo-class's specificity and sorts before the pseudo-classes in StyleX's order,defaultMarker()is the classx-default-marker, anddefineMarker()names a class after its file and export that importing modules read too.@devup-ui/reacttypeswhen,defineMarker,defaultMarkerand markers inprops(). Pseudo-classes nested in each other are now written in the order StyleX sorts them, so:hoverinside:focusreads:focus:hover. New build errors: awhen.*()call whose pseudo-class is not a string literal starting with:or[(or is a pseudo-element, or an unclosed attribute selector), whose marker is not a marker or a class name, or that names another relation; adefineMarker()call with arguments or not bound to a named export of the module's top level; adefaultMarker()call with argumentsp => p.theme.space[2]or({ theme }) => theme.colors['brand'], now reads the CSS variable ThemeProvider declares (var(--space-2)). A theme read the build cannot turn into a CSS variable, such asp => p.theme,p => p.theme.brand()ortheme.space[i], is a build error naming the file, line, column and code, where it used to read a theme object that does not exist at runtime and give undefined or throwcardand a shadowcardboth declared--card, so one replaced the other in:root. New build error:theme: color token 'card' and shadow token 'card' both become the CSS variable --card: rename one, raised when the theme is registered for any two of colors,lengthandshadow(names compared after dots become dashes, sogray.100andgray-100clash too)$before forwarding a rest spread to a tag or component, including props supplied by callers or attrs. Style and attrs functions can still read transient props, and all other build-time forwarding policies remain unchanged. The styled-components migration guide documents transient prop support. No new build errorsoxc_sourcemap10, whichoxc_codegen0.159 now uses), napi 3.16 and typescript-eslint 8.73. Extracted CSS and class names are unchanged.@vanilla-extract/css-utilsis aliased by default and itscalccompiles to the strings the package builds (calc.add/subtract/multiply/divide/negate, chainedcalc(x)with.toString()or template interpolation, nested operations only parenthesized). A.css.tsstylesheet evaluates it without a module resolver, so its operands may be anything the stylesheet computes; elsewhere each call is written as its string and its operands must be literals, module-levelconsts holding a literal or othercalcresults.@devup-ui/react/compat/vanilla-extract-css-utilstypes it, and css-utils-literal-only reads its calls as the build does. New build errors: acalcoperand outside a stylesheet the build cannot read, acalcread without being called, acalc(x)used as a value without.toString()(also in a stylesheet), an export other thancalc, and a namespace import,require()or re-export of the package outside a stylesheet. SetimportAliases: { '@vanilla-extract/css-utils': false }to keep the packagestyle(rule, debugId)andstyleVariants(..., debugId)add a class named after the debug ID (root-0-0,tone_primary-0-1) that styles nothing, so the readable class list shows which style it came from; builds without debug are unchanged, andkeyframesstill ignores its debug ID@vanilla-extract/cssis aliased:@vanilla-extract/recipesand@vanilla-extract/sprinklesloaded byexport … from,export *,require(),import x = require()orimport()(an import already was);@vanilla-extract/dynamicloaded in any of these ways; andglobalKeyframesimported from@vanilla-extract/css, which failed with a bareTypeError: not a callable functionstyle({ margin: vars.space })or<Box p={vars.space} />compiles to the custom property the stylesheet's own CSS declares andstyle([base, ...])keeps the stylesheet's class. The import of the stylesheet stays so its CSS loads, and the importer depends on the stylesheet and the files it reads. A stylesheet that fails to extract, or an export the build cannot read as a literal, is still a located errorRuntimeError: unreachable.@devup-ui/bun-plugin@1.0.22 → 1.0.23 - packages/bun-plugin/package.json
Patch
includeoption, as the other plugins do, and compiles the published.jsfiles of the listed packages. Before, only.jsunder@devup-ui/was loaded, so an uncompiled library's components threwCannot run on the runtime. Each name matches that whole package, also in pnpm and Bun stores, and not the dependencies in its ownnode_modulesDevupUI()(from@devup-ui/bun-plugin/register) serves the generated stylesheet to the bundler's CSS loader once every other module is loaded, so the build emits a CSS output with the styles of the whole bundle instead of an empty module; class names are short there and readable under the runtime (debugoption). Files importing the packages Devup UI takes the place of (@emotion/react,@emotion/styled,styled-components,@vanilla-extract/css),@stylexjs/stylex, or a subpath or re-export of these or@devup-ui/react, are compiled instead of skipped.mts,.cts, and.jsand.cjsfiles outsidenode_modulesjoin.ts,.tsx,.jsxand.mjs. CommonJS keeps its exports: Bun does not run CommonJS anonLoadcallback returns, so the runtime plugin runs the module itself and hands Bun an ES module exporting itsmodule.exportstorequire()andimport. Source loads are synchronous, sorequire()works on compiled files too.extendschain as well as the Tailwind CSS, through their directories: editing, creating or removing one reloads the theme and rewrites theme.d.ts and the stylesheet, and a removed devup.json leaves an empty theme. Reloads never overlap. Coalesce the runtime stylesheet writes of the modules loaded together into one write of the latest sheet, made in the microtask after them, so N modules no longer rewrite the growing sheet N times while the sheet is still up to date once their import settles.v1.0.83, notv1.0.83,). A newlicenseBannerplugin option (defaulttrue) and thesetLicenseBanner/isLicenseBannerengine functions turn the banner off; both engines emit identical output.devup.jsonis reported instead of silently loading an empty theme. New errors:<file> is not valid JSON: <cause>,<file> must hold a JSON object, anddevup.json extends form a cycle: a -> b -> a(previously a cycle recursed until the stack overflowed). Vite, webpack, Rsbuild and Bun log the error and clear the theme as before (Bun used to swallow it); the Next.js Turbopack setup fails with it.theme.d.tsis now overwritten even when the theme has no tokens, so removed tokens leave no stale declarations. Rsbuild creates the CSS directory before writing into it, so a cold start no longer fails with ENOENTexport const B = Box,const c = css; export { c as cc },export const D = Devupandexport const C = Devup.cssin a barrel (the barrel module exports them as re-exports of the package, and what imports them follows them),export { Box }after an import,export default Box,const D = Devupnamespace aliases, andconst inner = cssdeclared inside a function. A css() or keyframes() const that a function reads before its declaration compiles. New build error: a css()/keyframes() const read before its declaration runs (outside a function) is located and says to move the declaration above its first readdevup.jsonextendsentry naming a file that does not exist now prints a warning naming that file and the config that lists it ([devup-ui] <config> extends <file>, which does not exist, so it adds nothing to the theme) instead of being silently ignored. The build still goes on without it, and dev servers keep watching the path, so the theme reloads once the file is created. A project without a devup.json stays quiet. No new build errors..mts,.ctsand.cjsmodules in every plugin, Turbopack and the import graph, and resolve./a.js,./a.mjsand./a.cjsimports to their TypeScript sources. Resolve packageexportsin the package's own order with the conditions of the bundler: Vite'sresolve.conditions, the ESM conditions of webpack and Rspack per environment, and the target andconditionsof Bun. Atom hoisting in webpack and Rsbuild plans over thesrcandappdirectories of the working directory and of the bundler root, notsrcalone. Bun keeps the modules whose values a file inlines in its module graph, so changing one rebuilds the file, and bundles the project's own.jsand.cjsmodules. No new build errors.stylex: { styleResolution }, StyleX's babel plugin option of the same name, and the engines take it through the newsetStylexStyleResolution().'property-specificity'stays the default.'application-order'gives a staticstylex.create()key thenullresets StyleX's table lists for the longhands it covers (and reads its aliases,marginStartasmargin-inline-start), so the key applied last wins instylex.props()and within a namespace.'legacy-expand-shorthands'splits a shorthand into its longhands at build time as StyleX's table does (padding: '1px 2px'intopadding-top,padding-inline-end,padding-bottom,padding-inline-start). A later key of a static namespace now replaces an earlier one of the same name. New build errors under the two non-default policies only: a shorthand givenfirstThatWorks()fallbacks,allunderapplication-orderand alistStyleStyleX cannot sort underlegacy-expand-shorthands; an unknownstyleResolutionis a configuration error (StylexConfigError). Devup UI's own APIs ignore the optiondevup.json, an invalid token name, or two token kinds that become the same CSS variable) now fails production builds with that error instead of building with an empty theme. Dev servers and watch builds keep running on an empty theme and report the error: Vite shows it in the error overlay in place of the reload, webpack, Next.js (webpack) and Rsbuild add it to every compilation's errors until it is fixed, and a Bun reload logs it@devup-ui/components@0.1.60 → 0.1.61 - packages/components/package.json
Patch
refas a prop. A ref given to Select or SelectContainer no longer replaces the internal one, which outside-click closing and popup positioning rely on. Toggle hands therole="switch"element; StepperInput hands the<input>, or the<output>of atype="text"stepperProgressBarcomponent: aprogressbarwith its range that fills a bar tovalueout ofmax, or withvariant="step"one segment per finished step, and can show the progress as a percent ordone/totalSearchcomponent: an<input type="search">with a magnifier icon built onInput, which callsonSearchwith the query on Enter (not on the Enter that confirms an IME composition), clears the query on Escape as its clear button does, and hides the browser's own clear button*and no longer depend on React 19 themselves, so a React 18 app no longer gets a second React. Select and Stepper read their context with useContext instead of React 19's use() and provide it with Context.Provider instead of React 19's (which crashes React 18), and Select repositions its container from an effect instead of a callback ref returning cleanup, which React 18 ignores@devup-ui/eslint-plugin@1.0.22 → 1.1.0 - packages/eslint-plugin/package.json
Minor
Patch
Xis read at runtime, where it does not exist"), and css-utils-literal-only reports globals that do not exist where a .css.ts is evaluated (window, document, process, ...). No new build errors.packageandimportAliasesoptions from the shared ESLint settingssettings['@devup-ui'], merged with the default aliases as the build merges them, so the rules check the same imports the build compiles: a custom package name, added aliases, and default aliases turned off withfalse. A setting the build plugin would not take stops the lint run with its path. No new build errors.@emotion/csslike the build does: itscss,keyframesandinjectGlobalget the same rules as Devup UI'scss,keyframesandglobalCss, so a dynamic value the build rejects is reported in the editor toocolor: ${(p) => p.color};or css({ color: () => 'red' }), in css-utils-literal-only. The build already refuses these; lint now reports them first with the new functionValue message. Functions called in a value and StyleX dynamic styles are not reported. No new build errors.@devup-ui/no-runtime-readacceptsstyled['div']andstyled[`div`]where they build a component, as the build now compiles them; a computed tag it cannot read (styled[tag]) is still reportedoxc_sourcemap10, whichoxc_codegen0.159 now uses), napi 3.16 and typescript-eslint 8.73. Extracted CSS and class names are unchanged.@vanilla-extract/css-utilsis aliased by default and itscalccompiles to the strings the package builds (calc.add/subtract/multiply/divide/negate, chainedcalc(x)with.toString()or template interpolation, nested operations only parenthesized). A.css.tsstylesheet evaluates it without a module resolver, so its operands may be anything the stylesheet computes; elsewhere each call is written as its string and its operands must be literals, module-levelconsts holding a literal or othercalcresults.@devup-ui/react/compat/vanilla-extract-css-utilstypes it, and css-utils-literal-only reads its calls as the build does. New build errors: acalcoperand outside a stylesheet the build cannot read, acalcread without being called, acalc(x)used as a value without.toString()(also in a stylesheet), an export other thancalc, and a namespace import,require()or re-export of the package outside a stylesheet. SetimportAliases: { '@vanilla-extract/css-utils': false }to keep the package@devup-ui/next-plugin@1.0.90 → 1.1.0 - packages/next-plugin/package.json
Minor
Patch
devup.jsonextends, as Vite does, and reload the theme when one is edited, added or deleted. Rsbuild did not reloaddevup.jsonitself in dev before; webpack only watched adevup.jsonthat existed when the build startedexitnever let finish, so the last writes could be lostv1.0.83, notv1.0.83,). A newlicenseBannerplugin option (defaulttrue) and thesetLicenseBanner/isLicenseBannerengine functions turn the banner off; both engines emit identical output.devup.jsonis reported instead of silently loading an empty theme. New errors:<file> is not valid JSON: <cause>,<file> must hold a JSON object, anddevup.json extends form a cycle: a -> b -> a(previously a cycle recursed until the stack overflowed). Vite, webpack, Rsbuild and Bun log the error and clear the theme as before (Bun used to swallow it); the Next.js Turbopack setup fails with it.theme.d.tsis now overwritten even when the theme has no tokens, so removed tokens leave no stale declarations. Rsbuild creates the CSS directory before writing into it, so a cold start no longer fails with ENOENTdevup.jsonextendsentry naming a file that does not exist now prints a warning naming that file and the config that lists it ([devup-ui] <config> extends <file>, which does not exist, so it adds nothing to the theme) instead of being silently ignored. The build still goes on without it, and dev servers keep watching the path, so the theme reloads once the file is created. A project without a devup.json stays quiet. No new build errors.Coordinator port file <file> names no valid portandCoordinator at 127.0.0.1:<port> (port file <file>) sent no response for 300s(a coordinator that accepts a request and never answers used to hang the build forever)distDir, each with its own engine session, extraction tracking and listener. Starting a second app no longer closes the first app's coordinator, and a config re-evaluation replaces only its own app's coordinator; the app's session is dropped when its last coordinator closes@devup-ui/next-pluginpublishes.restoreSessionStatewas typed through the internal engine loader, which pulled@devup-ui/webpack-pluginand webpack's own types (ajv, enhanced-resolve, schema-utils and more, 72 files) into the type check of every app whosenext.config.tsimports the plugin. Next's type check now reads 72 fewer files and its.next/cache/.tsbuildinfois about 26 KB smaller. The public API is unchanged.app/orpages/at the project root (nosrc/) are prewarmed and waited on likesrc/apps, so Turbopack production builds no longer fall back to a 2.5 s idle wait before serving the base CSS. Source scans skip dot directories such as.nextand.gitdebugoption (readable class names) like the webpack path, and keeps it apart in the production setup cache. A dev restart restores the previous session's sheet, class map and file map all together or not at all, so a missing or corrupt file no longer leaves a mix that gives new styles clashing names. When the import graph or file numbering cannot be built, Turbopack now prints a warning naming the cause and what the build loses instead of continuing silently. No new build errors.mts,.ctsand.cjsmodules in every plugin, Turbopack and the import graph, and resolve./a.js,./a.mjsand./a.cjsimports to their TypeScript sources. Resolve packageexportsin the package's own order with the conditions of the bundler: Vite'sresolve.conditions, the ESM conditions of webpack and Rspack per environment, and the target andconditionsof Bun. Atom hoisting in webpack and Rsbuild plans over thesrcandappdirectories of the working directory and of the bundler root, notsrcalone. Bun keeps the modules whose values a file inlines in its module graph, so changing one rebuilds the file, and bundles the project's own.jsand.cjsmodules. No new build errors.@devup-ui/plugin-utils/typesentry (resolved throughexports, andtypesVersionsfornode10resolution) holding the types the plugins' published declarations name. The Next plugin's declarations now import it instead of the whole package, so anext.config.tstype check loads 7 of plugin-utils' declaration files instead of 22 (.next/cache/.tsbuildinfoabout 3.5 KB smaller on the benchmark apps).@devup-ui/reactin the passes that run before the bundler: the shared class-slot reservation and the Next production prewarm no longer read, resolve or extract the runtime package's own modules, which hold no styles. Next's Turbopack setup drops from about 40 ms to 15 ms on the benchmark app and each webpack compiler does less work. Webpack per-file builds now number a project's files without the runtime package's modules in front of them, so per-file class prefixes and stylesheet names can be shorter (devup-ui-0.cssanda-instead ofdevup-ui-23.cssandx-); the styles are unchanged.globalCss, its own stylesheet and the class names handed out in it are dropped, and it leaves the bucket it collapsed into. The engine gainsremoveFile(filename)(native and WASM), which Vite calls on adeletewatch change, webpack and Rsbuild on the removed files of a watch run (webpack watch mode also saves the pruned state), and the Next.js Turbopack coordinator when an edited file is extracted again. Atoms in a stylesheet other files share stay, as nothing records which file added them; they style nothing once no module uses themwithSourceCache/readSourcein plugin-utils), which Next passes to the webpack plugin of each compiler. Watch and dev builds keep reading the disk on every compilation. Output is unchanged.devup-ui.css, the same layoutsingleCss: truegives, unlesssingleCssis set explicitly. Every stylesheet of such an app loads on its one page, so a stylesheet per file only added modules. The app counts as one route only when the import graph is sure: one page or route handler (page.mdxand other route files count too), noimport()that splits off a chunk, and no source file outside that route.next devand multi-route apps keep the per-file layout and their output.stylex: { styleResolution }, StyleX's babel plugin option of the same name, and the engines take it through the newsetStylexStyleResolution().'property-specificity'stays the default.'application-order'gives a staticstylex.create()key thenullresets StyleX's table lists for the longhands it covers (and reads its aliases,marginStartasmargin-inline-start), so the key applied last wins instylex.props()and within a namespace.'legacy-expand-shorthands'splits a shorthand into its longhands at build time as StyleX's table does (padding: '1px 2px'intopadding-top,padding-inline-end,padding-bottom,padding-inline-start). A later key of a static namespace now replaces an earlier one of the same name. New build errors under the two non-default policies only: a shorthand givenfirstThatWorks()fallbacks,allunderapplication-orderand alistStyleStyleX cannot sort underlegacy-expand-shorthands; an unknownstyleResolutionis a configuration error (StylexConfigError). Devup UI's own APIs ignore the optiondevup.json, an invalid token name, or two token kinds that become the same CSS variable) now fails production builds with that error instead of building with an empty theme. Dev servers and watch builds keep running on an empty theme and report the error: Vite shows it in the error overlay in place of the reload, webpack, Next.js (webpack) and Rsbuild add it to every compilation's errors until it is fixed, and a Bun reload logs it@devup-ui/plugin-utils@1.0.17 → 1.1.0 - packages/plugin-utils/package.json
Minor
Patch
openCompilerSession(compiler): it opens an engine session of its own on a shared compiler and returns{ id, compiler, close }. Every function of the scopedcompilerselects the session before it runs, so two apps in one process keep their numbering, sheet, theme and settings apart;close()drops the sessionv1.0.83, notv1.0.83,). A newlicenseBannerplugin option (defaulttrue) and thesetLicenseBanner/isLicenseBannerengine functions turn the banner off; both engines emit identical output.src) were missing from the output. The files the entries reach undersrcare now extracted before the build, the shared base on disk is kept current, and when a stylesheet still changed during the build it is compiled once more, writing only the complete result. Rsbuild serves each stylesheet from the current sheet instead of a module-wide string kept only when it grew, which left edits that shortened the CSS and later builds in the same process stale. plugin-utils adds computeReachableFilesdevup.jsonis reported instead of silently loading an empty theme. New errors:<file> is not valid JSON: <cause>,<file> must hold a JSON object, anddevup.json extends form a cycle: a -> b -> a(previously a cycle recursed until the stack overflowed). Vite, webpack, Rsbuild and Bun log the error and clear the theme as before (Bun used to swallow it); the Next.js Turbopack setup fails with it.theme.d.tsis now overwritten even when the theme has no tokens, so removed tokens leave no stale declarations. Rsbuild creates the CSS directory before writing into it, so a cold start no longer fails with ENOENTincludepackage names match only the whole package directory under the innermostnode_modules:foo.barno longer compilesfooXbar,pkgno longer compiles@scope/pkgorpkg-extra, names with regex characters such asfoo+barare compiled, and dependencies nested in an included package's ownnode_modulesare no longer compiled with it. Vite and Rsbuild build the matcher once instead of on every transformed module. No new build errorsdevup.jsonextendsentry naming a file that does not exist now prints a warning naming that file and the config that lists it ([devup-ui] <config> extends <file>, which does not exist, so it adds nothing to the theme) instead of being silently ignored. The build still goes on without it, and dev servers keep watching the path, so the theme reloads once the file is created. A project without a devup.json stays quiet. No new build errors.app/orpages/at the project root (nosrc/) are prewarmed and waited on likesrc/apps, so Turbopack production builds no longer fall back to a 2.5 s idle wait before serving the base CSS. Source scans skip dot directories such as.nextand.git.mts,.ctsand.cjsmodules in every plugin, Turbopack and the import graph, and resolve./a.js,./a.mjsand./a.cjsimports to their TypeScript sources. Resolve packageexportsin the package's own order with the conditions of the bundler: Vite'sresolve.conditions, the ESM conditions of webpack and Rspack per environment, and the target andconditionsof Bun. Atom hoisting in webpack and Rsbuild plans over thesrcandappdirectories of the working directory and of the bundler root, notsrcalone. Bun keeps the modules whose values a file inlines in its module graph, so changing one rebuilds the file, and bundles the project's own.jsand.cjsmodules. No new build errors.@devup-ui/plugin-utils/typesentry (resolved throughexports, andtypesVersionsfornode10resolution) holding the types the plugins' published declarations name. The Next plugin's declarations now import it instead of the whole package, so anext.config.tstype check loads 7 of plugin-utils' declaration files instead of 22 (.next/cache/.tsbuildinfoabout 3.5 KB smaller on the benchmark apps).@devup-ui/reactin the passes that run before the bundler: the shared class-slot reservation and the Next production prewarm no longer read, resolve or extract the runtime package's own modules, which hold no styles. Next's Turbopack setup drops from about 40 ms to 15 ms on the benchmark app and each webpack compiler does less work. Webpack per-file builds now number a project's files without the runtime package's modules in front of them, so per-file class prefixes and stylesheet names can be shorter (devup-ui-0.cssanda-instead ofdevup-ui-23.cssandx-); the styles are unchanged.withSourceCache/readSourcein plugin-utils), which Next passes to the webpack plugin of each compiler. Watch and dev builds keep reading the disk on every compilation. Output is unchanged.stylex: { styleResolution }, StyleX's babel plugin option of the same name, and the engines take it through the newsetStylexStyleResolution().'property-specificity'stays the default.'application-order'gives a staticstylex.create()key thenullresets StyleX's table lists for the longhands it covers (and reads its aliases,marginStartasmargin-inline-start), so the key applied last wins instylex.props()and within a namespace.'legacy-expand-shorthands'splits a shorthand into its longhands at build time as StyleX's table does (padding: '1px 2px'intopadding-top,padding-inline-end,padding-bottom,padding-inline-start). A later key of a static namespace now replaces an earlier one of the same name. New build errors under the two non-default policies only: a shorthand givenfirstThatWorks()fallbacks,allunderapplication-orderand alistStyleStyleX cannot sort underlegacy-expand-shorthands; an unknownstyleResolutionis a configuration error (StylexConfigError). Devup UI's own APIs ignore the optionpathsandbaseUrlare read throughextendsthe way TypeScript reads them: relative and package configs (a package'stsconfigfield ortsconfig.json), lists of configs where a later one wins, and cycles stop.baseUrlis relative to the config that declares it, andpathswithoutbaseUrlto the config that declarespaths. Imports through such aliases now resolve for build-time constants, atom hoisting and single-importer collapse@vanilla-extract/css-utilsis aliased by default and itscalccompiles to the strings the package builds (calc.add/subtract/multiply/divide/negate, chainedcalc(x)with.toString()or template interpolation, nested operations only parenthesized). A.css.tsstylesheet evaluates it without a module resolver, so its operands may be anything the stylesheet computes; elsewhere each call is written as its string and its operands must be literals, module-levelconsts holding a literal or othercalcresults.@devup-ui/react/compat/vanilla-extract-css-utilstypes it, and css-utils-literal-only reads its calls as the build does. New build errors: acalcoperand outside a stylesheet the build cannot read, acalcread without being called, acalc(x)used as a value without.toString()(also in a stylesheet), an export other thancalc, and a namespace import,require()or re-export of the package outside a stylesheet. SetimportAliases: { '@vanilla-extract/css-utils': false }to keep the package@devup-ui/react@1.0.44 → 1.0.45 - packages/react/package.json
Patch
ThemeProviderrenders no wrapper element without atheme, and with one declares only the CSS variables its theme changes from the outer provider's.withThemehoists the component's non-React statics, andServerStyleSheethas an emptyinstance(withclearTag()) for SSR setups that pass it toStyleSheetManager. New runtime errors thrown byThemeProvider: a theme key that cannot be part of a CSS variable name (such as'brand color'), two theme paths giving the same variable ({ a: { b } }and'a-b'), and a theme that contains itself, each naming the theme path, instead of silently dropping values or recursing foreverimport { CacheProvider } from '@emotion/react'is redirected there instead of keeping @emotion/react as a runtime dependency; the cache it configures holds styles Emotion inserts at runtime, which Devup UI writes at build time;before}: StyleXdefineVars(),createTheme(), typed-variable@property,positionTry()andviewTransitionClass()rules, and the variables the runtimecreateTheme()GlobalStyledeclares, now separate declarations with;only between them, as the rest of the generated CSS already does. The CSS is equivalent and slightly smaller.*and no longer depend on React 19 themselves, so a React 18 app no longer gets a second React. Select and Stepper read their context with useContext instead of React 19's use() and provide it with Context.Provider instead of React 19's (which crashes React 18), and Select repositions its container from an effect instead of a callback ref returning cleanup, which React 18 ignores@devup-ui/react's type declarations bundled: one file per entry (@devup-ui/react,/compat,/stylex) plus one shared file, instead of one declaration file per source module. A project type-checks 4 declaration files of the package instead of about 50. Behavior change formoduleResolution: node16/nodenextprojects: they used to resolve the package's types toany(the per-module declarations imported each other without file extensions), with theme augmentation ignored; they now get the real types, so type errors that were hidden before can appear. Withbundlerandnode10resolution the exported names and types and theme augmentation are unchanged.styledcarries astyledComponentIdproperty, set once per file by a small helper, and the compatisStyledComponentreturns true for it as styled-components does instead of always returning false(size) => ({ width: { default: 100, ':hover': size } })), each condition taking its own variable; a computed condition key may read adefineConsts()constant ([constants.wide]); atypes.*()variable indefineVars()registers@propertywith itsdefaultas the initial value; a'--global'key keeps its name andcolors['--global']reads it;positionTry()andviewTransitionClass()bindings read as their names increate(), two of them in one file no longer share a name, and a dashed ident on an anchor, timeline or position-try property stays a name instead of becomingvar(--name);viewTransitionClass()takes thegroup,imagePair,oldandnewgroups and styles their pseudo-elements. New build errors: atypes.*()variable without adefault,types.integer()given a fraction, an unknowntypes.*helper, and aviewTransitionClass()key other thangroup,imagePair,oldandnewor a group that is not an object of declarationsstyleattribute text ("--a:" + value), as StyleX does for spreading onto non-React targets, instead of a style object; stylex.props() keeps the object React takes. The attrs() return type declaresstyleas a stringwhen.ancestor(),when.descendant(),when.anySibling(),when.siblingBefore(),when.siblingAfter(),defineMarker()anddefaultMarker()at build time, as@stylexjs/babel-plugindoes, instead of reporting them as unsupported: awhen.*()call becomes the:where(...)condition key StyleX writes, its rule writes the class twice to keep a pseudo-class's specificity and sorts before the pseudo-classes in StyleX's order,defaultMarker()is the classx-default-marker, anddefineMarker()names a class after its file and export that importing modules read too.@devup-ui/reacttypeswhen,defineMarker,defaultMarkerand markers inprops(). Pseudo-classes nested in each other are now written in the order StyleX sorts them, so:hoverinside:focusreads:focus:hover. New build errors: awhen.*()call whose pseudo-class is not a string literal starting with:or[(or is a pseudo-element, or an unclosed attribute selector), whose marker is not a marker or a class name, or that names another relation; adefineMarker()call with arguments or not bound to a named export of the module's top level; adefaultMarker()call with arguments$before forwarding a rest spread to a tag or component, including props supplied by callers or attrs. Style and attrs functions can still read transient props, and all other build-time forwarding policies remain unchanged. The styled-components migration guide documents transient prop support. No new build errors@vanilla-extract/css-utilsis aliased by default and itscalccompiles to the strings the package builds (calc.add/subtract/multiply/divide/negate, chainedcalc(x)with.toString()or template interpolation, nested operations only parenthesized). A.css.tsstylesheet evaluates it without a module resolver, so its operands may be anything the stylesheet computes; elsewhere each call is written as its string and its operands must be literals, module-levelconsts holding a literal or othercalcresults.@devup-ui/react/compat/vanilla-extract-css-utilstypes it, and css-utils-literal-only reads its calls as the build does. New build errors: acalcoperand outside a stylesheet the build cannot read, acalcread without being called, acalc(x)used as a value without.toString()(also in a stylesheet), an export other thancalc, and a namespace import,require()or re-export of the package outside a stylesheet. SetimportAliases: { '@vanilla-extract/css-utils': false }to keep the package@devup-ui/reset-css@1.0.31 → 1.0.32 - packages/reset-css/package.json
Patch
@devup-ui/rsbuild-plugin@1.0.67 → 1.1.0 - packages/rsbuild-plugin/package.json
Minor
Patch
devup.jsonextends, as Vite does, and reload the theme when one is edited, added or deleted. Rsbuild did not reloaddevup.jsonitself in dev before; webpack only watched adevup.jsonthat existed when the build startedv1.0.83, notv1.0.83,). A newlicenseBannerplugin option (defaulttrue) and thesetLicenseBanner/isLicenseBannerengine functions turn the banner off; both engines emit identical output.src) were missing from the output. The files the entries reach undersrcare now extracted before the build, the shared base on disk is kept current, and when a stylesheet still changed during the build it is compiled once more, writing only the complete result. Rsbuild serves each stylesheet from the current sheet instead of a module-wide string kept only when it grew, which left edits that shortened the CSS and later builds in the same process stale. plugin-utils adds computeReachableFilesdevup.jsonis reported instead of silently loading an empty theme. New errors:<file> is not valid JSON: <cause>,<file> must hold a JSON object, anddevup.json extends form a cycle: a -> b -> a(previously a cycle recursed until the stack overflowed). Vite, webpack, Rsbuild and Bun log the error and clear the theme as before (Bun used to swallow it); the Next.js Turbopack setup fails with it.theme.d.tsis now overwritten even when the theme has no tokens, so removed tokens leave no stale declarations. Rsbuild creates the CSS directory before writing into it, so a cold start no longer fails with ENOENTincludepackage names match only the whole package directory under the innermostnode_modules:foo.barno longer compilesfooXbar,pkgno longer compiles@scope/pkgorpkg-extra, names with regex characters such asfoo+barare compiled, and dependencies nested in an included package's ownnode_modulesare no longer compiled with it. Vite and Rsbuild build the matcher once instead of on every transformed module. No new build errorsextractCss: falseis published uncompiled, and every application that uses it must list the package ininclude..mdxfilename as the JavaScript module (with or without JSX) an MDX compiler makes of it instead of rejecting the extension, the Vite plugin extracts.mdxin aposttransform, and the webpack and Rsbuild plugins in apostloader; Next.js with Turbopack and the Bun plugin still leave MDX untransformeddevup.jsonextendsentry naming a file that does not exist now prints a warning naming that file and the config that lists it ([devup-ui] <config> extends <file>, which does not exist, so it adds nothing to the theme) instead of being silently ignored. The build still goes on without it, and dev servers keep watching the path, so the theme reloads once the file is created. A project without a devup.json stays quiet. No new build errors..mts,.ctsand.cjsmodules in every plugin, Turbopack and the import graph, and resolve./a.js,./a.mjsand./a.cjsimports to their TypeScript sources. Resolve packageexportsin the package's own order with the conditions of the bundler: Vite'sresolve.conditions, the ESM conditions of webpack and Rspack per environment, and the target andconditionsof Bun. Atom hoisting in webpack and Rsbuild plans over thesrcandappdirectories of the working directory and of the bundler root, notsrcalone. Bun keeps the modules whose values a file inlines in its module graph, so changing one rebuilds the file, and bundles the project's own.jsand.cjsmodules. No new build errors.globalCss, its own stylesheet and the class names handed out in it are dropped, and it leaves the bucket it collapsed into. The engine gainsremoveFile(filename)(native and WASM), which Vite calls on adeletewatch change, webpack and Rsbuild on the removed files of a watch run (webpack watch mode also saves the pruned state), and the Next.js Turbopack coordinator when an edited file is extracted again. Atoms in a stylesheet other files share stay, as nothing records which file added them; they style nothing once no module uses themstylex: { styleResolution }, StyleX's babel plugin option of the same name, and the engines take it through the newsetStylexStyleResolution().'property-specificity'stays the default.'application-order'gives a staticstylex.create()key thenullresets StyleX's table lists for the longhands it covers (and reads its aliases,marginStartasmargin-inline-start), so the key applied last wins instylex.props()and within a namespace.'legacy-expand-shorthands'splits a shorthand into its longhands at build time as StyleX's table does (padding: '1px 2px'intopadding-top,padding-inline-end,padding-bottom,padding-inline-start). A later key of a static namespace now replaces an earlier one of the same name. New build errors under the two non-default policies only: a shorthand givenfirstThatWorks()fallbacks,allunderapplication-orderand alistStyleStyleX cannot sort underlegacy-expand-shorthands; an unknownstyleResolutionis a configuration error (StylexConfigError). Devup UI's own APIs ignore the optiondevup.json, an invalid token name, or two token kinds that become the same CSS variable) now fails production builds with that error instead of building with an empty theme. Dev servers and watch builds keep running on an empty theme and report the error: Vite shows it in the error overlay in place of the reload, webpack, Next.js (webpack) and Rsbuild add it to every compilation's errors until it is fixed, and a Bun reload logs it@devup-ui/vite-plugin@1.0.73 → 1.0.74 - packages/vite-plugin/package.json
Patch
v1.0.83, notv1.0.83,). A newlicenseBannerplugin option (defaulttrue) and thesetLicenseBanner/isLicenseBannerengine functions turn the banner off; both engines emit identical output.devup.jsonis reported instead of silently loading an empty theme. New errors:<file> is not valid JSON: <cause>,<file> must hold a JSON object, anddevup.json extends form a cycle: a -> b -> a(previously a cycle recursed until the stack overflowed). Vite, webpack, Rsbuild and Bun log the error and clear the theme as before (Bun used to swallow it); the Next.js Turbopack setup fails with it.theme.d.tsis now overwritten even when the theme has no tokens, so removed tokens leave no stale declarations. Rsbuild creates the CSS directory before writing into it, so a cold start no longer fails with ENOENTincludepackage names match only the whole package directory under the innermostnode_modules:foo.barno longer compilesfooXbar,pkgno longer compiles@scope/pkgorpkg-extra, names with regex characters such asfoo+barare compiled, and dependencies nested in an included package's ownnode_modulesare no longer compiled with it. Vite and Rsbuild build the matcher once instead of on every transformed module. No new build errorsextractCss: falseis published uncompiled, and every application that uses it must list the package ininclude..mdxfilename as the JavaScript module (with or without JSX) an MDX compiler makes of it instead of rejecting the extension, the Vite plugin extracts.mdxin aposttransform, and the webpack and Rsbuild plugins in apostloader; Next.js with Turbopack and the Bun plugin still leave MDX untransformeddevup.jsonextendsentry naming a file that does not exist now prints a warning naming that file and the config that lists it ([devup-ui] <config> extends <file>, which does not exist, so it adds nothing to the theme) instead of being silently ignored. The build still goes on without it, and dev servers keep watching the path, so the theme reloads once the file is created. A project without a devup.json stays quiet. No new build errors..mts,.ctsand.cjsmodules in every plugin, Turbopack and the import graph, and resolve./a.js,./a.mjsand./a.cjsimports to their TypeScript sources. Resolve packageexportsin the package's own order with the conditions of the bundler: Vite'sresolve.conditions, the ESM conditions of webpack and Rspack per environment, and the target andconditionsof Bun. Atom hoisting in webpack and Rsbuild plans over thesrcandappdirectories of the working directory and of the bundler root, notsrcalone. Bun keeps the modules whose values a file inlines in its module graph, so changing one rebuilds the file, and bundles the project's own.jsand.cjsmodules. No new build errors.globalCss, its own stylesheet and the class names handed out in it are dropped, and it leaves the bucket it collapsed into. The engine gainsremoveFile(filename)(native and WASM), which Vite calls on adeletewatch change, webpack and Rsbuild on the removed files of a watch run (webpack watch mode also saves the pruned state), and the Next.js Turbopack coordinator when an edited file is extracted again. Atoms in a stylesheet other files share stay, as nothing records which file added them; they style nothing once no module uses themstylex: { styleResolution }, StyleX's babel plugin option of the same name, and the engines take it through the newsetStylexStyleResolution().'property-specificity'stays the default.'application-order'gives a staticstylex.create()key thenullresets StyleX's table lists for the longhands it covers (and reads its aliases,marginStartasmargin-inline-start), so the key applied last wins instylex.props()and within a namespace.'legacy-expand-shorthands'splits a shorthand into its longhands at build time as StyleX's table does (padding: '1px 2px'intopadding-top,padding-inline-end,padding-bottom,padding-inline-start). A later key of a static namespace now replaces an earlier one of the same name. New build errors under the two non-default policies only: a shorthand givenfirstThatWorks()fallbacks,allunderapplication-orderand alistStyleStyleX cannot sort underlegacy-expand-shorthands; an unknownstyleResolutionis a configuration error (StylexConfigError). Devup UI's own APIs ignore the optiondevup.json, an invalid token name, or two token kinds that become the same CSS variable) now fails production builds with that error instead of building with an empty theme. Dev servers and watch builds keep running on an empty theme and report the error: Vite shows it in the error overlay in place of the reload, webpack, Next.js (webpack) and Rsbuild add it to every compilation's errors until it is fixed, and a Bun reload logs it@devup-ui/webpack-plugin@1.0.71 → 1.1.0 - packages/webpack-plugin/package.json
Minor
Patch
devup.jsonextends, as Vite does, and reload the theme when one is edited, added or deleted. Rsbuild did not reloaddevup.jsonitself in dev before; webpack only watched adevup.jsonthat existed when the build startedv1.0.83, notv1.0.83,). A newlicenseBannerplugin option (defaulttrue) and thesetLicenseBanner/isLicenseBannerengine functions turn the banner off; both engines emit identical output.src) were missing from the output. The files the entries reach undersrcare now extracted before the build, the shared base on disk is kept current, and when a stylesheet still changed during the build it is compiled once more, writing only the complete result. Rsbuild serves each stylesheet from the current sheet instead of a module-wide string kept only when it grew, which left edits that shortened the CSS and later builds in the same process stale. plugin-utils adds computeReachableFilesdevup.jsonis reported instead of silently loading an empty theme. New errors:<file> is not valid JSON: <cause>,<file> must hold a JSON object, anddevup.json extends form a cycle: a -> b -> a(previously a cycle recursed until the stack overflowed). Vite, webpack, Rsbuild and Bun log the error and clear the theme as before (Bun used to swallow it); the Next.js Turbopack setup fails with it.theme.d.tsis now overwritten even when the theme has no tokens, so removed tokens leave no stale declarations. Rsbuild creates the CSS directory before writing into it, so a cold start no longer fails with ENOENTextractCss: falseis published uncompiled, and every application that uses it must list the package ininclude..mdxfilename as the JavaScript module (with or without JSX) an MDX compiler makes of it instead of rejecting the extension, the Vite plugin extracts.mdxin aposttransform, and the webpack and Rsbuild plugins in apostloader; Next.js with Turbopack and the Bun plugin still leave MDX untransformeddevup.jsonextendsentry naming a file that does not exist now prints a warning naming that file and the config that lists it ([devup-ui] <config> extends <file>, which does not exist, so it adds nothing to the theme) instead of being silently ignored. The build still goes on without it, and dev servers keep watching the path, so the theme reloads once the file is created. A project without a devup.json stays quiet. No new build errors..mts,.ctsand.cjsmodules in every plugin, Turbopack and the import graph, and resolve./a.js,./a.mjsand./a.cjsimports to their TypeScript sources. Resolve packageexportsin the package's own order with the conditions of the bundler: Vite'sresolve.conditions, the ESM conditions of webpack and Rspack per environment, and the target andconditionsof Bun. Atom hoisting in webpack and Rsbuild plans over thesrcandappdirectories of the working directory and of the bundler root, notsrcalone. Bun keeps the modules whose values a file inlines in its module graph, so changing one rebuilds the file, and bundles the project's own.jsand.cjsmodules. No new build errors.globalCss, its own stylesheet and the class names handed out in it are dropped, and it leaves the bucket it collapsed into. The engine gainsremoveFile(filename)(native and WASM), which Vite calls on adeletewatch change, webpack and Rsbuild on the removed files of a watch run (webpack watch mode also saves the pruned state), and the Next.js Turbopack coordinator when an edited file is extracted again. Atoms in a stylesheet other files share stay, as nothing records which file added them; they style nothing once no module uses themwithSourceCache/readSourcein plugin-utils), which Next passes to the webpack plugin of each compiler. Watch and dev builds keep reading the disk on every compilation. Output is unchanged.stylex: { styleResolution }, StyleX's babel plugin option of the same name, and the engines take it through the newsetStylexStyleResolution().'property-specificity'stays the default.'application-order'gives a staticstylex.create()key thenullresets StyleX's table lists for the longhands it covers (and reads its aliases,marginStartasmargin-inline-start), so the key applied last wins instylex.props()and within a namespace.'legacy-expand-shorthands'splits a shorthand into its longhands at build time as StyleX's table does (padding: '1px 2px'intopadding-top,padding-inline-end,padding-bottom,padding-inline-start). A later key of a static namespace now replaces an earlier one of the same name. New build errors under the two non-default policies only: a shorthand givenfirstThatWorks()fallbacks,allunderapplication-orderand alistStyleStyleX cannot sort underlegacy-expand-shorthands; an unknownstyleResolutionis a configuration error (StylexConfigError). Devup UI's own APIs ignore the optiondevup.json, an invalid token name, or two token kinds that become the same CSS variable) now fails production builds with that error instead of building with an empty theme. Dev servers and watch builds keep running on an empty theme and report the error: Vite shows it in the error overlay in place of the reload, webpack, Next.js (webpack) and Rsbuild add it to every compilation's errors until it is fixed, and a Bun reload logs it