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
from
November 17, 2026 07:35
f6ff7a9 to
ee60cae
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.1.1 - bindings/devup-ui-binding/package.json
Patch
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 aliasedborder-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 itspan: {...}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 acceptedstyledcarries astyledComponentIdproperty, set once per file by a small helper, and the compatisStyledComponentreturns true for it as styled-components does instead of always returning falsestyled['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 errorthemeprop 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@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 wholecardand 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)style(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.1.1 - bindings/devup-ui-binding-darwin-arm64/package.json
Patch
@devup-ui/binding-darwin-x64@0.1.0 → 0.1.1 - bindings/devup-ui-binding-darwin-x64/package.json
Patch
@devup-ui/binding-linux-arm64-gnu@0.1.0 → 0.1.1 - bindings/devup-ui-binding-linux-arm64-gnu/package.json
Patch
@devup-ui/binding-linux-arm64-musl@0.1.0 → 0.1.1 - bindings/devup-ui-binding-linux-arm64-musl/package.json
Patch
@devup-ui/binding-linux-x64-gnu@0.1.0 → 0.1.1 - bindings/devup-ui-binding-linux-x64-gnu/package.json
Patch
@devup-ui/binding-linux-x64-musl@0.1.0 → 0.1.1 - bindings/devup-ui-binding-linux-x64-musl/package.json
Patch
@devup-ui/binding-win32-arm64-msvc@0.1.0 → 0.1.1 - bindings/devup-ui-binding-win32-arm64-msvc/package.json
Patch
@devup-ui/binding-win32-x64-msvc@0.1.0 → 0.1.1 - bindings/devup-ui-binding-win32-x64-msvc/package.json
Patch
@devup-ui/wasm@1.0.83 → 1.0.84 - bindings/devup-ui-wasm/package.json
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 runtime&: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 written${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 aliasedexport 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 readborder-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 itspan: {...}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")styledcarries astyledComponentIdproperty, set once per file by a small helper, and the compatisStyledComponentreturns true for it as styled-components does instead of always returning falsestyled['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$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 insteadstyleattribute 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@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 wholep => 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 errorsstyle(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
DevupUI()(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 skippeddevup.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.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"stepper*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.0.23 - packages/eslint-plugin/package.json
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 too@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 reported@devup-ui/next-plugin@1.0.90 → 1.0.91 - packages/next-plugin/package.json
Patch
exitnever let finish, so the last writes could be lostdevup.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 ENOENTapp/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.gitglobalCss, 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 themdevup.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.0.18 - packages/plugin-utils/package.json
Patch
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 errorsapp/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.gitpathsandbaseUrlare 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@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*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 ignoresstyledcarries astyledComponentIdproperty, set once per file by a small helper, and the compatisStyledComponentreturns true for it as styled-components does instead of always returning falsestyleattribute 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$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@devup-ui/reset-css@1.0.31 → 1.0.32 - packages/reset-css/package.json
Patch
@devup-ui/rsbuild-plugin@1.0.67 → 1.0.68 - packages/rsbuild-plugin/package.json
Patch
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 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 untransformedglobalCss, 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 themdevup.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
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 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 untransformedglobalCss, 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 themdevup.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.0.72 - packages/webpack-plugin/package.json
Patch
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 ENOENT.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 untransformedglobalCss, 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 themdevup.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