Skip to content

Update Versions - #769

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
changepacks/main
Open

github-actions[bot] wants to merge 1 commit into
mainfrom
changepacks/main

Conversation

@github-actions

@github-actions github-actions Bot commented Oct 8, 2026 •

Copy link
Copy Markdown
Contributor

Changepacks

@devup-ui/binding@0.1.0 → 0.2.0 - bindings/devup-ui-binding/package.json

Minor

  • Require Node.js 20 or later for the build-time packages: Node 18 is past its end of life and does not expose the globalThis.crypto the WASM engine reads. The plugins, plugin-utils, the WASM engine and the native bindings now declare engines.node >=20 (the ESLint plugin ^20.9.0 || >=21.1.0, as typescript-eslint 8 requires; the Vite plugin keeps >=22).

Patch

  • One-shot production builds with the Vite and webpack plugins (Next.js without Turbopack included) drop the component-selector markers no module selects. Each transform and the start-of-build scan report the markers they give and select; once every module is compiled, a marker no module selects or writes leaves the output chunks. When a module selects a component but the scan never read it (virtual module, a file compiled by another tool such as MDX, require.context / import.meta.glob / computed import(), or a file outside the scanned roots and entries), the build keeps every marker and warns with the module and the reason. The scan now also follows require.context and import.meta.glob calls whose arguments are written out. Warm webpack builds read the reports of modules restored from the persistent cache. Dev servers, watch builds, Turbopack and the Rsbuild and Bun plugins keep every marker.
  • Stylesheets without any rule are emitted empty instead of as a bare license banner, so the empty shared base sheet no longer repeats the banner in every per-file stylesheet that imports it. The banner names the version without a trailing comma (v1.0.83, not v1.0.83,). A new licenseBanner plugin option (default true) and the setLicenseBanner/isLicenseBanner engine functions turn the banner off; both engines emit identical output.
  • Emotion's css prop now compiles a const that chooses among style objects, as in const rules = on ? { color: 'red' } : { color: 'blue' }; <div css={rules} />. Before, it became className={rules} with no CSS. When only css props read the binding, each object (or array, or CSS text) compiles in the declaration to the classes Emotion would give it, with numbers read as px as 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.
  • Reuse a serialized stylesheet until the sheet or the atom-hoisting settings it reads change: getCss and the CSS a transform returns no longer serialize the same unchanged sheet again. The output is byte-identical.
  • Emotion code the build cannot compile is a located build error instead of staying at runtime, and Emotion's cx merges the styles of classes css() gives in argument order, so cx(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 no withComponent; an @emotion/react import with no Devup UI equivalent (ThemeContext, withEmotionCache, a default or namespace import) while @emotion/react is aliased, naming the export; and @emotion/css/create-instance loaded by an import, re-export, require() or import() while @emotion/css is aliased
  • New createSession(), selectSession(id) and dropSession(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. selectSession and dropSession throw a TypeError for an id that is not an unsigned 32-bit integer, and an Error for an unknown session or for dropping session 0
  • The engine keeps its state per engine session: class and file numbering, routes, prefix, debug, atom hoisting, slot reservation, shorthands, theme tokens, Tailwind definitions, the stylesheet, the stylesheet caches and the module resolver move together when a session is switched. Session 0 is the only one until a host creates another, so a single app sees no change
  • A shorthand set across a boundary after a longhand it covers now wins, as the later style: css({ borderTopWidth: 2 }, { borderWidth: 1 }) keeps only border-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, so css({ 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 errors
  • Serialize the CSS a transform returns only when it is read: a read after later transforms or setting changes still returns the sheet as that transform left it. The Next.js loader and prewarm never read it, and the Webpack loader reads it only when it writes it, so single-CSS builds no longer serialize the whole sheet after every module. The output is byte-identical.
  • A longhand now wins over a shorthand that covers it, as StyleX's property-specificity policy and atomic CSS expect: rules of one selector and breakpoint were sorted by property name, so border-width came after border-top-width and place-items after align-items and the shorthand won. Each property now sorts right after the last shorthand covering it (all first); 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
  • MDX documents are extracted after the MDX plugin compiles them: the engine reads an .mdx filename as the JavaScript module (with or without JSX) an MDX compiler makes of it instead of rejecting the extension, the Vite plugin extracts .mdx in a post transform, and the webpack and Rsbuild plugins in a post loader; Next.js with Turbopack and the Bun plugin still leave MDX untransformed
  • The native binding now rejects a module resolver result with an empty path in the engine itself, as WASM does, instead of relying on the JavaScript adapter alone: both report malformed module resolver result: path must be a non-empty string at the import that requested it
  • CSS blocks no longer end with a redundant ; before }: StyleX defineVars(), createTheme(), typed-variable @property, positionTry() and viewTransitionClass() rules, and the variables the runtime createTheme() GlobalStyle declares, now separate declarations with ; only between them, as the rest of the generated CSS already does. The CSS is equivalent and slightly smaller.
  • Read a style object key that holds an object and names no style property as a nested selector, as Emotion and styled-components do, in css(), globalCss(), styled object styles, the css prop and the Emotion and styled-components imports: 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 as hover stays that selector as in the selectors prop, and :, ::, [ and & keys keep applying to the element. Style properties, Devup UI shorthands such as p, string values and JSX props keep their meaning.
  • Add the public native build-time compiler with CommonJS and ESM types and eight OS, architecture and libc-specific optional packages. Validate exact native tarballs and publish platform artifacts before the root binding. Unsupported hosts and omitted native optional packages fail explicitly; source build errors and generated styling runtime are unchanged. Plugin engine selection is a separate phase.
  • A source file deleted or renamed in watch mode or the dev server no longer leaves its styles behind: its globalCss, its own stylesheet and the class names handed out in it are dropped, and it leaves the bucket it collapsed into. The engine gains removeFile(filename) (native and WASM), which Vite calls on a delete watch 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
  • Resolving the imports of a file parses it once to find where it references each module, instead of once per import resolved. A component with ten imports was parsed again ten times during extraction just to locate possible resolver errors; diagnostics are unchanged
  • A responsive length or shadow $token inside a responsive array now reads var(--token) instead of the token's first raw value: px={['8px', null, '$containerX']} showed the mobile 16px at index 2 where the theme sets --containerX to 32px, and w={['$containerX']} ignored theme variants such as compact. The slot still emits one class at its own breakpoint
  • Options that styled-components' StyleSheetManager and Emotion's createCache() would apply at runtime, and the inert compat StyleSheetManager and CacheProvider silently dropped, are now located build errors (file:line:col, cause and fix): stylisPlugins, shouldForwardProp and namespace of StyleSheetManager from an aliased package, and spread props on it; stylisPlugins of 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 as key stays accepted
  • styled-components v6 passes shouldForwardProp the 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 evaluates shouldForwardProp only 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.
  • Every component compiled from styled carries a styledComponentId property, set once per file by a small helper, and the compat isStyledComponent returns true for it as styled-components does instead of always returning false
  • Components made with styled-components' styled now pass props on as styled-components v6 does: without shouldForwardProp, every prop reaches the rendered element, a DOM tag included, even one the styles read, except $ props, as and theme. 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's shouldForwardProp stays a build error: keep props off the element with $ transient props or .withConfig({ shouldForwardProp }).
  • styled['div'] and styled[`div`] compile as styled.div does, in tagged templates and calls and before .attrs / .withConfig, for Emotion, styled-components and Devup UI's own styled, keeping Emotion's numbers as pixels. A computed tag the build cannot read (styled[tag]) or that no styled. member could spell (styled['my-element']) stays a located build error
  • Emotion's <Global styles> takes a css() class holding rules under selectors, an array of rule objects and classes (false, null and undefined skipped) and a function of the theme whose theme.a.b reads become var(--a-b); Emotion's target and styled-components' componentId become a stable class on the element that extending components render too; and a label: declaration in CSS text is dropped instead of written as invalid CSS. New build errors: a target or componentId that is not one class name written as a string; defaultProps assigned to a styled component, which compiles to a function component whose defaultProps React 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 as theme.a.b
  • A theme prop 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: a theme attribute on an element of a styled component whose styles read the theme; wrap the element in a ThemeProvider with that theme instead
  • StyleX APIs compile as StyleX defines them: a dynamic style may set its parameters under conditions ((size) => ({ width: { default: 100, ':hover': size } })), each condition taking its own variable; a computed condition key may read a defineConsts() constant ([constants.wide]); a types.*() variable in defineVars() registers @property with its default as the initial value; a '--global' key keeps its name and colors['--global'] reads it; positionTry() and viewTransitionClass() bindings read as their names in create(), 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 becoming var(--name); viewTransitionClass() takes the group, imagePair, old and new groups and styles their pseudo-elements. New build errors: a types.*() variable without a default, types.integer() given a fraction, an unknown types.* helper, and a viewTransitionClass() key other than group, imagePair, old and new or a group that is not an object of declarations
  • A key written after ...stylex.include(base.root) in stylex.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 later include() replaces what came before, and stylex.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 errors
  • Every plugin takes stylex: { styleResolution }, StyleX's babel plugin option of the same name, and the engines take it through the new setStylexStyleResolution(). 'property-specificity' stays the default. 'application-order' gives a static stylex.create() key the null resets StyleX's table lists for the longhands it covers (and reads its aliases, marginStart as margin-inline-start), so the key applied last wins in stylex.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' into padding-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 given firstThatWorks() fallbacks, all under application-order and a listStyle StyleX cannot sort under legacy-expand-shorthands; an unknown styleResolution is a configuration error (StylexConfigError). Devup UI's own APIs ignore the option
  • A StyleX API Devup UI does not compile is a located build error naming it, instead of being dropped from the compiled set while its calls stay StyleX calls that throw at runtime. New build error: an export of @stylexjs/stylex outside create, props, attrs, keyframes, defineVars, createTheme, createThemeContract, defineConsts, positionTry, viewTransitionClass, firstThatWorks, include and types (such as when, env or defaultMarker), imported by name or read as a member of the package imported whole
  • Compile StyleX when.ancestor(), when.descendant(), when.anySibling(), when.siblingBefore(), when.siblingAfter(), defineMarker() and defaultMarker() at build time, as @stylexjs/babel-plugin does, instead of reporting them as unsupported: a when.*() 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 class x-default-marker, and defineMarker() names a class after its file and export that importing modules read too. @devup-ui/react types when, defineMarker, defaultMarker and markers in props(). Pseudo-classes nested in each other are now written in the order StyleX sorts them, so :hover inside :focus reads :focus:hover. New build errors: a when.*() 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; a defineMarker() call with arguments or not bound to a named export of the module's top level; a defaultMarker() call with arguments
  • Theme tokens of different kinds can no longer silently share a CSS variable: a color card and a shadow card both 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, length and shadow (names compared after dots become dashes, so gray.100 and gray-100 clash too)
  • Update dependencies to their latest releases: Oxc 0.159 (with oxc_sourcemap 10, which oxc_codegen 0.159 now uses), napi 3.16 and typescript-eslint 8.73. Extracted CSS and class names are unchanged.
  • @vanilla-extract/css-utils is aliased by default and its calc compiles to the strings the package builds (calc.add/subtract/multiply/divide/negate, chained calc(x) with .toString() or template interpolation, nested operations only parenthesized). A .css.ts stylesheet 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-level consts holding a literal or other calc results. @devup-ui/react/compat/vanilla-extract-css-utils types it, and css-utils-literal-only reads its calls as the build does. New build errors: a calc operand outside a stylesheet the build cannot read, a calc read without being called, a calc(x) used as a value without .toString() (also in a stylesheet), an export other than calc, and a namespace import, require() or re-export of the package outside a stylesheet. Set importAliases: { '@vanilla-extract/css-utils': false } to keep the package
  • With the debug option, vanilla-extract style(rule, debugId) and styleVariants(..., 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, and keyframes still ignores its debug ID
  • vanilla-extract code Devup UI does not compile is a located build error however it is loaded, instead of slipping past the check on import declarations. New build errors while @vanilla-extract/css is aliased: @vanilla-extract/recipes and @vanilla-extract/sprinkles loaded by export … from, export *, require(), import x = require() or import() (an import already was); @vanilla-extract/dynamic loaded in any of these ways; and globalKeyframes imported from @vanilla-extract/css, which failed with a bare TypeError: not a callable function

@devup-ui/binding-darwin-arm64@0.1.0 → 0.2.0 - bindings/devup-ui-binding-darwin-arm64/package.json

Minor

  • Require Node.js 20 or later for the build-time packages: Node 18 is past its end of life and does not expose the globalThis.crypto the WASM engine reads. The plugins, plugin-utils, the WASM engine and the native bindings now declare engines.node >=20 (the ESLint plugin ^20.9.0 || >=21.1.0, as typescript-eslint 8 requires; the Vite plugin keeps >=22).

Patch

  • Add the public native build-time compiler with CommonJS and ESM types and eight OS, architecture and libc-specific optional packages. Validate exact native tarballs and publish platform artifacts before the root binding. Unsupported hosts and omitted native optional packages fail explicitly; source build errors and generated styling runtime are unchanged. Plugin engine selection is a separate phase.

@devup-ui/binding-darwin-x64@0.1.0 → 0.2.0 - bindings/devup-ui-binding-darwin-x64/package.json

Minor

  • Require Node.js 20 or later for the build-time packages: Node 18 is past its end of life and does not expose the globalThis.crypto the WASM engine reads. The plugins, plugin-utils, the WASM engine and the native bindings now declare engines.node >=20 (the ESLint plugin ^20.9.0 || >=21.1.0, as typescript-eslint 8 requires; the Vite plugin keeps >=22).

Patch

  • Add the public native build-time compiler with CommonJS and ESM types and eight OS, architecture and libc-specific optional packages. Validate exact native tarballs and publish platform artifacts before the root binding. Unsupported hosts and omitted native optional packages fail explicitly; source build errors and generated styling runtime are unchanged. Plugin engine selection is a separate phase.

@devup-ui/binding-linux-arm64-gnu@0.1.0 → 0.2.0 - bindings/devup-ui-binding-linux-arm64-gnu/package.json

Minor

  • Require Node.js 20 or later for the build-time packages: Node 18 is past its end of life and does not expose the globalThis.crypto the WASM engine reads. The plugins, plugin-utils, the WASM engine and the native bindings now declare engines.node >=20 (the ESLint plugin ^20.9.0 || >=21.1.0, as typescript-eslint 8 requires; the Vite plugin keeps >=22).

Patch

  • Add the public native build-time compiler with CommonJS and ESM types and eight OS, architecture and libc-specific optional packages. Validate exact native tarballs and publish platform artifacts before the root binding. Unsupported hosts and omitted native optional packages fail explicitly; source build errors and generated styling runtime are unchanged. Plugin engine selection is a separate phase.

@devup-ui/binding-linux-arm64-musl@0.1.0 → 0.2.0 - bindings/devup-ui-binding-linux-arm64-musl/package.json

Minor

  • Require Node.js 20 or later for the build-time packages: Node 18 is past its end of life and does not expose the globalThis.crypto the WASM engine reads. The plugins, plugin-utils, the WASM engine and the native bindings now declare engines.node >=20 (the ESLint plugin ^20.9.0 || >=21.1.0, as typescript-eslint 8 requires; the Vite plugin keeps >=22).

Patch

  • Add the public native build-time compiler with CommonJS and ESM types and eight OS, architecture and libc-specific optional packages. Validate exact native tarballs and publish platform artifacts before the root binding. Unsupported hosts and omitted native optional packages fail explicitly; source build errors and generated styling runtime are unchanged. Plugin engine selection is a separate phase.

@devup-ui/binding-linux-x64-gnu@0.1.0 → 0.2.0 - bindings/devup-ui-binding-linux-x64-gnu/package.json

Minor

  • Require Node.js 20 or later for the build-time packages: Node 18 is past its end of life and does not expose the globalThis.crypto the WASM engine reads. The plugins, plugin-utils, the WASM engine and the native bindings now declare engines.node >=20 (the ESLint plugin ^20.9.0 || >=21.1.0, as typescript-eslint 8 requires; the Vite plugin keeps >=22).

Patch

  • Add the public native build-time compiler with CommonJS and ESM types and eight OS, architecture and libc-specific optional packages. Validate exact native tarballs and publish platform artifacts before the root binding. Unsupported hosts and omitted native optional packages fail explicitly; source build errors and generated styling runtime are unchanged. Plugin engine selection is a separate phase.

@devup-ui/binding-linux-x64-musl@0.1.0 → 0.2.0 - bindings/devup-ui-binding-linux-x64-musl/package.json

Minor

  • Require Node.js 20 or later for the build-time packages: Node 18 is past its end of life and does not expose the globalThis.crypto the WASM engine reads. The plugins, plugin-utils, the WASM engine and the native bindings now declare engines.node >=20 (the ESLint plugin ^20.9.0 || >=21.1.0, as typescript-eslint 8 requires; the Vite plugin keeps >=22).

Patch

  • Add the public native build-time compiler with CommonJS and ESM types and eight OS, architecture and libc-specific optional packages. Validate exact native tarballs and publish platform artifacts before the root binding. Unsupported hosts and omitted native optional packages fail explicitly; source build errors and generated styling runtime are unchanged. Plugin engine selection is a separate phase.

@devup-ui/binding-win32-arm64-msvc@0.1.0 → 0.2.0 - bindings/devup-ui-binding-win32-arm64-msvc/package.json

Minor

  • Require Node.js 20 or later for the build-time packages: Node 18 is past its end of life and does not expose the globalThis.crypto the WASM engine reads. The plugins, plugin-utils, the WASM engine and the native bindings now declare engines.node >=20 (the ESLint plugin ^20.9.0 || >=21.1.0, as typescript-eslint 8 requires; the Vite plugin keeps >=22).

Patch

  • Add the public native build-time compiler with CommonJS and ESM types and eight OS, architecture and libc-specific optional packages. Validate exact native tarballs and publish platform artifacts before the root binding. Unsupported hosts and omitted native optional packages fail explicitly; source build errors and generated styling runtime are unchanged. Plugin engine selection is a separate phase.

@devup-ui/binding-win32-x64-msvc@0.1.0 → 0.2.0 - bindings/devup-ui-binding-win32-x64-msvc/package.json

Minor

  • Require Node.js 20 or later for the build-time packages: Node 18 is past its end of life and does not expose the globalThis.crypto the WASM engine reads. The plugins, plugin-utils, the WASM engine and the native bindings now declare engines.node >=20 (the ESLint plugin ^20.9.0 || >=21.1.0, as typescript-eslint 8 requires; the Vite plugin keeps >=22).

Patch

  • Add the public native build-time compiler with CommonJS and ESM types and eight OS, architecture and libc-specific optional packages. Validate exact native tarballs and publish platform artifacts before the root binding. Unsupported hosts and omitted native optional packages fail explicitly; source build errors and generated styling runtime are unchanged. Plugin engine selection is a separate phase.

@devup-ui/wasm@1.0.83 → 1.1.0 - bindings/devup-ui-wasm/package.json

Minor

  • Require Node.js 20 or later for the build-time packages: Node 18 is past its end of life and does not expose the globalThis.crypto the WASM engine reads. The plugins, plugin-utils, the WASM engine and the native bindings now declare engines.node >=20 (the ESLint plugin ^20.9.0 || >=21.1.0, as typescript-eslint 8 requires; the Vite plugin keeps >=22).

Patch

  • Enable atomHoist by default at two boundaries in Vite, Webpack, Rsbuild and Next Webpack, with numeric zero opting out and no effect in singleCss mode. Keep Next Turbopack in per-file mode until its shared-slot reservation lands, warning once for explicit positive atomHoist requests. Allocate shared and file-local short counter names through deterministic reserved slots instead of content names; preserve frozen route plans, dynamic !important, local keyframes, first-value responsive tokens, shared CSS updates and persisted placement. Bump the naming cache generation. Stabilize Vite dev-sheet module identity with independent content-write revisions, preserving cache busting for changed CSS text and unchanged build paths. Track inherited configuration inputs, serialize refreshes and drain owned engine work before releasing shared build ownership. Reuse exact-input semantic extraction only in eligible exclusive serve sessions, registering dependencies on every request without retaining CSS snapshots or replaying writes; builds continue extracting normally. No new build errors.
  • A project module re-exporting Devup UI (export { Box, css } from '@devup-ui/react', export * from '@devup-ui/react', export { styled as s }, export * as Devup, a default export of an import, chains of barrels and the compat entry) now works: a file importing Box or css from it compiles exactly as if it imported from the package, following the barrel through the resolver (relative paths, tsconfig paths, package exports), and hasDevupUI sees such a file. Members read from a namespace or default import of the package (Devup['css'], const { css } = Devup, Devup.css as a value) compile where the build can follow them, Devup.x for 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 unresolvable export * 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 is
  • Validate native and WASM compiler binding arguments with matching TypeErrors before state changes, preserve existing user exceptions and seed-array observations, and use the performance-accepted extraction wrappers. Invalid binding arguments now report the function, parameter and required type; located source build errors are unchanged.
  • Batch native entries and snapshot-length access, stream WASM file maps without trusting allocation hints, and reject seed copies with unvalidated trailing holes before either engine runs. Malformed seed headers now use the existing canonical TypeError; no new source build errors. Separately fix target-dependent demanded-name resolver callback order in the shared extractor: native and WASM now resolve demanded local names lexically while preserving pass order and callback multiplicity.
  • Test infrastructure: debug and test builds compile Boa (boa_parser, boa_engine, boa_ast) at opt-level 1, so a vanilla-extract stylesheet with a call nested in a chained call, such as g(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 errors
  • CI and test infrastructure: the workflow always runs the latest releases (the ubuntu-latest runner, the newest major version of every action, and the latest stable Rust, Bun, Node.js, wasm-pack, cargo-binstall, cargo-tarpaulin and changepacks), runs pull requests read-only and moves npm publishing and Pages deployment into jobs that run only on pushes to main, never creates or commits e2e baselines, and sets timeouts. The wasm package build now starts from an empty pkg/ and verify:dist rejects files of the removed lite export, its README describes the real API, state and errors, and a Bun test checks the JS/WASM interface. The README benchmark tables are generated from one checked result file in both languages with the CSS size in its own column.
  • Resolve Emotion ClassNames components, callback css/cx APIs and theme reads by lexical binding identity across compilation, numeric preprocessing, imported constants and mutation analysis. Ordinary shadowed callbacks, components and values retain their authored behavior while genuine outer APIs still compile without styling runtime. No new build-error categories.
  • Rewriting styled-components, Emotion and vanilla-extract imports keeps type-only imports type-only: import { type DefaultTheme, ThemeProvider } now leaves import type { DefaultTheme } on the package instead of a value import that made it a runtime dependency, and an import type declaration is left as written. spin.getName() on a keyframes() binding becomes the generated keyframes name instead of a call on a string that threw at runtime
  • The styled-components and Emotion compat ThemeProvider now gives its theme through React context: useTheme, withTheme and the new ThemeConsumer return the real theme object (an object merged over the outer theme, or what a theme function makes of it) instead of an empty Proxy of var() references, withTheme forwards refs, lets a caller's theme win and sets a displayName. Styles keep reading the CSS variables the provider declares. styled-components v6.4 createTheme is available from the compat entry, and ThemeConsumer and createTheme imports are redirected there instead of staying a runtime dependency on styled-components
  • Resolve native css() definitions composed from known rule objects and css() results through imported module chains. Later declarations replace earlier declarations at the same property, selector, breakpoint and layer, while earlier-only declarations remain. Imported composition chains with cycles, dynamic parts or unresolved imports now produce located build errors instead of silently deferring precedence to stylesheet order.
  • css(a, b) composing classes whose styles the build knows (a const bound to css() in the file, or a css() result another module exports with a rule object every value of which is known) merges their styles: a later part's declaration replaces an earlier one's for the same property, selector, breakpoint and layer, also under conditions (css(base, cond && danger)) and for ||/?? parts, where the classes used to be joined and the stylesheet order picked the winner. vanilla-extract style([a, b]) passes each composed style as its own argument, so the later one wins, and a style composed again later (style([a, b, a])) is kept. Classes the build does not know (strings, props, CSS Modules) are kept as they are
  • styled(Base) extending a styled component the file binds to a const renders Base's tag directly with Base's styles composed under its own, so the extension's declarations replace Base's for the same property, selector, breakpoint and layer instead of losing to them by stylesheet order; Base's attrs apply before the extension's. attrs merge as styled-components merges them: className is joined with the caller's, style is merged and other props replace earlier ones. On an element, a className or style spread after the explicit prop now wins, as React merges props in the order they are written
  • stylex.props() and stylex.attrs() merge namespaces this file creates key by key as StyleX does: a later namespace's key replaces an earlier one's, so props(red, blue) is blue and props(blue, red) is red, and a key set to null removes the earlier value; conditions (cond && styles.x, cond ? a : b) choose per key. Arguments the build cannot read key by key (namespaces from other modules, props, dynamic namespaces, include()) keep the previous joined behavior
  • Compose namespace-imported styled components, inline tagged CSS and exact CSS spreads with later styles winning, and compile conditional props rule objects and read-only function-local style shapes without a styling runtime. Local function captures keep lexical hygiene, so user names like rest, style or className never collide with generated code. Styled callbacks bound to read-only const arrow or function declarations compile like inline callbacks while keeping the original exports and live bindings. Emotion numbers on the left operand of OR and nullish whole-rule choices become px like the right operand. Preserve Emotion numeric units and captured values, read exact imported computations, and retain named CSS layer metadata through composition. Unknowable shapes and spreads keep located build errors, including an unknown whole-rule shape held by a local or shadowing binding named undefined; namespace css props report the same non-inlineable overlap error as named imports, and anonymous layers, invalid layer names, and component layer-order statements report located errors directing users to named layers and globalCss.
  • Respect source-order property replacement across conditional spreads in styled rule objects, and document that styled callbacks cannot return runtime class names. No new build errors; existing located Cannot compose errors remain unchanged.
  • Compose constant object rules in css tags without runtime styling, preserve lexical tag bindings and numeric-unit marks, and report authored build errors for mutated, escaped or unresolved object mixins and dynamic object leaves.
  • Avoid cloning unreferenced constant initializers and defer initialization analysis until constant reads need it. Extraction output and build errors are unchanged.
  • One-shot production builds with the Vite and webpack plugins (Next.js without Turbopack included) drop the component-selector markers no module selects. Each transform and the start-of-build scan report the markers they give and select; once every module is compiled, a marker no module selects or writes leaves the output chunks. When a module selects a component but the scan never read it (virtual module, a file compiled by another tool such as MDX, require.context / import.meta.glob / computed import(), or a file outside the scanned roots and entries), the build keeps every marker and warns with the module and the reason. The scan now also follows require.context and import.meta.glob calls whose arguments are written out. Warm webpack builds read the reports of modules restored from the persistent cache. Dev servers, watch builds, Turbopack and the Rsbuild and Bun plugins keep every marker.
  • Narrow CSS capture validation states and cover namespace tags, registered template composition, nested responsive rejection and bounded-call checker errors without changing runtime behavior.
  • Stylesheets without any rule are emitted empty instead of as a bare license banner, so the empty shared base sheet no longer repeats the banner in every per-file stylesheet that imports it. The banner names the version without a trailing comma (v1.0.83, not v1.0.83,). A new licenseBanner plugin option (default true) and the setLicenseBanner/isLicenseBanner engine functions turn the banner off; both engines emit identical output.
  • Preserve unitless legacy vendor numbers, classify vendor time values as milliseconds and emit the Opera vendor prefix correctly; reject nested responsive arrays and known dead unprefixed CSS property names with source-located build errors, while preserving supported experimental CSS, unknown properties and documented shorthands.
  • Emotion's css prop now compiles a const that chooses among style objects, as in const rules = on ? { color: 'red' } : { color: 'blue' }; <div css={rules} />. Before, it became className={rules} with no CSS. When only css props read the binding, each object (or array, or CSS text) compiles in the declaration to the classes Emotion would give it, with numbers read as px as 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.
  • Reuse a serialized stylesheet until the sheet or the atom-hoisting settings it reads change: getCss and the CSS a transform returns no longer serialize the same unchanged sheet again. The output is byte-identical.
  • Keep 100000-level heap stress coverage while reducing fixture construction overhead. No new build errors or runtime behavior changes.
  • Class names and file numbers no longer depend on the order files are processed in. Every plugin walks the files it can extract (the project's source and the included packages) before the first transform and numbers them in path order (a file collapsed into a bucket is numbered as the bucket, and only files that mention the package, StyleX or an aliased package take numbers) through the new seedFileMap, so identical builds give identical class prefixes, CSS file names and output hashes; in development, files that appear later are numbered after the existing ones. Styles are given class names in a fixed order, not the order of a hash set. The exported class, file and canonical maps are canonical JSON (sorted keys). Stylesheet evaluation (vanilla-extract) refuses Math.random(), Date.now(), new Date() and Date(), which differ between builds, with a build error; fixed dates such as new Date(0) are unchanged. resetBuildState starts a build from its own options: the prefix, atom hoisting, routes, buckets, names, numbers and styles an earlier build in the process left are cleared, and the prefix is set on every setup even when it is absent. Engine snapshots from concurrent transforms are written one after another per file, so an older snapshot is never written last. File lists are ordered by code point rather than the locale
  • Typography documents the emitted default breakpoints, and source-backed integration tests keep the public breakpoint lists and range bounds synchronized with the production defaults. No runtime changes or new build errors.
  • Emotion's now compiles at build time with no runtime: the element becomes what its child function ({ css, cx, theme }) => ... renders, each css and cx call becomes the classes it composes (later styles replace earlier ones; css reads strings as CSS text and its tagged templates split around mixins; cx keeps unknown classes, reads { name: condition } objects as conditional classes and composes nested css and cx calls), and theme.a.b in their values becomes var(--a-b). Numbers in css rules are px lengths, as Emotion reads them, and top-level constants are inlined. New build errors, each at file:line:col: a without exactly one child function taking { css, cx, theme } that gives what it renders at once (attributes, other children, rest or default parameters, async or generator functions, several statements); reading the theme other than as theme.a.b in a css value; using css or cx other than by calling them; a cx object with a spread, getter or method; parts css and cx cannot compose (runtime calls, spreads, a condition choosing between styles and classes). @devup-ui/react/compat exports ClassNames with the ClassNamesContent and ClassNamesArg types, and the @emotion/react declarations include them
  • Emotion and styled-components component selectors now compile at build time: a styled component the file defines that another style selects (${Child} { ... } in CSS text, [Child] or [&: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 properties
  • @emotion/css is aliased by default: css and keyframes compile like Devup UI's own (numbers in px, as Emotion reads them), injectGlobal declares global CSS. cx takes class names, as in Emotion: strings and runtime values are classes kept as written (falsy values are skipped), an object is a { name: condition } class map, arrays nest, and inline css() calls and css() classes compose with the rules css(a, b) uses. merge(className) splits what the build can read (string tokens, template literal parts) and composes the css() classes in it, keeping a runtime string it cannot split as it is. Namespace members, constant-string bracket access, const destructuring and const alias chains compile through these same named APIs with scope-aware binding resolution; numeric values retain Emotion units after constant inlining and build-time evaluation. The Emotion import disappears when no runtime-only member is used. Ambient declarations type the styling imports (cx(...args: ClassNamesArg[]), merge(className: string)). New located build errors: cx() cannot use a spread, a getter, a setter or a method in a class map, or a template literal call; merge() takes exactly one class string, not a spread or a template literal call; the root module has no default export, namespace member keys must be constant strings naming supported exports, and styling functions cannot be passed, mutated or re-exported. Optional styling reads/calls, namespace rest destructuring, styling defaults or nested patterns, non-const aliases, exported styling bindings and reads whose initialization order cannot be established are build errors instead of runtime dependencies. Styling loaded through require, import-equals or dynamic import must use static ES module imports; an unawaited dynamic namespace that the build cannot follow is also a located error. Its runtime-only APIs (cache, flush, hydrate, sheet, getRegisteredStyles) stay on @emotion/css, including their nested/default destructuring, optional reads and recognized runtime-loader access
  • Emotion's css prop compiles at build time while @emotion/react is aliased: on tags and Devup UI components always, and on every element once the file imports @emotion/react or @emotion/styled or names @emotion/react in a @jsxImportSource pragma; jsx, jsxs and jsxDEV from @emotion/react/jsx-runtime (or jsx-dev-runtime) and jsx from @emotion/react compile it too, so libraries built with Emotion's JSX runtime do as well. The prop becomes the element's className, with CSS variables in its style for values only the runtime gives: arrays and conditions compose with a later part replacing what an earlier one sets, css() classes the file knows compose by their styles, strings and templates are CSS text, css`` mixins split the text around them, a function of the theme reads theme.a.b as var(--a-b), unitless numbers are px as in Emotion (constants included), and a className holding known css() classes overrides the prop as Emotion's registered classes do. A styled component the file defines renders its tag in the element's place when the prop overrides its styles and it renders a tag with no attrs or props read and the element has no spread, as or forwardedAs. Emotion's JSX runtime imports become react/jsx-runtime, the pragma names react, and jsx comes from @devup-ui/react/compat (React's createElement); @devup-ui/react/compat/css-prop types the prop on React.Attributes. New build errors, each with file:line:column and the code: a css prop part the build cannot read (a call, an element), a style object declared inside a function or with let, a binding only running the module gives or code changes, a theme function that does more than return rules or reads the theme other than as theme.a.b in a value, an interpolation CSS text cannot place or a mixin inside a nested rule, and a css prop overriding a styled component's styles where its tag cannot be rendered in place. Composing css() with a part that reads a known binding (such as a keyframes name) now reads its value
  • Recognize Emotion jsxImportSource eligibility with the same exact header rules used for rewriting, preserve authored first-use cascade-layer order while composing css props, retain exact computed theme keys, and keep Emotion numeric-length pixel semantics when constant rule arrays are inlined. Unitless values and zero retain their existing behavior. Every valid css-prop form remains supported; invalid empty JSX css expressions retain main's located syntax error. No new build-error category is introduced.
  • Emotion's CacheProvider is available from the compat entry as a no-op that renders its children, and import { 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
  • In rule objects written against Emotion, styled-components or vanilla-extract, a property whose value is an array of literals (background: ['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
  • Emotion's now writes the rules a css() class gives it in the same base cascade layer as the rules of its objects, so its entries keep the order Emotion writes them in: in styles={[cssp { 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.
  • A project whose tsconfig.json (or jsconfig.json) builds JSX with Emotion (compilerOptions.jsxImportSource of @emotion/react, through extends and project references too) now compiles the css prop on every element of every file, and its .tsx and .jsx files are built with React's JSX runtime through a /** @jsxImportSource react */ pragma, which a file's own JSX pragma overrides, so the bundler no longer imports Emotion's runtime. The plugins read the setting into a new @emotion/react/jsx-runtime alias (importAliases can turn it off with false, and it is left out when @emotion/react is not aliased); @devup-ui/react/compat/emotion-jsx-runtime declares Emotion's JSX runtimes as React's so the project type-checks without Emotion installed. plugin-utils exports readJsxImportSource, and mergeImportAliases takes the JSX import source
  • Numbers in rules written against Emotion, styled-components or vanilla-extract now read as px lengths when a constant stands in for the literal, as they do for a literal written in place: css({ padding: gap }) with const gap = 8, styled.div({ margin: SIZE }), <Global styles={{ body: { margin: GAP } }} /> and the same with imported constants and constant style objects give 8px, while unitless properties keep bare numbers, 0 stays 0 and Devup shorthands such as p keep the spacing scale. css${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 errors
  • Emotion code the build cannot compile is a located build error instead of staying at runtime, and Emotion's cx merges the styles of classes css() gives in argument order, so cx(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 no withComponent; an @emotion/react import with no Devup UI equivalent (ThemeContext, withEmotionCache, a default or namespace import) while @emotion/react is aliased, naming the export; and @emotion/css/create-instance loaded by an import, re-export, require() or import() while @emotion/css is aliased
  • New createSession(), selectSession(id) and dropSession(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. selectSession and dropSession throw a TypeError for an id that is not an unsigned 32-bit integer, and an Error for an unknown session or for dropping session 0
  • The engine keeps its state per engine session: class and file numbering, routes, prefix, debug, atom hoisting, slot reservation, shorthands, theme tokens, Tailwind definitions, the stylesheet, the stylesheet caches and the module resolver move together when a session is switched. Session 0 is the only one until a host creates another, so a single app sees no change
  • style-order-range only checks styleOrder where the build reads it: a prop of a Devup UI component and a top-level key of a style object passed to css/globalCss/keyframes. A styleOrder key in nested data, in a prop value such as an element passed as a prop, or in a call of a function sharing a name with an Object.prototype member is no longer reported. The array, typography and media rules already skip non-style data, and css-utils-literal-only accepts a css()/keyframes() result held in a const inside a function. No new build errors.
  • Preserve exact JavaScript literal property keys in static lookups and generated finite class maps, independently of CSS numeric value normalization. Only fold standalone unary string coercion when its spelling is proven to agree with JavaScript Number; other values retain the existing conservative dynamic or located build-error path without a styling runtime.
  • Add regression coverage for extraction safety, property pruning and source-order behavior; remove unreachable post-flatten spread handling and consolidate unknown property-shape rejection. Extraction output and build errors are unchanged.
  • The extractor guide shows reproducible native-element output, generated CSS-variable bindings, and actual atomic CSS rather than obsolete class names. Documentation only: no new build errors.
  • Compile imported style utility calls before serializing dynamic JSX factory values, preserving lexical shadows and deterministic CSS-variable output. Existing located css/keyframes errors now also reject unreadable nested factory values instead of emitting missing runtime calls; no new error kind.
  • hasDevupUI takes the import aliases and is true for a file extraction changes: one importing a redirected package (@emotion/styled, ...), naming @emotion/react in a @jsxImportSource pragma, or in a project whose tsconfig jsxImportSource is @emotion/react, so the Bun plugin no longer skips files whose only Devup UI is Emotion's css prop or an aliased import. Aliases of Devup UI now compile like the original: export const B = Box, const c = css; export { c as cc }, export const D = Devup and export const C = Devup.css in 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 = Devup namespace aliases, and const inner = css declared 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 read
  • vanilla-extract's globalKeyframes(name, frames) now compiles in .css.ts/.css.js stylesheets, declaring @Keyframes under the name as written, instead of being a build error. globalCss() takes a '@Keyframes name' key the same way ('@Keyframes fade': { from: {...}, to: {...} }), which before wrote invalid CSS such as '@Keyframes fade from{...}'; keyframes declared by name go to the shared stylesheet. @devup-ui/react/compat declares globalKeyframes for @vanilla-extract/css. New build error at file:line:col: a '@Keyframes' key in globalCss() whose name is not letters, digits, '-' and '_' (or starts with a digit), or that sits inside an at-rule.
  • Global CSS keeps the order it is written in: globalCss rules, @import and @font-face now appear in source order within each file (the later of two equal rules wins as written, repeated imports and font faces count where they are written last), object globalCss declarations on the same selector keep their written order, and custom cascade layers are declared in the order files first use them (nested layers after their parent) instead of alphabetical order
  • Compile known imported styled withComponent calls without requiring an unused styling-package import; preserve semantic import boundaries and share relevance with plugin filtering. No new build errors.
  • A styled component another module defines now composes at build time exactly as one the file defines itself: styled(ImportedBase)(...), styled(ImportedBase).attrs(...), ImportedBase.withComponent(...) and the Emotion css prop on ImportedBase render the base's tag with the base's styles under their own (the later declaration wins per property, selector, breakpoint and layer), merge attrs in order and filter props by what the styles read and shouldForwardProp. The build reads the other module through the same module resolution imported constants use (relative paths, tsconfig paths, package exports, include libraries) and reports it as a dependency, so a change to it rebuilds the importing file. A definition the build cannot read exactly (a base only the runtime gives, an attrs or style expression reading a binding of the defining module, a module with a build error, an unresolvable module, an import cycle) stays a runtime component that wraps, as before. Every exported styled component now carries a marker class computed from its file and its export name alone, so ${ImportedChild} { ... } in CSS text and [ImportedChild] as a rule key select it from another file; the marker replaces the registry-ordered one, which two files could not compute alike. No new build errors: the css prop on an imported styled component now reports the same override error a local one does when its styles overlap the component's
  • Keep unknown element-prop spreads wholly as native pass-through data: their keys never select, replace or remove separately authored styles, regardless of order. Preserve fully known ordinary spread composition, canonical aliases, source-ordered once-only values and native className/style merging without spread-key styling variables, fallbacks or conversion code. Preserve exact imported enum and Math values including negative zero, lexical constants, binding-aware CommonJS require, React createElement calls, type-only imports, and compiled reset CSS tests. Retain located errors for intrinsically unreadable explicit styles, runtime styleOrder, unmovable lazy logical suspension, whole Devup UI namespaces escaping to runtime, and immediate lexical temporal-dead-zone reads. Native Emotion css spread restrictions and separate styled css overlap restrictions remain unchanged. Inline eager styled render stages, attrs merges and destructuring carriers into their existing render scope, and reuse scoped captures for CSS composition and StyleX units. Preserve per-instance dynamic component targets, parameter environments, getter and iterator effects, function names and call receivers while removing unnecessary generated arrow functions.
  • Attach extracted classes and authored CSS variables to jsx, jsxs and jsxDEV props wrapped in parentheses, as const or satisfies. Preserve source evaluation order, responsive and conditional styleOrder output, native className/style merging and whole unknown-spread pass-through. Syntax wrappers do not introduce spread replacement diagnostics or a styling runtime.
  • Keep leading JSX compiler pragmas through extraction, styled lowering, namespace rewrites and generated stylesheets with correct source maps. Enabled Emotion aliases keep the React JSX import-source compatibility bridge; other sources and opted-out Emotion are preserved. No new build errors.
  • A shorthand set across a boundary after a longhand it covers now wins, as the later style: css({ borderTopWidth: 2 }, { borderWidth: 1 }) keeps only border-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, so css({ 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 errors
  • Serialize the CSS a transform returns only when it is read: a read after later transforms or setting changes still returns the sheet as that transform left it. The Next.js loader and prewarm never read it, and the Webpack loader reads it only when it writes it, so single-CSS builds no longer serialize the whole sheet after every module. The output is byte-identical.
  • Render a property's literal array in Emotion, styled-components and vanilla-extract rules as each library's runtime does instead of as breakpoints: Emotion declares string-first arrays as ordered fallbacks, skipping null, undefined and booleans, and declares nothing for arrays starting with another value; styled-components joins the values with commas into one declaration; vanilla-extract declares every value verbatim as a fallback, also in .css.ts stylesheets that import @vanilla-extract/css. Devup UI shorthands and Devup UI's own APIs keep responsive arrays.
  • A style object declared with const inside a function and passed only to styling APIs now compiles when its entries are written out, including Emotion, styled-components and vanilla-extract aliases. Successful member, primitive and constant-condition folding accounts for erased semantic references, so mutation or extra-use paths keep the existing located refusal while safe style-only member reads compile. css() and styled() compose known conditional rule arrays with the controller read once. Whole-rule props callbacks preserve their original invocation scope, destructuring, defaults, rest and authored argument evaluation order, including covered reads and empty/static-only results; fixed dynamic values become CSS variables without a runtime rule-object interpreter. Nonzero numbers remain px lengths except for unitless properties, and proven theme paths remain static CSS variables. Implicit actual-props theme reads through own arguments or a first rest formal retain located errors with correct catch, loop, switch and var binding ownership. Named whole-rule callbacks that refer to their own binding, including metadata reads, now give a located error naming the callback and explaining that recursion is not compiled; a same-named type parameter cannot hide that value self-reference, while type-only names and actual value shadows still compile. Repeated preparation checks, traversal and error buffering are consolidated without changing output or existing diagnostics. Opaque calls in Emotion ClassNames cx remain located errors until their result is proven unable to carry Devup style classes; only that allowance is deferred. Other located errors remain: attrs chained after styles, callbacks without one immediate explicit rule object, and local style objects also read elsewhere or holding unprovable style structure. No styling runtime or helper is added.
  • Report extraction, module-resolution and stylesheet execution failures at their original source locations with the cause and repair. Reject recoverable syntax errors, nondeterministic build-time reads, synthetic descriptor/function-source and legacy accessor reflection, and unsafe stylesheet execution fallbacks instead of silently changing CSS. Preserve module resolver and serialization exceptions, evaluate transitive helper side effects, and prevent placeholder-name collisions from losing styles. Match import package names only at exact or slash-delimited boundaries so sibling data packages remain external. Retain helper CSS loads in evaluation order with deduplicated portable relative specifiers and query suffixes, without CSS content dependencies. Report missing CSS or incompatible path roots as located errors, and reject host-recorded unknown CSS export observations even when caught; unused bindings, object passing and typeof follow default TypeScript/JavaScript import semantics.
  • A longhand now wins over a shorthand that covers it, as StyleX's property-specificity policy and atomic CSS expect: rules of one selector and breakpoint were sorted by property name, so border-width came after border-top-width and place-items after align-items and the shorthand won. Each property now sorts right after the last shorthand covering it (all first); 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
  • MDX documents are extracted after the MDX plugin compiles them: the engine reads an .mdx filename as the JavaScript module (with or without JSX) an MDX compiler makes of it instead of rejecting the extension, the Vite plugin extracts .mdx in a post transform, and the webpack and Rsbuild plugins in a post loader; Next.js with Turbopack and the Bun plugin still leave MDX untransformed
  • Exercise the production native adapter in the root Rust coverage report without preparation for plain Cargo tests, and deterministically order namespace resolver traversal and changed-constant diagnostics. Reduce native per-call control costs while preserving callbacks and public outputs; prevent private Number coercions, global String use for BigInts, Array.from use for byte diagnostics, and incorrect Symbol.iterator exception conversion. No newly rejected source or styling runtime.
  • The native binding now rejects a module resolver result with an empty path in the engine itself, as WASM does, instead of relying on the JavaScript adapter alone: both report malformed module resolver result: path must be a non-empty string at the import that requested it
  • Statically known css() results used as nested rule values expand into their source rules under each top-level comma-separated selector, preserving responsive values, nested selectors, layers and style order without runtime styling. Unknown rule sources retain a located build error naming the value and its static-value requirement.
  • Accept JSX in .js, .mjs and .cjs throughout extraction without changing TypeScript dialects or plain JavaScript output, and pass parsed source-map objects to webpack callbacks for Next SWC compatibility. Malformed relevant source now fails with located parser diagnostics instead of unlocated parser-panic messages or silently recovered output.
  • CSS blocks no longer end with a redundant ; before }: StyleX defineVars(), createTheme(), typed-variable @property, positionTry() and viewTransitionClass() rules, and the variables the runtime createTheme() GlobalStyle declares, now separate declarations with ; only between them, as the rest of the generated CSS already does. The CSS is equivalent and slightly smaller.
  • Preserve complete template interpolations when extracting style values: fold exact pure template text and keep dynamic element values in CSS variables without dropping side effects. Standalone css() values that cannot be known at build time now reach the existing located build error instead of silently losing their interpolations.
  • Read a style object key that holds an object and names no style property as a nested selector, as Emotion and styled-components do, in css(), globalCss(), styled object styles, the css prop and the Emotion and styled-components imports: 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 as hover stays that selector as in the selectors prop, and :, ::, [ and & keys keep applying to the element. Style properties, Devup UI shorthands such as p, string values and JSX props keep their meaning.
  • Reserve existing short counter class, variable, keyframe and raw-file slots in physical input order before Bun, webpack, Rsbuild and Next webpack extraction. Watch revisions append sorted slots without renumbering. No new source build errors or styling runtime; unknown virtual, generated and opaque outside-inventory inputs retain observable residual allocation.
  • Canonicalize complete exported property records, use portable content keyframe identities and short debug keyframe counters, and advance atomNamingVersion to 3. No new build errors.
  • Preserve quoted CSS text during selector substitution, media-query folding and template interpolation placement, and resume optimization after bad-string newlines without changing EOF string contents. No new styling runtime or build-error kind is added.
  • Keep quoted strings in CSS values, template blocks and selectors byte for byte: a number, color, space, comma, semicolon, brace, parenthesis or comment marker inside quotes is data, so content: '0.5' no longer becomes '.5'. The text around a string is still optimized, with no styling runtime and no new build errors.
  • Refresh dependencies, including Oxc 0.156, wasm-bindgen 0.2.130, parse5 8.1 and Rsbuild 2.3. Preserve the React 18 compatibility fixture while updating its build tooling.
  • Add an internal aggregate compiler-state reset for isolated tests, scoped native cleanup and Next test-cache isolation; verify real Bun registration callbacks and packed production consumers across bundlers and browsers. No new application build errors are introduced.
  • A source file deleted or renamed in watch mode or the dev server no longer leaves its styles behind: its globalCss, its own stylesheet and the class names handed out in it are dropped, and it leaves the bucket it collapsed into. The engine gains removeFile(filename) (native and WASM), which Vite calls on a delete watch 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
  • Resolving the imports of a file parses it once to find where it references each module, instead of once per import resolved. A component with ten imports was parsed again ten times during extraction just to locate possible resolver errors; diagnostics are unchanged
  • A responsive length or shadow $token inside a responsive array now reads var(--token) instead of the token's first raw value: px={['8px', null, '$containerX']} showed the mobile 16px at index 2 where the theme sets --containerX to 32px, and w={['$containerX']} ignored theme variants such as compact. The slot still emits one class at its own breakpoint
  • Options that styled-components' StyleSheetManager and Emotion's createCache() would apply at runtime, and the inert compat StyleSheetManager and CacheProvider silently dropped, are now located build errors (file:line:col, cause and fix): stylisPlugins, shouldForwardProp and namespace of StyleSheetManager from an aliased package, and spread props on it; stylisPlugins of 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 as key stays accepted
  • Resolve compiled styling APIs and components by lexical binding so shadowed local names remain ordinary JavaScript and JSX, and preserve StyleX conditions exactly once in argument order. Conditions needing capture storage now report located build errors in parameter defaults, class field initializers, and statement frames visible to direct eval when safe local storage is unavailable; move the value into a variable in a safe statement body.
  • The limitations page documents why every exported styled component carries a component-selector marker class even when no selector in its file names it: a module importing it may select or extend it, and each file is built without knowing its importers. No runtime changes or new build errors.
  • Pin the component-selector marker rule with tests: a styled component a file keeps to itself (not exported) and no selector in that file names renders without a marker class, also when it is only extended or given withComponent there; selected or exported components keep it. The limitations page explains why exported components keep it until the build can know that no module selects them. No runtime changes or new build errors.
  • Selectors: a nested rule without & 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; content keeps the quotes of its strings (content: 'x', content: ""); params go on the pseudo-class that takes them, so _groupNthChild gives :is(...):nth-child(2n) .a also when nested; a bare selectors key 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 _name prop or selector key that names nothing (_notASelector, selectors={{ div: ... }}), and a string under a selector that is not CSS text (_hover="external-class")
  • Custom shorthand targets are constrained to supported camelCase/kebab-case CSS properties, built-in aliases and valid custom properties. All five build adapters normalize options at creation before registration or extraction, including Next.js production cache reuse. Unsupported targets fail registration atomically with the original shorthand name, target and zero-based index; previously registered shorthands remain unchanged. New devup-ui option errors expose structured logical shorthands paths without inventing source coordinates. Eighteen dead unprefixed property names are rejected.
  • styled-components v6 passes shouldForwardProp the 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 evaluates shouldForwardProp only 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.
  • Validate explicit static styleOrder as an integer from 1 to 254 or its canonical decimal digit string, consistently in extraction and lint, including composed Emotion css props. Keep order metadata out of library px conversion. Invalid static values and conditional branches now produce located build errors instead of silently changing cascade order.
  • Preserve extractor callback, theme-read and rule-array behavior while removing redundant preparation and unreachable analysis paths. Add Linux-coverable regression cases without coverage exclusions. No new build errors.
  • Every component compiled from styled carries a styledComponentId property, set once per file by a small helper, and the compat isStyledComponent returns true for it as styled-components does instead of always returning false
  • Components made with styled-components' styled now pass props on as styled-components v6 does: without shouldForwardProp, every prop reaches the rendered element, a DOM tag included, even one the styles read, except $ props, as and theme. 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's shouldForwardProp stays a build error: keep props off the element with $ transient props or .withConfig({ shouldForwardProp }).
  • styled['div'] and styled[`div`] compile as styled.div does, in tagged templates and calls and before .attrs / .withConfig, for Emotion, styled-components and Devup UI's own styled, keeping Emotion's numbers as pixels. A computed tag the build cannot read (styled[tag]) or that no styled. member could spell (styled['my-element']) stays a located build error
  • Emotion's <Global styles> takes a css() class holding rules under selectors, an array of rule objects and classes (false, null and undefined skipped) and a function of the theme whose theme.a.b reads become var(--a-b); Emotion's target and styled-components' componentId become a stable class on the element that extending components render too; and a label: declaration in CSS text is dropped instead of written as invalid CSS. New build errors: a target or componentId that is not one class name written as a string; defaultProps assigned to a styled component, which compiles to a function component whose defaultProps React 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 as theme.a.b
  • A styled component now takes the displayName its library gives it: a string displayName in styled-components' .withConfig(), or the label option of Emotion's styled(tag, { label }), becomes the compiled component's displayName, as React DevTools shows it. The classes it renders are unchanged. No new build errors.
  • Styled components the build generates are wrapped in React's forwardRef, so a ref passed to them reaches the element they render on React 18 as well as React 19; the file imports forwardRef from react when it defines one
  • Styled components no longer pass every prop to the tag they render: $ props, theme and the props their style functions or attrs read are kept away from a tag unless it takes them as attributes, and shouldForwardProp (Emotion options or styled-components withConfig) is evaluated at build time. A shouldForwardProp the 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 written
  • Styled components render what their as prop names, defaulting to the tag or component they were defined with, and pass forwardedAs on as as, as styled-components and Emotion do; as used 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 as target (a tag name or a component JSX can name), where it used to call a method the generated function does not have and throw
  • A theme prop 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: a theme attribute on an element of a styled component whose styles read the theme; wrap the element in a ThemeProvider with that theme instead
  • StyleX APIs compile as StyleX defines them: a dynamic style may set its parameters under conditions ((size) => ({ width: { default: 100, ':hover': size } })), each condition taking its own variable; a computed condition key may read a defineConsts() constant ([constants.wide]); a types.*() variable in defineVars() registers @property with its default as the initial value; a '--global' key keeps its name and colors['--global'] reads it; positionTry() and viewTransitionClass() bindings read as their names in create(), 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 becoming var(--name); viewTransitionClass() takes the group, imagePair, old and new groups and styles their pseudo-elements. New build errors: a types.*() variable without a default, types.integer() given a fraction, an unknown types.* helper, and a viewTransitionClass() key other than group, imagePair, old and new or a group that is not an object of declarations
  • stylex.attrs() gives the dynamic CSS variables it sets as style attribute 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 declares style as a string
  • A key written after ...stylex.include(base.root) in stylex.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 later include() replaces what came before, and stylex.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 errors
  • Every plugin takes stylex: { styleResolution }, StyleX's babel plugin option of the same name, and the engines take it through the new setStylexStyleResolution(). 'property-specificity' stays the default. 'application-order' gives a static stylex.create() key the null resets StyleX's table lists for the longhands it covers (and reads its aliases, marginStart as margin-inline-start), so the key applied last wins in stylex.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' into padding-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 given firstThatWorks() fallbacks, all under application-order and a listStyle StyleX cannot sort under legacy-expand-shorthands; an unknown styleResolution is a configuration error (StylexConfigError). Devup UI's own APIs ignore the option
  • A StyleX API Devup UI does not compile is a located build error naming it, instead of being dropped from the compiled set while its calls stay StyleX calls that throw at runtime. New build error: an export of @stylexjs/stylex outside create, props, attrs, keyframes, defineVars, createTheme, createThemeContract, defineConsts, positionTry, viewTransitionClass, firstThatWorks, include and types (such as when, env or defaultMarker), imported by name or read as a member of the package imported whole
  • Compile StyleX when.ancestor(), when.descendant(), when.anySibling(), when.siblingBefore(), when.siblingAfter(), defineMarker() and defaultMarker() at build time, as @stylexjs/babel-plugin does, instead of reporting them as unsupported: a when.*() 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 class x-default-marker, and defineMarker() names a class after its file and export that importing modules read too. @devup-ui/react types when, defineMarker, defaultMarker and markers in props(). Pseudo-classes nested in each other are now written in the order StyleX sorts them, so :hover inside :focus reads :focus:hover. New build errors: a when.*() 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; a defineMarker() call with arguments or not bound to a named export of the module's top level; a defaultMarker() call with arguments
  • Tailwind classes in a className: each class compiles on its own and every class Tailwind does not define (custom, plugin and analytics classes) stays as written, where any recognized class used to rebuild the whole className without them and could rewrite part of another class; a class touching a template interpolation (icon-${name}) is left as written, and template classNames no longer get spaces inserted around interpolations. A class whose variant is not understood stays as written instead of applying unconditionally; variants follow Tailwind v4: stacked variants compose (hover:focus: matches the element itself), hover is guarded by @media (hover: hover), group-/peer- use the group/peer marker classes (and group-hover/name), and data-, aria-, has-, nth-, , **, supports-[…] and [&…]/[@media …] variants compile. Utilities emit all their declarations (size-, rounded-t-, truncate, sr-only, not-sr-only, text-sm with its line height, text-sm/6, leading-), translate/rotate/scale/skew compose through Tailwind's individual properties and registered variables (@Property) with negative values kept negative, and arbitrary values follow Tailwind's grammar: spaces for underscores except in url() and var() names, _ for an underscore, spaces around math operators, type hints, [property:value] and (--variable) shorthands. Words that only share a utility's prefix (select-wrapper, order-summary, cursor-foo) are no longer compiled
  • Order standalone nonresponsive hover-capability guards within their selector group so active, focus and disabled styles can override hover. Keep responsive Tailwind hover and Devup selector prop ordering unchanged. No new build errors.
  • More of Tailwind CSS v4 compiles: container queries (@sm:, @max-md:, @min-[400px]:, @sm/main:) and @container utilities, mask-* (all but the gradient masks), text-shadow-, inset-shadow-, font-variant-numeric utilities (tabular-nums and the like), 3D transforms (rotate-x/y/z, translate-z, scale-z, translate-3d, scale-3d, transform-3d, backface-, perspective-, perspective-origin-), contain- and outline-hidden (with its forced-colors fallback). The project's Tailwind CSS is read further: functional @Utility with --value() and --modifier(), @apply in @Utility, and theme(--name) in arbitrary values; classes of @plugin entries stay as written. A className now compiles the classes of cn()/twMerge() calls whose arguments are all static (merged as tailwind-merge does, the later class wins), of consts bound to class strings, and of cva() calls (base, variants, compound variants). The Rsbuild plugin reads the Tailwind CSS again and compiles every module again when it changes, and the Bun plugin reads it again. No new build errors
  • Tailwind classes in a className follow Tailwind CSS v4: colors are the v4 default palette (oklch) and the colors and shadows of devup.json theme are usable as Tailwind theme values (bg-primary, text-text, shadow-card, as var(--token)); the opacity modifier (bg-red-500/50, /[71.37%], /(--alpha)) mixes with color-mix as v4 does; a trailing or leading ! makes every declaration important; blur, brightness, contrast, grayscale, hue-rotate, invert, saturate, sepia and their backdrop-* forms compose through Tailwind's custom properties instead of overwriting filter and backdrop-filter; gradients use bg-linear-, bg-conic- and bg-radial-* with from-, via- and to-* composing through the gradient variables (bg-gradient-to-* is not defined by v4 and stays as written); animate-* brings the @Keyframes it names and transition, duration, delay and ease follow v4; space-* and divide-* apply to the children like v4 (:where(& > :not(:last-child))); @Property rules are emitted only for the custom properties a class uses. Anything the build cannot reproduce exactly (drop-shadow-*) stays as written in the className. No new build errors
  • Tailwind classes in a className read the Tailwind CSS of the project: the file that imports tailwindcss (the tailwind.css option of devup.json, else a conventional path) gives @theme variables (colors, spacing, shadows, blurs, radii, easings, animations with their @Keyframes, default transitions, breakpoints), @Utility utilities and @custom-variant variants, and the Vite, webpack and Next.js plugins read it again when it or a CSS file it imports changes. Anything that cannot be read exactly, and the classes of namespaces the build does not read, stay as written. More of Tailwind CSS v4 compiles: ring-, inset-ring-, ring-offset-* and drop-shadow-* compose with shadows and filters, borders and outlines draw in --tw-border-style and --tw-outline-style (a border now shows its style), line-clamp, text decoration, border-spacing, logical and scroll spacing, tables, perspective, font-stretch and more; the arguments of clsx(), classnames() and classNames() and [...].join(' ') compile in place. Radii follow v4 (rounded-sm is 0.25rem, rounded-full is calc(infinity * 1px)). No new build errors
  • A styled-components or Emotion style function reading the theme by literal keys, such as p => 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 as p => p.theme, p => p.theme.brand() or theme.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 throw
  • Theme tokens of different kinds can no longer silently share a CSS variable: a color card and a shadow card both 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, length and shadow (names compared after dots become dashes, so gray.100 and gray-100 clash too)
  • Styled components now remove every runtime prop whose name starts with $ 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
  • Generate React JSX-runtime calls for styled components in non-JSX source modules while preserving JSX and TSX output. No new build errors.
  • Reject unresolved imports and font-face values, misplaced font-template expressions and unusable functional-selector arguments with located build errors, preserving static values and genuine optional absence without a styling runtime.
  • Refresh all dependency ranges and regenerated lockfiles with the latest dependency-check-updates CLI, including Oxc 0.154, sourcemap 9, Next, React, Panda, Playwright, ESLint, Vinext and WASM dependencies. Preserve the existing hybrid CommonJS bundler language through exact top-level declaration-goal classification without changing parser AST, diagnostics or source-type metadata; real invalid syntax, including nested ES declarations, still produces located parser errors. Keep React 18 and 19 peer support and the React 18 fixture pins. No new build errors for valid supported styling inputs or styling runtime.
  • Update dependencies to their latest releases and migrate Oxc while preserving exact JavaScript string identity, static CSS output, and React 18/19 compatibility. Final CSS text, values, keys, and required evaluation-module specifiers containing unpaired UTF-16 surrogates now fail at build time with source locations instead of becoming lossy text or dynamic styling.
  • Update dependencies to their latest releases: Oxc 0.159 (with oxc_sourcemap 10, which oxc_codegen 0.159 now uses), napi 3.16 and typescript-eslint 8.73. Extracted CSS and class names are unchanged.
  • While @vanilla-extract/css is aliased, importing @vanilla-extract/recipes or @vanilla-extract/sprinkles is a build error naming the file, line and column: those packages generate CSS Devup UI does not compile, so their rules used to be silently missing from the stylesheet. The error says to write the styles with css(), or to disable the alias and build with the vanilla-extract plugin. Type-only imports are allowed
  • @vanilla-extract/css-utils is aliased by default and its calc compiles to the strings the package builds (calc.add/subtract/multiply/divide/negate, chained calc(x) with .toString() or template interpolation, nested operations only parenthesized). A .css.ts stylesheet 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-level consts holding a literal or other calc results. @devup-ui/react/compat/vanilla-extract-css-utils types it, and css-utils-literal-only reads its calls as the build does. New build errors: a calc operand outside a stylesheet the build cannot read, a calc read without being called, a calc(x) used as a value without .toString() (also in a stylesheet), an export other than calc, and a namespace import, require() or re-export of the package outside a stylesheet. Set importAliases: { '@vanilla-extract/css-utils': false } to keep the package
  • With the debug option, vanilla-extract style(rule, debugId) and styleVariants(..., 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, and keyframes still ignores its debug ID
  • vanilla-extract code Devup UI does not compile is a located build error however it is loaded, instead of slipping past the check on import declarations. New build errors while @vanilla-extract/css is aliased: @vanilla-extract/recipes and @vanilla-extract/sprinkles loaded by export … from, export *, require(), import x = require() or import() (an import already was); @vanilla-extract/dynamic loaded in any of these ways; and globalKeyframes imported from @vanilla-extract/css, which failed with a bare TypeError: not a callable function
  • An ordinary module (not .css.ts / .css.js) can now read what a vanilla-extract stylesheet exports: the vars objects of createThemeContract, createTheme and createGlobalTheme, theme classes, createVar variables and style class names. The imported stylesheet is extracted the way the bundler extracts it, so style({ margin: vars.space }) or <Box p={vars.space} /> compiles to the custom property the stylesheet's own CSS declares and style([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 error
  • A Rust panic inside the WASM compiler now fails the call with a JavaScript Error that names it an internal Devup UI bug, gives the panic message and its Rust location, and says to report it and restart the build, instead of an opaque RuntimeError: unreachable.
  • Skip source-map generation in the codeExtractWithoutSourceMap WASM export while preserving extracted code, CSS and dependencies. Add real WASM and Next loader regressions for map-enabled and map-disabled extraction. No new build errors.

@devup-ui/bun-plugin@1.0.22 → 1.0.23 - packages/bun-plugin/package.json

Patch

  • When an optional setup step fails and the build goes on without it (Vite, webpack and Bun file numbering, the webpack and Rsbuild import graphs, the webpack stylesheet warm-up), print one warning naming the step, the cause and what the build loses instead of continuing silently. A project without a src directory stays quiet. No new build errors.
  • The Bun plugin takes an include option, as the other plugins do, and compiles the published .js files of the listed packages. Before, only .js under @devup-ui/ was loaded, so an uncompiled library's components threw Cannot run on the runtime. Each name matches that whole package, also in pnpm and Bun stores, and not the dependencies in its own node_modules
  • Bun plugin works with Bun.build: 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 (debug option). 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
  • Compile every source kind under the Bun runtime: .mts, .cts, and .js and .cjs files outside node_modules join .ts, .tsx, .jsx and .mjs. CommonJS keeps its exports: Bun does not run CommonJS an onLoad callback returns, so the runtime plugin runs the module itself and hands Bun an ES module exporting its module.exports to require() and import. Source loads are synchronous, so require() works on compiled files too.
  • Under the Bun runtime, watch devup.json and every file of its extends chain 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.
  • Under the Bun runtime, rewrite devup-ui.css only when a module adds or removes styles, from the sheet the extraction already serialized, instead of serializing and writing the whole sheet after every compiled module.
  • Stylesheets without any rule are emitted empty instead of as a bare license banner, so the empty shared base sheet no longer repeats the banner in every per-file stylesheet that imports it. The banner names the version without a trailing comma (v1.0.83, not v1.0.83,). A new licenseBanner plugin option (default true) and the setLicenseBanner/isLicenseBanner engine functions turn the banner off; both engines emit identical output.
  • Class names and file numbers no longer depend on the order files are processed in. Every plugin walks the files it can extract (the project's source and the included packages) before the first transform and numbers them in path order (a file collapsed into a bucket is numbered as the bucket, and only files that mention the package, StyleX or an aliased package take numbers) through the new seedFileMap, so identical builds give identical class prefixes, CSS file names and output hashes; in development, files that appear later are numbered after the existing ones. Styles are given class names in a fixed order, not the order of a hash set. The exported class, file and canonical maps are canonical JSON (sorted keys). Stylesheet evaluation (vanilla-extract) refuses Math.random(), Date.now(), new Date() and Date(), which differ between builds, with a build error; fixed dates such as new Date(0) are unchanged. resetBuildState starts a build from its own options: the prefix, atom hoisting, routes, buckets, names, numbers and styles an earlier build in the process left are cleared, and the prefix is set on every setup even when it is absent. Engine snapshots from concurrent transforms are written one after another per file, so an older snapshot is never written last. File lists are ordered by code point rather than the locale
  • A broken devup.json is reported instead of silently loading an empty theme. New errors: <file> is not valid JSON: <cause>, <file> must hold a JSON object, and devup.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.ts is 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
  • A project whose tsconfig.json (or jsconfig.json) builds JSX with Emotion (compilerOptions.jsxImportSource of @emotion/react, through extends and project references too) now compiles the css prop on every element of every file, and its .tsx and .jsx files are built with React's JSX runtime through a /** @jsxImportSource react */ pragma, which a file's own JSX pragma overrides, so the bundler no longer imports Emotion's runtime. The plugins read the setting into a new @emotion/react/jsx-runtime alias (importAliases can turn it off with false, and it is left out when @emotion/react is not aliased); @devup-ui/react/compat/emotion-jsx-runtime declares Emotion's JSX runtimes as React's so the project type-checks without Emotion installed. plugin-utils exports readJsxImportSource, and mergeImportAliases takes the JSX import source
  • hasDevupUI takes the import aliases and is true for a file extraction changes: one importing a redirected package (@emotion/styled, ...), naming @emotion/react in a @jsxImportSource pragma, or in a project whose tsconfig jsxImportSource is @emotion/react, so the Bun plugin no longer skips files whose only Devup UI is Emotion's css prop or an aliased import. Aliases of Devup UI now compile like the original: export const B = Box, const c = css; export { c as cc }, export const D = Devup and export const C = Devup.css in 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 = Devup namespace aliases, and const inner = css declared 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 read
  • Keep leading JSX compiler pragmas through extraction, styled lowering, namespace rewrites and generated stylesheets with correct source maps. Enabled Emotion aliases keep the React JSX import-source compatibility bridge; other sources and opted-out Emotion are preserved. No new build errors.
  • A devup.json extends entry 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.
  • Reserve existing short counter class, variable, keyframe and raw-file slots in physical input order before Bun, webpack, Rsbuild and Next webpack extraction. Watch revisions append sorted slots without renumbering. No new source build errors or styling runtime; unknown virtual, generated and opaque outside-inventory inputs retain observable residual allocation.
  • Compile .mts, .cts and .cjs modules in every plugin, Turbopack and the import graph, and resolve ./a.js, ./a.mjs and ./a.cjs imports to their TypeScript sources. Resolve package exports in the package's own order with the conditions of the bundler: Vite's resolve.conditions, the ESM conditions of webpack and Rspack per environment, and the target and conditions of Bun. Atom hoisting in webpack and Rsbuild plans over the src and app directories of the working directory and of the bundler root, not src alone. 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 .js and .cjs modules. No new build errors.
  • Resolve relative plugin options (devupFile, distDir, cssDir), the tsconfig and the webpack extraction ids against the bundler's project root (Vite root, webpack context, Rsbuild rootPath, Next's project directory for webpack builds, Bun.build root) instead of process.cwd(), so builds started from a parent directory as turbo or nx do read the project's devup.json and write its df. Builds started from the project root are unchanged. When devupFile is not set and only the working directory holds a devup.json, that file is still read and a one-time warning says to move it next to the project or set devupFile. Class names may change once for webpack and Next webpack builds run from a parent directory, because files are now numbered relative to the project root.
  • Resolve the imports the extractor follows against the bundler's project root (webpack's context, the Rsbuild root, the root of Bun.build) instead of the working directory, so a build started from a parent directory, as monorepo tools do, reads that project's tsconfig.json paths and resolves the relative imports of its root-relative webpack ids under the project.
  • Add an internal aggregate compiler-state reset for isolated tests, scoped native cleanup and Next test-cache isolation; verify real Bun registration callbacks and packed production consumers across bundlers and browsers. No new application build errors are introduced.
  • Custom shorthand targets are constrained to supported camelCase/kebab-case CSS properties, built-in aliases and valid custom properties. All five build adapters normalize options at creation before registration or extraction, including Next.js production cache reuse. Unsupported targets fail registration atomically with the original shorthand name, target and zero-based index; previously registered shorthands remain unchanged. New devup-ui option errors expose structured logical shorthands paths without inventing source coordinates. Eighteen dead unprefixed property names are rejected.
  • Every plugin takes stylex: { styleResolution }, StyleX's babel plugin option of the same name, and the engines take it through the new setStylexStyleResolution(). 'property-specificity' stays the default. 'application-order' gives a static stylex.create() key the null resets StyleX's table lists for the longhands it covers (and reads its aliases, marginStart as margin-inline-start), so the key applied last wins in stylex.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' into padding-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 given firstThatWorks() fallbacks, all under application-order and a listStyle StyleX cannot sort under legacy-expand-shorthands; an unknown styleResolution is a configuration error (StylexConfigError). Devup UI's own APIs ignore the option
  • More of Tailwind CSS v4 compiles: container queries (@sm:, @max-md:, @min-[400px]:, @sm/main:) and @container utilities, mask-* (all but the gradient masks), text-shadow-, inset-shadow-, font-variant-numeric utilities (tabular-nums and the like), 3D transforms (rotate-x/y/z, translate-z, scale-z, translate-3d, scale-3d, transform-3d, backface-, perspective-, perspective-origin-), contain- and outline-hidden (with its forced-colors fallback). The project's Tailwind CSS is read further: functional @Utility with --value() and --modifier(), @apply in @Utility, and theme(--name) in arbitrary values; classes of @plugin entries stay as written. A className now compiles the classes of cn()/twMerge() calls whose arguments are all static (merged as tailwind-merge does, the later class wins), of consts bound to class strings, and of cva() calls (base, variants, compound variants). The Rsbuild plugin reads the Tailwind CSS again and compiles every module again when it changes, and the Bun plugin reads it again. No new build errors
  • Tailwind classes in a className read the Tailwind CSS of the project: the file that imports tailwindcss (the tailwind.css option of devup.json, else a conventional path) gives @theme variables (colors, spacing, shadows, blurs, radii, easings, animations with their @Keyframes, default transitions, breakpoints), @Utility utilities and @custom-variant variants, and the Vite, webpack and Next.js plugins read it again when it or a CSS file it imports changes. Anything that cannot be read exactly, and the classes of namespaces the build does not read, stay as written. More of Tailwind CSS v4 compiles: ring-, inset-ring-, ring-offset-* and drop-shadow-* compose with shadows and filters, borders and outlines draw in --tw-border-style and --tw-outline-style (a border now shows its style), line-clamp, text decoration, border-spacing, logical and scroll spacing, tables, perspective, font-stretch and more; the arguments of clsx(), classnames() and classNames() and [...].join(' ') compile in place. Radii follow v4 (rounded-sm is 0.25rem, rounded-full is calc(infinity * 1px)). No new build errors
  • A theme that cannot be loaded or registered (a broken devup.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
  • Refresh all dependency ranges and regenerated lockfiles with the latest dependency-check-updates CLI, including Oxc 0.154, sourcemap 9, Next, React, Panda, Playwright, ESLint, Vinext and WASM dependencies. Preserve the existing hybrid CommonJS bundler language through exact top-level declaration-goal classification without changing parser AST, diagnostics or source-type metadata; real invalid syntax, including nested ES declarations, still produces located parser errors. Keep React 18 and 19 peer support and the React 18 fixture pins. No new build errors for valid supported styling inputs or styling runtime.
  • Update dependencies to their latest releases and migrate Oxc while preserving exact JavaScript string identity, static CSS output, and React 18/19 compatibility. Final CSS text, values, keys, and required evaluation-module specifiers containing unpaired UTF-16 surrogates now fail at build time with source locations instead of becoming lossy text or dynamic styling.
  • Add shared native/WASM compiler selection, structural compiler types and exact native platform-load diagnostics for build plugins.

@devup-ui/components@0.1.60 → 0.1.61 - packages/components/package.json

Patch

  • Select, SelectContainer, SelectOption, SelectDivider, Toggle, RadioGroup and the Stepper parts (StepperContainer, StepperDecreaseButton, StepperIncreaseButton, StepperInput) forward their ref, so a ref reaches the element on React 18 too, where a function component never receives ref as 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 the role="switch" element; StepperInput hands the <input>, or the <output> of a type="text" stepper
  • Add the ProgressBar component: a progressbar with its range that fills a bar to value out of max, or with variant="step" one segment per finished step, and can show the progress as a percent or done/total
  • Add the Search component: an <input type="search"> with a magnifier icon built on Input, which calls onSearch with 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
  • Keep unknown element-prop spreads wholly as native pass-through data: their keys never select, replace or remove separately authored styles, regardless of order. Preserve fully known ordinary spread composition, canonical aliases, source-ordered once-only values and native className/style merging without spread-key styling variables, fallbacks or conversion code. Preserve exact imported enum and Math values including negative zero, lexical constants, binding-aware CommonJS require, React createElement calls, type-only imports, and compiled reset CSS tests. Retain located errors for intrinsically unreadable explicit styles, runtime styleOrder, unmovable lazy logical suspension, whole Devup UI namespaces escaping to runtime, and immediate lexical temporal-dead-zone reads. Native Emotion css spread restrictions and separate styled css overlap restrictions remain unchanged. Inline eager styled render stages, attrs merges and destructuring carriers into their existing render scope, and reuse scoped captures for CSS composition and StyleX units. Preserve per-instance dynamic component targets, parameter environments, getter and iterator effects, function names and call receivers while removing unnecessary generated arrow functions.
  • Package READMEs are refreshed: the benchmark tables show the current CI run and are regenerated with the root README from benchmark-results.json, the examples show the current generated class names instead of fixed d0/d1 names, and the Korean README link points to the repository; @devup-ui/components and @devup-ui/reset-css name their own package and install line and add a short usage section; the ESLint README notes that preset rules can report the same code. Documentation only
  • Canonicalize complete exported property records, use portable content keyframe identities and short debug keyframe counters, and advance atomNamingVersion to 3. No new build errors.
  • RadioGroup is a radiogroup with an optional label, its radios share a name (generated when not given) so arrow keys move between them, and it keeps the typed values of its options: false, 0 and '' stay selectable and onChange receives the option's own value rather than a string. Button-variant radios are visually hidden instead of display:none, so they stay focusable and show a focus ring, and the default radio's focus outline is valid CSS and shown on :focus-visible. Checkbox uses an id it is given for its labels as well as its input, where the labels used to point at a generated id
  • @devup-ui/react and @devup-ui/components take React as a peer of ^18 || ^19 instead of * 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
  • Refresh dependencies, including Oxc 0.156, wasm-bindgen 0.2.130, parse5 8.1 and Rsbuild 2.3. Preserve the React 18 compatibility fixture while updating its build tooling.
  • Select follows the listbox pattern: the trigger has aria-haspopup, aria-controls and opens with ArrowDown/ArrowUp; the popup is a listbox (aria-multiselectable for checkbox selects) whose options carry role=option, aria-selected and aria-disabled; opening focuses the selected or first option, arrows/Home/End move between enabled options, Enter/Space choose one, and Escape or choosing closes the popup and returns focus to the trigger. An outside click on a controlled select now calls onOpenChange(false) instead of changing hidden internal state
  • Close the Select list and return focus to the trigger when a SelectOption with its own onClick is chosen; the handler still replaces the value update.
  • Each Select trigger now gets its own id from the Select id or a generated id, so several Selects on a page no longer share the id -trigger and each listbox is labelled by its own trigger; no new build errors.
  • Toggle is an accessible switch: role=switch with aria-checked, focusable with a visible focus ring, toggled by Space and Enter, labelled through aria-label or aria-labelledby, and submitted under the name it is given; when disabled it leaves the tab order, ignores keys and its hidden input is disabled
  • Components behave for keyboard, screen readers and both React 18 and 19: Button, Input and Textarea no longer force generic aria-labels (the visible text or an associated label names them), Input and Textarea mark errors with aria-invalid and aria-describedby pointing at the message, a loading Button sets aria-busy, is disabled by default (disableWhileLoading) and announces loadingLabel, Input clear dispatches a real change event instead of a fabricated one, color customization variables sit on the container so every part sees them and every public color key matches its CSS custom property (new keys inputDisabledBackground, inputDisabledText, inputPlaceholder, primaryBackground, Textarea disabledBackground and disabledText), Select positions against the viewport and clears the opposite inset, SelectTrigger asChild composes the child onClick, onKeyDown and ref with its own, Stepper counts without a controlled value, keeps its bound and disabled safeguards and renders its text mode as an output element. Select no longer forces aria-labels over its trigger, options, confirm button and container: an option is named by its content, the listbox by its trigger (aria-labelledby) or by what the caller passes. ThemeScript takes nonce and other script props and never aborts on blocked storage or missing matchMedia, follows the system while no theme was chosen and themes saved in other tabs; getTheme, setTheme and initTheme are safe on the server and initTheme returns a function that stops following. reset-css clips accessible-hidden content as sanitize.css does. No new build errors.
  • Input readOnly now reaches the native input, making the field read-only while keeping its clear button hidden; no new build errors.
  • Button, Checkbox, Input, Radio and Textarea forward their ref to the button, input or textarea they render, so a ref reaches the form element on React 18 as well as React 19
  • Refresh all dependency ranges and regenerated lockfiles with the latest dependency-check-updates CLI, including Oxc 0.154, sourcemap 9, Next, React, Panda, Playwright, ESLint, Vinext and WASM dependencies. Preserve the existing hybrid CommonJS bundler language through exact top-level declaration-goal classification without changing parser AST, diagnostics or source-type metadata; real invalid syntax, including nested ES declarations, still produces located parser errors. Keep React 18 and 19 peer support and the React 18 fixture pins. No new build errors for valid supported styling inputs or styling runtime.
  • Update dependencies to their latest releases and migrate Oxc while preserving exact JavaScript string identity, static CSS output, and React 18/19 compatibility. Final CSS text, values, keys, and required evaluation-module specifiers containing unpaired UTF-16 surrogates now fail at build time with source locations instead of becoming lossy text or dynamic styling.

@devup-ui/eslint-plugin@1.0.22 → 1.1.0 - packages/eslint-plugin/package.json

Minor

  • Require Node.js 20 or later for the build-time packages: Node 18 is past its end of life and does not expose the globalThis.crypto the WASM engine reads. The plugins, plugin-utils, the WASM engine and the native bindings now declare engines.node >=20 (the ESLint plugin ^20.9.0 || >=21.1.0, as typescript-eslint 8 requires; the Vite plugin keeps >=22).

Patch

  • The @devup-ui/react README and the css-utils-literal-only rule docs link their mention of build errors to the new Build Errors reference (https://devup-ui.com/docs/build-errors), which lists the build errors grouped by API; the docs sidebar lists the page after Supported Syntax & Limitations, whose Build errors section links to it. Documentation only: no new build errors
  • Fix sparse trailing-null autofixes to preserve authored values, complete parenthesized syntax and earlier holes using token-based edit boundaries while removing the maximal trailing run of nulls and holes only when the last element is canonical literal null; preserve regular-expression and BigInt literals without validating regex syntax, preserve existing comment and trailing-comma handling, remove an unreachable AST guard and restore complete behavior coverage on the latest Bun without exclusions or new build errors.
  • Declare the Node.js versions the build-time packages need (Node 22 for the Vite plugin, which calls Promise.withResolvers) and replace the unrestricted vite, next, @rsbuild/core and typescript-eslint peers with the oldest major each plugin is written against: Vite 5, Next.js 13, Rsbuild 1 and typescript-eslint 8.
  • ESLint rules now check exactly what the build reads. The array, typography, media and styleOrder rules and css-utils-literal-only follow the import aliases the build compiles by default (@emotion/react, @emotion/styled, styled-components, @vanilla-extract/css) and the rules of styled (styled.div({...}), styled("div", {...}), styled(Base)({...}, {...}); not .attrs()), createGlobalStyle({...}) and the styles of Emotion Global, and check and fix a module-level const object that only styles read. Vanilla-extract stylesheets (.css.ts/.css.js) are no longer read as Devup UI. New rule no-runtime-read reports css/keyframes/styled/Box read as a value ("X is 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.
  • style-order-range only checks styleOrder where the build reads it: a prop of a Devup UI component and a top-level key of a style object passed to css/globalCss/keyframes. A styleOrder key in nested data, in a prop value such as an element passed as a prop, or in a call of a function sharing a name with an Object.prototype member is no longer reported. The array, typography and media rules already skip non-style data, and css-utils-literal-only accepts a css()/keyframes() result held in a const inside a function. No new build errors.
  • Do not treat composition arrays as responsive property values in the duplicate, trailing-null or single-value array rules. Preserve composition arrays and their nested responsive property diagnostics.
  • Read the build plugin's package and importAliases options from the shared ESLint settings settings['@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 with false. A setting the build plugin would not take stops the lint run with its path. No new build errors.
  • Lint @emotion/css like the build does: its css, keyframes and injectGlobal get the same rules as Devup UI's css, keyframes and globalCss, so a dynamic value the build rejects is reported in the editor too
  • Report a function given as a value to css, globalCss, keyframes and createGlobalStyle (also through Emotion, styled-components and vanilla-extract), such as createGlobalStylecolor: ${(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.
  • Stop no-duplicate-value, no-useless-responsive and no-useless-tailing-nulls from reporting and fixing property arrays in the rules of Emotion, styled-components and vanilla-extract, where the build declares them as fallbacks in one rule rather than breakpoints. Fixing [4, 4, 8] to [4, null, 8] there turned the fallbacks into breakpoints. Packages added with importAliases and createGlobalStyle still read arrays as Devup UI does and are still checked. No new build or lint errors.
  • Declare the ESLint versions the ESLint plugin runs on (the range typescript-eslint 8 supports) and require a compatible @devup-ui/webpack-plugin from the Next.js plugin instead of any version.
  • Add no-useless-fallback, a warning in the recommended config for a property's array in Emotion and vanilla-extract rules whose values are all strings every browser supports, so only the last fallback applies; it points to Devup UI's responsive arrays when breakpoints were meant. Arrays using var(), env(), vendor prefixes, newer viewport, container or line height units, newer color functions or clamp()/min()/max() are left alone, as are non-literal values, Devup UI shorthands and styled-components rules, which join the values with commas. No autofix.
  • Package READMEs are refreshed: the benchmark tables show the current CI run and are regenerated with the root README from benchmark-results.json, the examples show the current generated class names instead of fixed d0/d1 names, and the Korean README link points to the repository; @devup-ui/components and @devup-ui/reset-css name their own package and install line and add a short usage section; the ESLint README notes that preset rules can report the same code. Documentation only
  • Refresh dependencies, including Oxc 0.156, wasm-bindgen 0.2.130, parse5 8.1 and Rsbuild 2.3. Preserve the React 18 compatibility fixture while updating its build tooling.
  • Validate explicit static styleOrder as an integer from 1 to 254 or its canonical decimal digit string, consistently in extraction and lint, including composed Emotion css props. Keep order metadata out of library px conversion. Invalid static values and conditional branches now produce located build errors instead of silently changing cascade order.
  • @devup-ui/no-runtime-read accepts styled['div'] and styled[`div`] where they build a component, as the build now compiles them; a computed tag it cannot read (styled[tag]) is still reported
  • Add opt-in type-aware diagnostics for provably runtime-only Devup style spreads and repair TypeScript 6 compatibility subpath resolution for typed project services. No new build errors or styling runtime.
  • Refresh all dependency ranges and regenerated lockfiles with the latest dependency-check-updates CLI, including Oxc 0.154, sourcemap 9, Next, React, Panda, Playwright, ESLint, Vinext and WASM dependencies. Preserve the existing hybrid CommonJS bundler language through exact top-level declaration-goal classification without changing parser AST, diagnostics or source-type metadata; real invalid syntax, including nested ES declarations, still produces located parser errors. Keep React 18 and 19 peer support and the React 18 fixture pins. No new build errors for valid supported styling inputs or styling runtime.
  • Update dependencies to their latest releases and migrate Oxc while preserving exact JavaScript string identity, static CSS output, and React 18/19 compatibility. Final CSS text, values, keys, and required evaluation-module specifiers containing unpaired UTF-16 surrogates now fail at build time with source locations instead of becoming lossy text or dynamic styling.
  • Update dependencies to their latest releases: Oxc 0.159 (with oxc_sourcemap 10, which oxc_codegen 0.159 now uses), napi 3.16 and typescript-eslint 8.73. Extracted CSS and class names are unchanged.
  • @vanilla-extract/css-utils is aliased by default and its calc compiles to the strings the package builds (calc.add/subtract/multiply/divide/negate, chained calc(x) with .toString() or template interpolation, nested operations only parenthesized). A .css.ts stylesheet 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-level consts holding a literal or other calc results. @devup-ui/react/compat/vanilla-extract-css-utils types it, and css-utils-literal-only reads its calls as the build does. New build errors: a calc operand outside a stylesheet the build cannot read, a calc read without being called, a calc(x) used as a value without .toString() (also in a stylesheet), an export other than calc, and a namespace import, require() or re-export of the package outside a stylesheet. Set importAliases: { '@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

  • Require Node.js 20 or later for the build-time packages: Node 18 is past its end of life and does not expose the globalThis.crypto the WASM engine reads. The plugins, plugin-utils, the WASM engine and the native bindings now declare engines.node >=20 (the ESLint plugin ^20.9.0 || >=21.1.0, as typescript-eslint 8 requires; the Vite plugin keeps >=22).

Patch

  • Enable atomHoist by default at two boundaries in Vite, Webpack, Rsbuild and Next Webpack, with numeric zero opting out and no effect in singleCss mode. Keep Next Turbopack in per-file mode until its shared-slot reservation lands, warning once for explicit positive atomHoist requests. Allocate shared and file-local short counter names through deterministic reserved slots instead of content names; preserve frozen route plans, dynamic !important, local keyframes, first-value responsive tokens, shared CSS updates and persisted placement. Bump the naming cache generation. Stabilize Vite dev-sheet module identity with independent content-write revisions, preserving cache busting for changed CSS text and unchanged build paths. Track inherited configuration inputs, serialize refreshes and drain owned engine work before releasing shared build ownership. Reuse exact-input semantic extraction only in eligible exclusive serve sessions, registering dependencies on every request without retaining CSS snapshots or replaying writes; builds continue extracting normally. No new build errors.
  • webpack (and Next.js on webpack) and Rsbuild watch every config devup.json extends, as Vite does, and reload the theme when one is edited, added or deleted. Rsbuild did not reload devup.json itself in dev before; webpack only watched a devup.json that existed when the build started
  • When the Turbopack coordinator closes, at process exit included, it writes the newest CSS, sheet and class/file maps still waiting to be written synchronously. Before, it only started an asynchronous flush that exit never let finish, so the last writes could be lost
  • Isolate the coordinator port file per owning process when another live next dev/build holds it, record the owner pid, and report port, pid and recovery when the coordinator is missing or unreachable
  • One-shot production builds with the Vite and webpack plugins (Next.js without Turbopack included) drop the component-selector markers no module selects. Each transform and the start-of-build scan report the markers they give and select; once every module is compiled, a marker no module selects or writes leaves the output chunks. When a module selects a component but the scan never read it (virtual module, a file compiled by another tool such as MDX, require.context / import.meta.glob / computed import(), or a file outside the scanned roots and entries), the build keeps every marker and warns with the module and the reason. The scan now also follows require.context and import.meta.glob calls whose arguments are written out. Warm webpack builds read the reports of modules restored from the persistent cache. Dev servers, watch builds, Turbopack and the Rsbuild and Bun plugins keep every marker.
  • Stylesheets without any rule are emitted empty instead of as a bare license banner, so the empty shared base sheet no longer repeats the banner in every per-file stylesheet that imports it. The banner names the version without a trailing comma (v1.0.83, not v1.0.83,). A new licenseBanner plugin option (default true) and the setLicenseBanner/isLicenseBanner engine functions turn the banner off; both engines emit identical output.
  • Class names and file numbers no longer depend on the order files are processed in. Every plugin walks the files it can extract (the project's source and the included packages) before the first transform and numbers them in path order (a file collapsed into a bucket is numbered as the bucket, and only files that mention the package, StyleX or an aliased package take numbers) through the new seedFileMap, so identical builds give identical class prefixes, CSS file names and output hashes; in development, files that appear later are numbered after the existing ones. Styles are given class names in a fixed order, not the order of a hash set. The exported class, file and canonical maps are canonical JSON (sorted keys). Stylesheet evaluation (vanilla-extract) refuses Math.random(), Date.now(), new Date() and Date(), which differ between builds, with a build error; fixed dates such as new Date(0) are unchanged. resetBuildState starts a build from its own options: the prefix, atom hoisting, routes, buckets, names, numbers and styles an earlier build in the process left are cleared, and the prefix is set on every setup even when it is absent. Engine snapshots from concurrent transforms are written one after another per file, so an older snapshot is never written last. File lists are ordered by code point rather than the locale
  • A broken devup.json is reported instead of silently loading an empty theme. New errors: <file> is not valid JSON: <cause>, <file> must hold a JSON object, and devup.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.ts is 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
  • A project whose tsconfig.json (or jsconfig.json) builds JSX with Emotion (compilerOptions.jsxImportSource of @emotion/react, through extends and project references too) now compiles the css prop on every element of every file, and its .tsx and .jsx files are built with React's JSX runtime through a /** @jsxImportSource react */ pragma, which a file's own JSX pragma overrides, so the bundler no longer imports Emotion's runtime. The plugins read the setting into a new @emotion/react/jsx-runtime alias (importAliases can turn it off with false, and it is left out when @emotion/react is not aliased); @devup-ui/react/compat/emotion-jsx-runtime declares Emotion's JSX runtimes as React's so the project type-checks without Emotion installed. plugin-utils exports readJsxImportSource, and mergeImportAliases takes the JSX import source
  • Declare the Node.js versions the build-time packages need (Node 22 for the Vite plugin, which calls Promise.withResolvers) and replace the unrestricted vite, next, @rsbuild/core and typescript-eslint peers with the oldest major each plugin is written against: Vite 5, Next.js 13, Rsbuild 1 and typescript-eslint 8.
  • Declare the ESLint versions the ESLint plugin runs on (the range typescript-eslint 8 supports) and require a compatible @devup-ui/webpack-plugin from the Next.js plugin instead of any version.
  • Compile known imported styled withComponent calls without requiring an unused styling-package import; preserve semantic import boundaries and share relevance with plugin filtering. No new build errors.
  • Serialize the CSS a transform returns only when it is read: a read after later transforms or setting changes still returns the sheet as that transform left it. The Next.js loader and prewarm never read it, and the Webpack loader reads it only when it writes it, so single-CSS builds no longer serialize the whole sheet after every module. The output is byte-identical.
  • A devup.json extends entry 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.
  • Turbopack loaders talk to the coordinator more robustly: the CSS loader keeps a port per port file, so two apps in one process no longer read each other's CSS; a loader whose coordinator restarted reads the new port and sends the request there instead of failing; a port file that is still being written is waited for instead of read as a bad port. New errors: Coordinator port file <file> names no valid port and Coordinator 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)
  • Turbopack apps in one process no longer share one coordinator: coordinators are kept per resolved 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
  • Reserve shared class slots in path order before next dev extracts, so Turbopack class names no longer depend on request order
  • Fail a Turbopack build whose CSS the coordinator cannot prove complete, naming the files that never extracted, instead of answering with partial CSS
  • Turbopack: forget the styles of source files deleted or renamed while no dev server ran, when the persisted state is restored, and write the pruned state at once. Write the persisted sheet, class map and file map atomically (temporary file renamed over the target, retrying Windows sharing errors), followed by a manifest of their hashes; a restore that finds files from different writes starts fresh instead of mixing them. State written by earlier releases, without a manifest, still restores.
  • Keep webpack out of the declarations @devup-ui/next-plugin publishes. restoreSessionState was typed through the internal engine loader, which pulled @devup-ui/webpack-plugin and webpack's own types (ajv, enhanced-resolve, schema-utils and more, 72 files) into the type check of every app whose next.config.ts imports the plugin. Next's type check now reads 72 fewer files and its .next/cache/.tsbuildinfo is about 26 KB smaller. The public API is unchanged.
  • Next apps with app/ or pages/ at the project root (no src/) are prewarmed and waited on like src/ 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 .next and .git
  • Count Pages Router modules and every App Router route file as Next route entries, so Pages Router projects get a deterministic CSS completion set
  • Write coordinator state to a per-process directory when another live next dev or next build already uses the same distDir, so concurrent processes no longer overwrite each other's sheet and class/file maps
  • Answer a repeated Turbopack extraction of an unchanged module (the server and client compiles of one file) from the coordinator's per-file transform cache instead of running the engine again
  • Turbopack honors the debug option (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
  • Reload the theme under Turbopack next dev when devup.json, a config it extends or the project's Tailwind CSS changes, and re-run the loaders that depend on it
  • Extract Devup UI used directly in .mdx documents under Next.js with Turbopack and @next/mdx, in either wrapping order. The source rule no longer skips the renamed .mdx.tsx module @next/mdx produces; the loader extracts it under the document's own path so its styles stay in the sheet. Production builds number MDX documents with the sources and make the stylesheet wait for MDX route files and the documents compiled sources import by a relative path.
  • Reconstruct the complete deterministic Next webpack stylesheet after each server, edge and client compiler reset, including accepted external package dependency closures, so delivered CSS matches rendered classes in per-file and single-CSS modes. Keep production CSS request paths stable across build IDs so persistent webpack cache cannot bypass the CSS loader. Genuine production prewarm collection, read and extraction failures now fail the build instead of silently dropping styles; failed initialization releases its build session without leaking styles into unrelated builds.
  • Use identity-bound Windows job membership for Next webpack lifecycle assertions so unrelated historical PID reuse cannot invalidate completed cleanup. Preserve genuine production, fault, descendant and fixture-removal checks. No runtime behavior change or new build errors.
  • Accept JSX in .js, .mjs and .cjs throughout extraction without changing TypeScript dialects or plain JavaScript output, and pass parsed source-map objects to webpack callbacks for Next SWC compatibility. Malformed relevant source now fails with located parser diagnostics instead of unlocated parser-panic messages or silently recovered output.
  • Reserve existing short counter class, variable, keyframe and raw-file slots in physical input order before Bun, webpack, Rsbuild and Next webpack extraction. Watch revisions append sorted slots without renumbering. No new source build errors or styling runtime; unknown virtual, generated and opaque outside-inventory inputs retain observable residual allocation.
  • Package READMEs are refreshed: the benchmark tables show the current CI run and are regenerated with the root README from benchmark-results.json, the examples show the current generated class names instead of fixed d0/d1 names, and the Korean README link points to the repository; @devup-ui/components and @devup-ui/reset-css name their own package and install line and add a short usage section; the ESLint README notes that preset rules can report the same code. Documentation only
  • Compile .mts, .cts and .cjs modules in every plugin, Turbopack and the import graph, and resolve ./a.js, ./a.mjs and ./a.cjs imports to their TypeScript sources. Resolve package exports in the package's own order with the conditions of the bundler: Vite's resolve.conditions, the ESM conditions of webpack and Rspack per environment, and the target and conditions of Bun. Atom hoisting in webpack and Rsbuild plans over the src and app directories of the working directory and of the bundler root, not src alone. 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 .js and .cjs modules. No new build errors.
  • Resolve relative plugin options (devupFile, distDir, cssDir), the tsconfig and the webpack extraction ids against the bundler's project root (Vite root, webpack context, Rsbuild rootPath, Next's project directory for webpack builds, Bun.build root) instead of process.cwd(), so builds started from a parent directory as turbo or nx do read the project's devup.json and write its df. Builds started from the project root are unchanged. When devupFile is not set and only the working directory holds a devup.json, that file is still read and a one-time warning says to move it next to the project or set devupFile. Class names may change once for webpack and Next webpack builds run from a parent directory, because files are now numbered relative to the project root.
  • Add the types-only @devup-ui/plugin-utils/types entry (resolved through exports, and typesVersions for node10 resolution) holding the types the plugins' published declarations name. The Next plugin's declarations now import it instead of the whole package, so a next.config.ts type check loads 7 of plugin-utils' declaration files instead of 22 (.next/cache/.tsbuildinfo about 3.5 KB smaller on the benchmark apps).
  • Skip @devup-ui/react in 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.css and a- instead of devup-ui-23.css and x-); the styles are unchanged.
  • A production prewarm no longer fails the build on a file it cannot extract. The Next.js prewarm still extracts every source file, but a file that does not parse (for example dead source no route imports) is now skipped with a warning naming the file and the error. If Next.js or webpack compiles that file, its loader still fails the build with the same error. Output for projects without such files is unchanged.
  • Add an internal aggregate compiler-state reset for isolated tests, scoped native cleanup and Next test-cache isolation; verify real Bun registration callbacks and packed production consumers across bundlers and browsers. No new application build errors are introduced.
  • A source file deleted or renamed in watch mode or the dev server no longer leaves its styles behind: its globalCss, its own stylesheet and the class names handed out in it are dropped, and it leaves the bucket it collapsed into. The engine gains removeFile(filename) (native and WASM), which Vite calls on a delete watch 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
  • Read each source file once per build in the passes that run before the bundler. The import graph, the class-slot reservation and the prewarm read the same files, and a Next production build runs them once per compiler (server, edge, client): they now share a stamp-checked source cache (withSourceCache / readSource in 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.
  • Custom shorthand targets are constrained to supported camelCase/kebab-case CSS properties, built-in aliases and valid custom properties. All five build adapters normalize options at creation before registration or extraction, including Next.js production cache reuse. Unsupported targets fail registration atomically with the original shorthand name, target and zero-based index; previously registered shorthands remain unchanged. New devup-ui option errors expose structured logical shorthands paths without inventing source coordinates. Eighteen dead unprefixed property names are rejected.
  • A Next production build (webpack or Turbopack) of an app that serves exactly one route now writes its styles into the shared devup-ui.css, the same layout singleCss: true gives, unless singleCss is 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.mdx and other route files count too), no import() that splits off a chunk, and no source file outside that route. next dev and multi-route apps keep the per-file layout and their output.
  • Every plugin takes stylex: { styleResolution }, StyleX's babel plugin option of the same name, and the engines take it through the new setStylexStyleResolution(). 'property-specificity' stays the default. 'application-order' gives a static stylex.create() key the null resets StyleX's table lists for the longhands it covers (and reads its aliases, marginStart as margin-inline-start), so the key applied last wins in stylex.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' into padding-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 given firstThatWorks() fallbacks, all under application-order and a listStyle StyleX cannot sort under legacy-expand-shorthands; an unknown styleResolution is a configuration error (StylexConfigError). Devup UI's own APIs ignore the option
  • Tailwind classes in a className read the Tailwind CSS of the project: the file that imports tailwindcss (the tailwind.css option of devup.json, else a conventional path) gives @theme variables (colors, spacing, shadows, blurs, radii, easings, animations with their @Keyframes, default transitions, breakpoints), @Utility utilities and @custom-variant variants, and the Vite, webpack and Next.js plugins read it again when it or a CSS file it imports changes. Anything that cannot be read exactly, and the classes of namespaces the build does not read, stay as written. More of Tailwind CSS v4 compiles: ring-, inset-ring-, ring-offset-* and drop-shadow-* compose with shadows and filters, borders and outlines draw in --tw-border-style and --tw-outline-style (a border now shows its style), line-clamp, text decoration, border-spacing, logical and scroll spacing, tables, perspective, font-stretch and more; the arguments of clsx(), classnames() and classNames() and [...].join(' ') compile in place. Radii follow v4 (rounded-sm is 0.25rem, rounded-full is calc(infinity * 1px)). No new build errors
  • A theme that cannot be loaded or registered (a broken devup.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
  • Pass the Turbopack loaders only what coordinator mode reads (the port file, the theme files and, for the CSS loader, watch), plus a short key of the setup state that re-runs them when it changes. Next serializes the resolved config into .next/required-server-files.{js,json}, which ships with the app; it no longer carries the default sheet, class map, file map, theme or file paths. CSS and JavaScript output is unchanged.
  • Refresh all dependency ranges and regenerated lockfiles with the latest dependency-check-updates CLI, including Oxc 0.154, sourcemap 9, Next, React, Panda, Playwright, ESLint, Vinext and WASM dependencies. Preserve the existing hybrid CommonJS bundler language through exact top-level declaration-goal classification without changing parser AST, diagnostics or source-type metadata; real invalid syntax, including nested ES declarations, still produces located parser errors. Keep React 18 and 19 peer support and the React 18 fixture pins. No new build errors for valid supported styling inputs or styling runtime.
  • Add shared native/WASM compiler selection, structural compiler types and exact native platform-load diagnostics for build plugins.
  • Skip source-map generation in the codeExtractWithoutSourceMap WASM export while preserving extracted code, CSS and dependencies. Add real WASM and Next loader regressions for map-enabled and map-disabled extraction. No new build errors.

@devup-ui/plugin-utils@1.0.17 → 1.1.0 - packages/plugin-utils/package.json

Minor

  • Require Node.js 20 or later for the build-time packages: Node 18 is past its end of life and does not expose the globalThis.crypto the WASM engine reads. The plugins, plugin-utils, the WASM engine and the native bindings now declare engines.node >=20 (the ESLint plugin ^20.9.0 || >=21.1.0, as typescript-eslint 8 requires; the Vite plugin keeps >=22).

Patch

  • Enable atomHoist by default at two boundaries in Vite, Webpack, Rsbuild and Next Webpack, with numeric zero opting out and no effect in singleCss mode. Keep Next Turbopack in per-file mode until its shared-slot reservation lands, warning once for explicit positive atomHoist requests. Allocate shared and file-local short counter names through deterministic reserved slots instead of content names; preserve frozen route plans, dynamic !important, local keyframes, first-value responsive tokens, shared CSS updates and persisted placement. Bump the naming cache generation. Stabilize Vite dev-sheet module identity with independent content-write revisions, preserving cache busting for changed CSS text and unchanged build paths. Track inherited configuration inputs, serialize refreshes and drain owned engine work before releasing shared build ownership. Reuse exact-input semantic extraction only in eligible exclusive serve sessions, registering dependencies on every request without retaining CSS snapshots or replaying writes; builds continue extracting normally. No new build errors.
  • When an optional setup step fails and the build goes on without it (Vite, webpack and Bun file numbering, the webpack and Rsbuild import graphs, the webpack stylesheet warm-up), print one warning naming the step, the cause and what the build loses instead of continuing silently. A project without a src directory stays quiet. No new build errors.
  • New openCompilerSession(compiler): it opens an engine session of its own on a shared compiler and returns { id, compiler, close }. Every function of the scoped compiler selects the session before it runs, so two apps in one process keep their numbering, sheet, theme and settings apart; close() drops the session
  • One-shot production builds with the Vite and webpack plugins (Next.js without Turbopack included) drop the component-selector markers no module selects. Each transform and the start-of-build scan report the markers they give and select; once every module is compiled, a marker no module selects or writes leaves the output chunks. When a module selects a component but the scan never read it (virtual module, a file compiled by another tool such as MDX, require.context / import.meta.glob / computed import(), or a file outside the scanned roots and entries), the build keeps every marker and warns with the module and the reason. The scan now also follows require.context and import.meta.glob calls whose arguments are written out. Warm webpack builds read the reports of modules restored from the persistent cache. Dev servers, watch builds, Turbopack and the Rsbuild and Bun plugins keep every marker.
  • Stylesheets without any rule are emitted empty instead of as a bare license banner, so the empty shared base sheet no longer repeats the banner in every per-file stylesheet that imports it. The banner names the version without a trailing comma (v1.0.83, not v1.0.83,). A new licenseBanner plugin option (default true) and the setLicenseBanner/isLicenseBanner engine functions turn the banner off; both engines emit identical output.
  • Webpack and Rsbuild builds hold every style in their stylesheets: a stylesheet module is built on its first import, so styles extracted later (the global styles of files webpack or Rsbuild reached late, often outside src) were missing from the output. The files the entries reach under src are 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 computeReachableFiles
  • Class names and file numbers no longer depend on the order files are processed in. Every plugin walks the files it can extract (the project's source and the included packages) before the first transform and numbers them in path order (a file collapsed into a bucket is numbered as the bucket, and only files that mention the package, StyleX or an aliased package take numbers) through the new seedFileMap, so identical builds give identical class prefixes, CSS file names and output hashes; in development, files that appear later are numbered after the existing ones. Styles are given class names in a fixed order, not the order of a hash set. The exported class, file and canonical maps are canonical JSON (sorted keys). Stylesheet evaluation (vanilla-extract) refuses Math.random(), Date.now(), new Date() and Date(), which differ between builds, with a build error; fixed dates such as new Date(0) are unchanged. resetBuildState starts a build from its own options: the prefix, atom hoisting, routes, buckets, names, numbers and styles an earlier build in the process left are cleared, and the prefix is set on every setup even when it is absent. Engine snapshots from concurrent transforms are written one after another per file, so an older snapshot is never written last. File lists are ordered by code point rather than the locale
  • A broken devup.json is reported instead of silently loading an empty theme. New errors: <file> is not valid JSON: <cause>, <file> must hold a JSON object, and devup.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.ts is 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
  • @emotion/css is aliased by default: css and keyframes compile like Devup UI's own (numbers in px, as Emotion reads them), injectGlobal declares global CSS. cx takes class names, as in Emotion: strings and runtime values are classes kept as written (falsy values are skipped), an object is a { name: condition } class map, arrays nest, and inline css() calls and css() classes compose with the rules css(a, b) uses. merge(className) splits what the build can read (string tokens, template literal parts) and composes the css() classes in it, keeping a runtime string it cannot split as it is. Namespace members, constant-string bracket access, const destructuring and const alias chains compile through these same named APIs with scope-aware binding resolution; numeric values retain Emotion units after constant inlining and build-time evaluation. The Emotion import disappears when no runtime-only member is used. Ambient declarations type the styling imports (cx(...args: ClassNamesArg[]), merge(className: string)). New located build errors: cx() cannot use a spread, a getter, a setter or a method in a class map, or a template literal call; merge() takes exactly one class string, not a spread or a template literal call; the root module has no default export, namespace member keys must be constant strings naming supported exports, and styling functions cannot be passed, mutated or re-exported. Optional styling reads/calls, namespace rest destructuring, styling defaults or nested patterns, non-const aliases, exported styling bindings and reads whose initialization order cannot be established are build errors instead of runtime dependencies. Styling loaded through require, import-equals or dynamic import must use static ES module imports; an unawaited dynamic namespace that the build cannot follow is also a located error. Its runtime-only APIs (cache, flush, hydrate, sheet, getRegisteredStyles) stay on @emotion/css, including their nested/default destructuring, optional reads and recognized runtime-loader access
  • A project whose tsconfig.json (or jsconfig.json) builds JSX with Emotion (compilerOptions.jsxImportSource of @emotion/react, through extends and project references too) now compiles the css prop on every element of every file, and its .tsx and .jsx files are built with React's JSX runtime through a /** @jsxImportSource react */ pragma, which a file's own JSX pragma overrides, so the bundler no longer imports Emotion's runtime. The plugins read the setting into a new @emotion/react/jsx-runtime alias (importAliases can turn it off with false, and it is left out when @emotion/react is not aliased); @devup-ui/react/compat/emotion-jsx-runtime declares Emotion's JSX runtimes as React's so the project type-checks without Emotion installed. plugin-utils exports readJsxImportSource, and mergeImportAliases takes the JSX import source
  • Declare the Node.js versions the build-time packages need (Node 22 for the Vite plugin, which calls Promise.withResolvers) and replace the unrestricted vite, next, @rsbuild/core and typescript-eslint peers with the oldest major each plugin is written against: Vite 5, Next.js 13, Rsbuild 1 and typescript-eslint 8.
  • include package names match only the whole package directory under the innermost node_modules: foo.bar no longer compiles fooXbar, pkg no longer compiles @scope/pkg or pkg-extra, names with regex characters such as foo+bar are compiled, and dependencies nested in an included package's own node_modules are no longer compiled with it. Vite and Rsbuild build the matcher once instead of on every transformed module. No new build errors
  • A devup.json extends entry 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.
  • Next apps with app/ or pages/ at the project root (no src/) are prewarmed and waited on like src/ 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 .next and .git
  • Count Pages Router modules and every App Router route file as Next route entries, so Pages Router projects get a deterministic CSS completion set
  • Reconstruct the complete deterministic Next webpack stylesheet after each server, edge and client compiler reset, including accepted external package dependency closures, so delivered CSS matches rendered classes in per-file and single-CSS modes. Keep production CSS request paths stable across build IDs so persistent webpack cache cannot bypass the CSS loader. Genuine production prewarm collection, read and extraction failures now fail the build instead of silently dropping styles; failed initialization releases its build session without leaking styles into unrelated builds.
  • Reserve existing short counter class, variable, keyframe and raw-file slots in physical input order before Bun, webpack, Rsbuild and Next webpack extraction. Watch revisions append sorted slots without renumbering. No new source build errors or styling runtime; unknown virtual, generated and opaque outside-inventory inputs retain observable residual allocation.
  • Compile .mts, .cts and .cjs modules in every plugin, Turbopack and the import graph, and resolve ./a.js, ./a.mjs and ./a.cjs imports to their TypeScript sources. Resolve package exports in the package's own order with the conditions of the bundler: Vite's resolve.conditions, the ESM conditions of webpack and Rspack per environment, and the target and conditions of Bun. Atom hoisting in webpack and Rsbuild plans over the src and app directories of the working directory and of the bundler root, not src alone. 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 .js and .cjs modules. No new build errors.
  • Resolve relative plugin options (devupFile, distDir, cssDir), the tsconfig and the webpack extraction ids against the bundler's project root (Vite root, webpack context, Rsbuild rootPath, Next's project directory for webpack builds, Bun.build root) instead of process.cwd(), so builds started from a parent directory as turbo or nx do read the project's devup.json and write its df. Builds started from the project root are unchanged. When devupFile is not set and only the working directory holds a devup.json, that file is still read and a one-time warning says to move it next to the project or set devupFile. Class names may change once for webpack and Next webpack builds run from a parent directory, because files are now numbered relative to the project root.
  • Add the types-only @devup-ui/plugin-utils/types entry (resolved through exports, and typesVersions for node10 resolution) holding the types the plugins' published declarations name. The Next plugin's declarations now import it instead of the whole package, so a next.config.ts type check loads 7 of plugin-utils' declaration files instead of 22 (.next/cache/.tsbuildinfo about 3.5 KB smaller on the benchmark apps).
  • Skip @devup-ui/react in 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.css and a- instead of devup-ui-23.css and x-); the styles are unchanged.
  • Resolve every working-directory-relative path in the project-root helpers through process.cwd() read at call time. Behavior is unchanged; tests now stub the working directory instead of changing the shared test process's directory.
  • Add an internal aggregate compiler-state reset for isolated tests, scoped native cleanup and Next test-cache isolation; verify real Bun registration callbacks and packed production consumers across bundlers and browsers. No new application build errors are introduced.
  • Stop the shared class-slot reservation at a dependency's files that the loaders leave to the bundler, instead of reading everything they import. Next's webpack client entries no longer make every production build read and scan about 300 of Next's own runtime files before compiling; the reserved classes and the emitted CSS and JavaScript are unchanged.
  • Remember package resolutions and module code in the module resolver, so a module imported by many files is read once until it changes
  • Read each source file once per build in the passes that run before the bundler. The import graph, the class-slot reservation and the prewarm read the same files, and a Next production build runs them once per compiler (server, edge, client): they now share a stamp-checked source cache (withSourceCache / readSource in 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.
  • Custom shorthand targets are constrained to supported camelCase/kebab-case CSS properties, built-in aliases and valid custom properties. All five build adapters normalize options at creation before registration or extraction, including Next.js production cache reuse. Unsupported targets fail registration atomically with the original shorthand name, target and zero-based index; previously registered shorthands remain unchanged. New devup-ui option errors expose structured logical shorthands paths without inventing source coordinates. Eighteen dead unprefixed property names are rejected.
  • Every plugin takes stylex: { styleResolution }, StyleX's babel plugin option of the same name, and the engines take it through the new setStylexStyleResolution(). 'property-specificity' stays the default. 'application-order' gives a static stylex.create() key the null resets StyleX's table lists for the longhands it covers (and reads its aliases, marginStart as margin-inline-start), so the key applied last wins in stylex.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' into padding-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 given firstThatWorks() fallbacks, all under application-order and a listStyle StyleX cannot sort under legacy-expand-shorthands; an unknown styleResolution is a configuration error (StylexConfigError). Devup UI's own APIs ignore the option
  • Tailwind classes in a className read the Tailwind CSS of the project: the file that imports tailwindcss (the tailwind.css option of devup.json, else a conventional path) gives @theme variables (colors, spacing, shadows, blurs, radii, easings, animations with their @Keyframes, default transitions, breakpoints), @Utility utilities and @custom-variant variants, and the Vite, webpack and Next.js plugins read it again when it or a CSS file it imports changes. Anything that cannot be read exactly, and the classes of namespaces the build does not read, stay as written. More of Tailwind CSS v4 compiles: ring-, inset-ring-, ring-offset-* and drop-shadow-* compose with shadows and filters, borders and outlines draw in --tw-border-style and --tw-outline-style (a border now shows its style), line-clamp, text decoration, border-spacing, logical and scroll spacing, tables, perspective, font-stretch and more; the arguments of clsx(), classnames() and classNames() and [...].join(' ') compile in place. Radii follow v4 (rounded-sm is 0.25rem, rounded-full is calc(infinity * 1px)). No new build errors
  • tsconfig paths and baseUrl are read through extends the way TypeScript reads them: relative and package configs (a package's tsconfig field or tsconfig.json), lists of configs where a later one wins, and cycles stop. baseUrl is relative to the config that declares it, and paths without baseUrl to the config that declares paths. Imports through such aliases now resolve for build-time constants, atom hoisting and single-importer collapse
  • Types now accept what the build compiles and nothing it rejects. css() takes classes, style objects, arrays and falsy parts, and the css/keyframes/globalCss tags take the static interpolations the build evaluates. styled gets .attrs(), .withConfig() and .withComponent(), and its result renders another tag. styleVars takes numbers; styleOrder is 1 to 254; ResponsiveValue is exported for hand-written custom shorthands. The compat declarations name what Emotion, styled-components and vanilla-extract give (SerializedStyles, Keyframes, RuleSet, an augmentable Theme and DefaultTheme, CSSObject and the other styled-components types) and follow the vanilla-extract APIs the evaluator registers (style arrays, the styleVariants mapper, createGlobalTheme, createGlobalThemeContract; globalKeyframes, composeStyles and generateIdentifier are gone). DevupTheme takes shadow as devup.json documents it. No new build errors.
  • @vanilla-extract/css-utils is aliased by default and its calc compiles to the strings the package builds (calc.add/subtract/multiply/divide/negate, chained calc(x) with .toString() or template interpolation, nested operations only parenthesized). A .css.ts stylesheet 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-level consts holding a literal or other calc results. @devup-ui/react/compat/vanilla-extract-css-utils types it, and css-utils-literal-only reads its calls as the build does. New build errors: a calc operand outside a stylesheet the build cannot read, a calc read without being called, a calc(x) used as a value without .toString() (also in a stylesheet), an export other than calc, and a namespace import, require() or re-export of the package outside a stylesheet. Set importAliases: { '@vanilla-extract/css-utils': false } to keep the package
  • Reserve short shared class and CSS-variable slots before Vite extraction across build, serve, and shared environments. Enable atom hoisting by default at two distinct physical module boundaries plus reachable dynamic targets, with zero opting out and singleCss unchanged. Install the closed-inventory canonical and reach plan before scratch and freeze it for the build lifetime, including watch updates. Discover static physical HTML inputs with a Vite-only build-time parse5 parser, keeping it outside non-Vite plugin and loader graphs, and refresh only dirty revisions without styling runtime or new intended source build-error categories.
  • Add shared native/WASM compiler selection, structural compiler types and exact native platform-load diagnostics for build plugins.
  • Plan single-importer collapse and atom hoisting in webpack and Rsbuild, as in Vite, over the graph of the files the shared-slot reservation discovers: the src and app directories, the closures of the bundler's real entries and the included packages, with the entries as routes. The graph is built once per build and reused by the stylesheet warm-up instead of scanning the source tree two more times; the warm-up skips the package files the transform skips. Report a failed Rsbuild warm-up with a warning instead of ignoring it. Add reservationRoutes to plugin-utils.

@devup-ui/react@1.0.44 → 1.0.45 - packages/react/package.json

Patch

  • The @devup-ui/react README and the css-utils-literal-only rule docs link their mention of build errors to the new Build Errors reference (https://devup-ui.com/docs/build-errors), which lists the build errors grouped by API; the docs sidebar lists the page after Supported Syntax & Limitations, whose Build errors section links to it. Documentation only: no new build errors
  • The styled-components and Emotion compat ThemeProvider now gives its theme through React context: useTheme, withTheme and the new ThemeConsumer return the real theme object (an object merged over the outer theme, or what a theme function makes of it) instead of an empty Proxy of var() references, withTheme forwards refs, lets a caller's theme win and sets a displayName. Styles keep reading the CSS variables the provider declares. styled-components v6.4 createTheme is available from the compat entry, and ThemeConsumer and createTheme imports are redirected there instead of staying a runtime dependency on styled-components
  • The outermost compat ThemeProvider also declares its theme's CSS variables on :root, in a <style> element rendered with the markup, so createGlobalStyle and rules on html, body or :root read the theme. Nested providers still scope only their subtree.
  • The compat ThemeProvider renders no wrapper element without a theme, and with one declares only the CSS variables its theme changes from the outer provider's. withTheme hoists the component's non-React statics, and ServerStyleSheet has an empty instance (with clearTag()) for SSR setups that pass it to StyleSheetManager. New runtime errors thrown by ThemeProvider: 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 forever
  • Reject the 18 unprefixed legacy flexbox and scroll-snap properties rejected by the compiler in component and StyleX property types. Keep vendor-prefixed compatibility properties, stroke-color and ime-mode.
  • Emotion's now compiles at build time with no runtime: the element becomes what its child function ({ css, cx, theme }) => ... renders, each css and cx call becomes the classes it composes (later styles replace earlier ones; css reads strings as CSS text and its tagged templates split around mixins; cx keeps unknown classes, reads { name: condition } objects as conditional classes and composes nested css and cx calls), and theme.a.b in their values becomes var(--a-b). Numbers in css rules are px lengths, as Emotion reads them, and top-level constants are inlined. New build errors, each at file:line:col: a without exactly one child function taking { css, cx, theme } that gives what it renders at once (attributes, other children, rest or default parameters, async or generator functions, several statements); reading the theme other than as theme.a.b in a css value; using css or cx other than by calling them; a cx object with a spread, getter or method; parts css and cx cannot compose (runtime calls, spreads, a condition choosing between styles and classes). @devup-ui/react/compat exports ClassNames with the ClassNamesContent and ClassNamesArg types, and the @emotion/react declarations include them
  • @emotion/css is aliased by default: css and keyframes compile like Devup UI's own (numbers in px, as Emotion reads them), injectGlobal declares global CSS. cx takes class names, as in Emotion: strings and runtime values are classes kept as written (falsy values are skipped), an object is a { name: condition } class map, arrays nest, and inline css() calls and css() classes compose with the rules css(a, b) uses. merge(className) splits what the build can read (string tokens, template literal parts) and composes the css() classes in it, keeping a runtime string it cannot split as it is. Namespace members, constant-string bracket access, const destructuring and const alias chains compile through these same named APIs with scope-aware binding resolution; numeric values retain Emotion units after constant inlining and build-time evaluation. The Emotion import disappears when no runtime-only member is used. Ambient declarations type the styling imports (cx(...args: ClassNamesArg[]), merge(className: string)). New located build errors: cx() cannot use a spread, a getter, a setter or a method in a class map, or a template literal call; merge() takes exactly one class string, not a spread or a template literal call; the root module has no default export, namespace member keys must be constant strings naming supported exports, and styling functions cannot be passed, mutated or re-exported. Optional styling reads/calls, namespace rest destructuring, styling defaults or nested patterns, non-const aliases, exported styling bindings and reads whose initialization order cannot be established are build errors instead of runtime dependencies. Styling loaded through require, import-equals or dynamic import must use static ES module imports; an unawaited dynamic namespace that the build cannot follow is also a located error. Its runtime-only APIs (cache, flush, hydrate, sheet, getRegisteredStyles) stay on @emotion/css, including their nested/default destructuring, optional reads and recognized runtime-loader access
  • Emotion's css prop compiles at build time while @emotion/react is aliased: on tags and Devup UI components always, and on every element once the file imports @emotion/react or @emotion/styled or names @emotion/react in a @jsxImportSource pragma; jsx, jsxs and jsxDEV from @emotion/react/jsx-runtime (or jsx-dev-runtime) and jsx from @emotion/react compile it too, so libraries built with Emotion's JSX runtime do as well. The prop becomes the element's className, with CSS variables in its style for values only the runtime gives: arrays and conditions compose with a later part replacing what an earlier one sets, css() classes the file knows compose by their styles, strings and templates are CSS text, css`` mixins split the text around them, a function of the theme reads theme.a.b as var(--a-b), unitless numbers are px as in Emotion (constants included), and a className holding known css() classes overrides the prop as Emotion's registered classes do. A styled component the file defines renders its tag in the element's place when the prop overrides its styles and it renders a tag with no attrs or props read and the element has no spread, as or forwardedAs. Emotion's JSX runtime imports become react/jsx-runtime, the pragma names react, and jsx comes from @devup-ui/react/compat (React's createElement); @devup-ui/react/compat/css-prop types the prop on React.Attributes. New build errors, each with file:line:column and the code: a css prop part the build cannot read (a call, an element), a style object declared inside a function or with let, a binding only running the module gives or code changes, a theme function that does more than return rules or reads the theme other than as theme.a.b in a value, an interpolation CSS text cannot place or a mixin inside a nested rule, and a css prop overriding a styled component's styles where its tag cannot be rendered in place. Composing css() with a part that reads a known binding (such as a keyframes name) now reads its value
  • Recognize Emotion jsxImportSource eligibility with the same exact header rules used for rewriting, preserve authored first-use cascade-layer order while composing css props, retain exact computed theme keys, and keep Emotion numeric-length pixel semantics when constant rule arrays are inlined. Unitless values and zero retain their existing behavior. Every valid css-prop form remains supported; invalid empty JSX css expressions retain main's located syntax error. No new build-error category is introduced.
  • Emotion's CacheProvider is available from the compat entry as a no-op that renders its children, and import { 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
  • A project whose tsconfig.json (or jsconfig.json) builds JSX with Emotion (compilerOptions.jsxImportSource of @emotion/react, through extends and project references too) now compiles the css prop on every element of every file, and its .tsx and .jsx files are built with React's JSX runtime through a /** @jsxImportSource react */ pragma, which a file's own JSX pragma overrides, so the bundler no longer imports Emotion's runtime. The plugins read the setting into a new @emotion/react/jsx-runtime alias (importAliases can turn it off with false, and it is left out when @emotion/react is not aliased); @devup-ui/react/compat/emotion-jsx-runtime declares Emotion's JSX runtimes as React's so the project type-checks without Emotion installed. plugin-utils exports readJsxImportSource, and mergeImportAliases takes the JSX import source
  • vanilla-extract's globalKeyframes(name, frames) now compiles in .css.ts/.css.js stylesheets, declaring @Keyframes under the name as written, instead of being a build error. globalCss() takes a '@Keyframes name' key the same way ('@Keyframes fade': { from: {...}, to: {...} }), which before wrote invalid CSS such as '@Keyframes fade from{...}'; keyframes declared by name go to the shared stylesheet. @devup-ui/react/compat declares globalKeyframes for @vanilla-extract/css. New build error at file:line:col: a '@Keyframes' key in globalCss() whose name is not letters, digits, '-' and '_' (or starts with a digit), or that sits inside an at-rule.
  • The README no longer claims every CSS-in-JS pattern compiles: it describes what the build compiles and that anything it cannot know is a CSS variable or a located build error, and links the new Supported Syntax & Limitations page, which lists what compiles, the style override rules (where a later part wins and where the CSS cascade decides), Baseline 2024 browser support, that a component taking the css prop must pass className and style on, the runtime-only APIs and how each is handled, and the known limitations
  • CSS blocks no longer end with a redundant ; before }: StyleX defineVars(), createTheme(), typed-variable @property, positionTry() and viewTransitionClass() rules, and the variables the runtime createTheme() GlobalStyle declares, now separate declarations with ; only between them, as the rest of the generated CSS already does. The CSS is equivalent and slightly smaller.
  • Package READMEs are refreshed: the benchmark tables show the current CI run and are regenerated with the root README from benchmark-results.json, the examples show the current generated class names instead of fixed d0/d1 names, and the Korean README link points to the repository; @devup-ui/components and @devup-ui/reset-css name their own package and install line and add a short usage section; the ESLint README notes that preset rules can report the same code. Documentation only
  • @devup-ui/react and @devup-ui/components take React as a peer of ^18 || ^19 instead of * 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
  • Publish @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 for moduleResolution: node16/nodenext projects: they used to resolve the package's types to any (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. With bundler and node10 resolution the exported names and types and theme augmentation are unchanged.
  • Refresh dependencies, including Oxc 0.156, wasm-bindgen 0.2.130, parse5 8.1 and Rsbuild 2.3. Preserve the React 18 compatibility fixture while updating its build tooling.
  • Every component compiled from styled carries a styledComponentId property, set once per file by a small helper, and the compat isStyledComponent returns true for it as styled-components does instead of always returning false
  • StyleX APIs compile as StyleX defines them: a dynamic style may set its parameters under conditions ((size) => ({ width: { default: 100, ':hover': size } })), each condition taking its own variable; a computed condition key may read a defineConsts() constant ([constants.wide]); a types.*() variable in defineVars() registers @property with its default as the initial value; a '--global' key keeps its name and colors['--global'] reads it; positionTry() and viewTransitionClass() bindings read as their names in create(), 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 becoming var(--name); viewTransitionClass() takes the group, imagePair, old and new groups and styles their pseudo-elements. New build errors: a types.*() variable without a default, types.integer() given a fraction, an unknown types.* helper, and a viewTransitionClass() key other than group, imagePair, old and new or a group that is not an object of declarations
  • stylex.attrs() gives the dynamic CSS variables it sets as style attribute 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 declares style as a string
  • Type every compiled StyleX API with opaque styles, dynamic function arguments, conditional variables, partial themes and static null/string theme contract placeholders. Unsupported runtime shapes are rejected by TypeScript; no new build errors in this change.
  • Compile StyleX when.ancestor(), when.descendant(), when.anySibling(), when.siblingBefore(), when.siblingAfter(), defineMarker() and defaultMarker() at build time, as @stylexjs/babel-plugin does, instead of reporting them as unsupported: a when.*() 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 class x-default-marker, and defineMarker() names a class after its file and export that importing modules read too. @devup-ui/react types when, defineMarker, defaultMarker and markers in props(). Pseudo-classes nested in each other are now written in the order StyleX sorts them, so :hover inside :focus reads :focus:hover. New build errors: a when.*() 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; a defineMarker() call with arguments or not bound to a named export of the module's top level; a defaultMarker() call with arguments
  • Styled components now remove every runtime prop whose name starts with $ 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
  • Types now accept what the build compiles and nothing it rejects. css() takes classes, style objects, arrays and falsy parts, and the css/keyframes/globalCss tags take the static interpolations the build evaluates. styled gets .attrs(), .withConfig() and .withComponent(), and its result renders another tag. styleVars takes numbers; styleOrder is 1 to 254; ResponsiveValue is exported for hand-written custom shorthands. The compat declarations name what Emotion, styled-components and vanilla-extract give (SerializedStyles, Keyframes, RuleSet, an augmentable Theme and DefaultTheme, CSSObject and the other styled-components types) and follow the vanilla-extract APIs the evaluator registers (style arrays, the styleVariants mapper, createGlobalTheme, createGlobalThemeContract; globalKeyframes, composeStyles and generateIdentifier are gone). DevupTheme takes shadow as devup.json documents it. No new build errors.
  • Components behave for keyboard, screen readers and both React 18 and 19: Button, Input and Textarea no longer force generic aria-labels (the visible text or an associated label names them), Input and Textarea mark errors with aria-invalid and aria-describedby pointing at the message, a loading Button sets aria-busy, is disabled by default (disableWhileLoading) and announces loadingLabel, Input clear dispatches a real change event instead of a fabricated one, color customization variables sit on the container so every part sees them and every public color key matches its CSS custom property (new keys inputDisabledBackground, inputDisabledText, inputPlaceholder, primaryBackground, Textarea disabledBackground and disabledText), Select positions against the viewport and clears the opposite inset, SelectTrigger asChild composes the child onClick, onKeyDown and ref with its own, Stepper counts without a controlled value, keeps its bound and disabled safeguards and renders its text mode as an output element. Select no longer forces aria-labels over its trigger, options, confirm button and container: an option is named by its content, the listbox by its trigger (aria-labelledby) or by what the caller passes. ThemeScript takes nonce and other script props and never aborts on blocked storage or missing matchMedia, follows the system while no theme was chosen and themes saved in other tabs; getTheme, setTheme and initTheme are safe on the server and initTheme returns a function that stops following. reset-css clips accessible-hidden content as sanitize.css does. No new build errors.
  • Refresh all dependency ranges and regenerated lockfiles with the latest dependency-check-updates CLI, including Oxc 0.154, sourcemap 9, Next, React, Panda, Playwright, ESLint, Vinext and WASM dependencies. Preserve the existing hybrid CommonJS bundler language through exact top-level declaration-goal classification without changing parser AST, diagnostics or source-type metadata; real invalid syntax, including nested ES declarations, still produces located parser errors. Keep React 18 and 19 peer support and the React 18 fixture pins. No new build errors for valid supported styling inputs or styling runtime.
  • Update dependencies to their latest releases and migrate Oxc while preserving exact JavaScript string identity, static CSS output, and React 18/19 compatibility. Final CSS text, values, keys, and required evaluation-module specifiers containing unpaired UTF-16 surrogates now fail at build time with source locations instead of becoming lossy text or dynamic styling.
  • @vanilla-extract/css-utils is aliased by default and its calc compiles to the strings the package builds (calc.add/subtract/multiply/divide/negate, chained calc(x) with .toString() or template interpolation, nested operations only parenthesized). A .css.ts stylesheet 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-level consts holding a literal or other calc results. @devup-ui/react/compat/vanilla-extract-css-utils types it, and css-utils-literal-only reads its calls as the build does. New build errors: a calc operand outside a stylesheet the build cannot read, a calc read without being called, a calc(x) used as a value without .toString() (also in a stylesheet), an export other than calc, and a namespace import, require() or re-export of the package outside a stylesheet. Set importAliases: { '@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

  • Keep unknown element-prop spreads wholly as native pass-through data: their keys never select, replace or remove separately authored styles, regardless of order. Preserve fully known ordinary spread composition, canonical aliases, source-ordered once-only values and native className/style merging without spread-key styling variables, fallbacks or conversion code. Preserve exact imported enum and Math values including negative zero, lexical constants, binding-aware CommonJS require, React createElement calls, type-only imports, and compiled reset CSS tests. Retain located errors for intrinsically unreadable explicit styles, runtime styleOrder, unmovable lazy logical suspension, whole Devup UI namespaces escaping to runtime, and immediate lexical temporal-dead-zone reads. Native Emotion css spread restrictions and separate styled css overlap restrictions remain unchanged. Inline eager styled render stages, attrs merges and destructuring carriers into their existing render scope, and reuse scoped captures for CSS composition and StyleX units. Preserve per-instance dynamic component targets, parameter environments, getter and iterator effects, function names and call receivers while removing unnecessary generated arrow functions.
  • Package READMEs are refreshed: the benchmark tables show the current CI run and are regenerated with the root README from benchmark-results.json, the examples show the current generated class names instead of fixed d0/d1 names, and the Korean README link points to the repository; @devup-ui/components and @devup-ui/reset-css name their own package and install line and add a short usage section; the ESLint README notes that preset rules can report the same code. Documentation only
  • Components behave for keyboard, screen readers and both React 18 and 19: Button, Input and Textarea no longer force generic aria-labels (the visible text or an associated label names them), Input and Textarea mark errors with aria-invalid and aria-describedby pointing at the message, a loading Button sets aria-busy, is disabled by default (disableWhileLoading) and announces loadingLabel, Input clear dispatches a real change event instead of a fabricated one, color customization variables sit on the container so every part sees them and every public color key matches its CSS custom property (new keys inputDisabledBackground, inputDisabledText, inputPlaceholder, primaryBackground, Textarea disabledBackground and disabledText), Select positions against the viewport and clears the opposite inset, SelectTrigger asChild composes the child onClick, onKeyDown and ref with its own, Stepper counts without a controlled value, keeps its bound and disabled safeguards and renders its text mode as an output element. Select no longer forces aria-labels over its trigger, options, confirm button and container: an option is named by its content, the listbox by its trigger (aria-labelledby) or by what the caller passes. ThemeScript takes nonce and other script props and never aborts on blocked storage or missing matchMedia, follows the system while no theme was chosen and themes saved in other tabs; getTheme, setTheme and initTheme are safe on the server and initTheme returns a function that stops following. reset-css clips accessible-hidden content as sanitize.css does. No new build errors.

@devup-ui/rsbuild-plugin@1.0.67 → 1.1.0 - packages/rsbuild-plugin/package.json

Minor

  • Require Node.js 20 or later for the build-time packages: Node 18 is past its end of life and does not expose the globalThis.crypto the WASM engine reads. The plugins, plugin-utils, the WASM engine and the native bindings now declare engines.node >=20 (the ESLint plugin ^20.9.0 || >=21.1.0, as typescript-eslint 8 requires; the Vite plugin keeps >=22).

Patch

  • Enable atomHoist by default at two boundaries in Vite, Webpack, Rsbuild and Next Webpack, with numeric zero opting out and no effect in singleCss mode. Keep Next Turbopack in per-file mode until its shared-slot reservation lands, warning once for explicit positive atomHoist requests. Allocate shared and file-local short counter names through deterministic reserved slots instead of content names; preserve frozen route plans, dynamic !important, local keyframes, first-value responsive tokens, shared CSS updates and persisted placement. Bump the naming cache generation. Stabilize Vite dev-sheet module identity with independent content-write revisions, preserving cache busting for changed CSS text and unchanged build paths. Track inherited configuration inputs, serialize refreshes and drain owned engine work before releasing shared build ownership. Reuse exact-input semantic extraction only in eligible exclusive serve sessions, registering dependencies on every request without retaining CSS snapshots or replaying writes; builds continue extracting normally. No new build errors.
  • When an optional setup step fails and the build goes on without it (Vite, webpack and Bun file numbering, the webpack and Rsbuild import graphs, the webpack stylesheet warm-up), print one warning naming the step, the cause and what the build loses instead of continuing silently. A project without a src directory stays quiet. No new build errors.
  • webpack (and Next.js on webpack) and Rsbuild watch every config devup.json extends, as Vite does, and reload the theme when one is edited, added or deleted. Rsbuild did not reload devup.json itself in dev before; webpack only watched a devup.json that existed when the build started
  • Stylesheets without any rule are emitted empty instead of as a bare license banner, so the empty shared base sheet no longer repeats the banner in every per-file stylesheet that imports it. The banner names the version without a trailing comma (v1.0.83, not v1.0.83,). A new licenseBanner plugin option (default true) and the setLicenseBanner/isLicenseBanner engine functions turn the banner off; both engines emit identical output.
  • Webpack and Rsbuild builds hold every style in their stylesheets: a stylesheet module is built on its first import, so styles extracted later (the global styles of files webpack or Rsbuild reached late, often outside src) were missing from the output. The files the entries reach under src are 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 computeReachableFiles
  • Class names and file numbers no longer depend on the order files are processed in. Every plugin walks the files it can extract (the project's source and the included packages) before the first transform and numbers them in path order (a file collapsed into a bucket is numbered as the bucket, and only files that mention the package, StyleX or an aliased package take numbers) through the new seedFileMap, so identical builds give identical class prefixes, CSS file names and output hashes; in development, files that appear later are numbered after the existing ones. Styles are given class names in a fixed order, not the order of a hash set. The exported class, file and canonical maps are canonical JSON (sorted keys). Stylesheet evaluation (vanilla-extract) refuses Math.random(), Date.now(), new Date() and Date(), which differ between builds, with a build error; fixed dates such as new Date(0) are unchanged. resetBuildState starts a build from its own options: the prefix, atom hoisting, routes, buckets, names, numbers and styles an earlier build in the process left are cleared, and the prefix is set on every setup even when it is absent. Engine snapshots from concurrent transforms are written one after another per file, so an older snapshot is never written last. File lists are ordered by code point rather than the locale
  • A broken devup.json is reported instead of silently loading an empty theme. New errors: <file> is not valid JSON: <cause>, <file> must hold a JSON object, and devup.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.ts is 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
  • A project whose tsconfig.json (or jsconfig.json) builds JSX with Emotion (compilerOptions.jsxImportSource of @emotion/react, through extends and project references too) now compiles the css prop on every element of every file, and its .tsx and .jsx files are built with React's JSX runtime through a /** @jsxImportSource react */ pragma, which a file's own JSX pragma overrides, so the bundler no longer imports Emotion's runtime. The plugins read the setting into a new @emotion/react/jsx-runtime alias (importAliases can turn it off with false, and it is left out when @emotion/react is not aliased); @devup-ui/react/compat/emotion-jsx-runtime declares Emotion's JSX runtimes as React's so the project type-checks without Emotion installed. plugin-utils exports readJsxImportSource, and mergeImportAliases takes the JSX import source
  • Declare the Node.js versions the build-time packages need (Node 22 for the Vite plugin, which calls Promise.withResolvers) and replace the unrestricted vite, next, @rsbuild/core and typescript-eslint peers with the oldest major each plugin is written against: Vite 5, Next.js 13, Rsbuild 1 and typescript-eslint 8.
  • include package names match only the whole package directory under the innermost node_modules: foo.bar no longer compiles fooXbar, pkg no longer compiles @scope/pkg or pkg-extra, names with regex characters such as foo+bar are compiled, and dependencies nested in an included package's own node_modules are no longer compiled with it. Vite and Rsbuild build the matcher once instead of on every transformed module. No new build errors
  • Document library mode in the Vite, Webpack and Rsbuild plugin READMEs: a library built with extractCss: false is published uncompiled, and every application that uses it must list the package in include.
  • MDX documents are extracted after the MDX plugin compiles them: the engine reads an .mdx filename as the JavaScript module (with or without JSX) an MDX compiler makes of it instead of rejecting the extension, the Vite plugin extracts .mdx in a post transform, and the webpack and Rsbuild plugins in a post loader; Next.js with Turbopack and the Bun plugin still leave MDX untransformed
  • A devup.json extends entry 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.
  • Reserve existing short counter class, variable, keyframe and raw-file slots in physical input order before Bun, webpack, Rsbuild and Next webpack extraction. Watch revisions append sorted slots without renumbering. No new source build errors or styling runtime; unknown virtual, generated and opaque outside-inventory inputs retain observable residual allocation.
  • Package READMEs are refreshed: the benchmark tables show the current CI run and are regenerated with the root README from benchmark-results.json, the examples show the current generated class names instead of fixed d0/d1 names, and the Korean README link points to the repository; @devup-ui/components and @devup-ui/reset-css name their own package and install line and add a short usage section; the ESLint README notes that preset rules can report the same code. Documentation only
  • Compile .mts, .cts and .cjs modules in every plugin, Turbopack and the import graph, and resolve ./a.js, ./a.mjs and ./a.cjs imports to their TypeScript sources. Resolve package exports in the package's own order with the conditions of the bundler: Vite's resolve.conditions, the ESM conditions of webpack and Rspack per environment, and the target and conditions of Bun. Atom hoisting in webpack and Rsbuild plans over the src and app directories of the working directory and of the bundler root, not src alone. 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 .js and .cjs modules. No new build errors.
  • Resolve relative plugin options (devupFile, distDir, cssDir), the tsconfig and the webpack extraction ids against the bundler's project root (Vite root, webpack context, Rsbuild rootPath, Next's project directory for webpack builds, Bun.build root) instead of process.cwd(), so builds started from a parent directory as turbo or nx do read the project's devup.json and write its df. Builds started from the project root are unchanged. When devupFile is not set and only the working directory holds a devup.json, that file is still read and a one-time warning says to move it next to the project or set devupFile. Class names may change once for webpack and Next webpack builds run from a parent directory, because files are now numbered relative to the project root.
  • Resolve the imports the extractor follows against the bundler's project root (webpack's context, the Rsbuild root, the root of Bun.build) instead of the working directory, so a build started from a parent directory, as monorepo tools do, reads that project's tsconfig.json paths and resolves the relative imports of its root-relative webpack ids under the project.
  • Refresh dependencies, including Oxc 0.156, wasm-bindgen 0.2.130, parse5 8.1 and Rsbuild 2.3. Preserve the React 18 compatibility fixture while updating its build tooling.
  • A source file deleted or renamed in watch mode or the dev server no longer leaves its styles behind: its globalCss, its own stylesheet and the class names handed out in it are dropped, and it leaves the bucket it collapsed into. The engine gains removeFile(filename) (native and WASM), which Vite calls on a delete watch 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
  • With atomHoist on, the shared devup-ui.css cacheGroup is now also added when the rspack config has no optimization.splitChunks yet, so hoisted atoms load once across entries instead of being inlined per entry. splitChunks: false is still left as it is.
  • Custom shorthand targets are constrained to supported camelCase/kebab-case CSS properties, built-in aliases and valid custom properties. All five build adapters normalize options at creation before registration or extraction, including Next.js production cache reuse. Unsupported targets fail registration atomically with the original shorthand name, target and zero-based index; previously registered shorthands remain unchanged. New devup-ui option errors expose structured logical shorthands paths without inventing source coordinates. Eighteen dead unprefixed property names are rejected.
  • Every plugin takes stylex: { styleResolution }, StyleX's babel plugin option of the same name, and the engines take it through the new setStylexStyleResolution(). 'property-specificity' stays the default. 'application-order' gives a static stylex.create() key the null resets StyleX's table lists for the longhands it covers (and reads its aliases, marginStart as margin-inline-start), so the key applied last wins in stylex.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' into padding-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 given firstThatWorks() fallbacks, all under application-order and a listStyle StyleX cannot sort under legacy-expand-shorthands; an unknown styleResolution is a configuration error (StylexConfigError). Devup UI's own APIs ignore the option
  • More of Tailwind CSS v4 compiles: container queries (@sm:, @max-md:, @min-[400px]:, @sm/main:) and @container utilities, mask-* (all but the gradient masks), text-shadow-, inset-shadow-, font-variant-numeric utilities (tabular-nums and the like), 3D transforms (rotate-x/y/z, translate-z, scale-z, translate-3d, scale-3d, transform-3d, backface-, perspective-, perspective-origin-), contain- and outline-hidden (with its forced-colors fallback). The project's Tailwind CSS is read further: functional @Utility with --value() and --modifier(), @apply in @Utility, and theme(--name) in arbitrary values; classes of @plugin entries stay as written. A className now compiles the classes of cn()/twMerge() calls whose arguments are all static (merged as tailwind-merge does, the later class wins), of consts bound to class strings, and of cva() calls (base, variants, compound variants). The Rsbuild plugin reads the Tailwind CSS again and compiles every module again when it changes, and the Bun plugin reads it again. No new build errors
  • Tailwind classes in a className read the Tailwind CSS of the project: the file that imports tailwindcss (the tailwind.css option of devup.json, else a conventional path) gives @theme variables (colors, spacing, shadows, blurs, radii, easings, animations with their @Keyframes, default transitions, breakpoints), @Utility utilities and @custom-variant variants, and the Vite, webpack and Next.js plugins read it again when it or a CSS file it imports changes. Anything that cannot be read exactly, and the classes of namespaces the build does not read, stay as written. More of Tailwind CSS v4 compiles: ring-, inset-ring-, ring-offset-* and drop-shadow-* compose with shadows and filters, borders and outlines draw in --tw-border-style and --tw-outline-style (a border now shows its style), line-clamp, text decoration, border-spacing, logical and scroll spacing, tables, perspective, font-stretch and more; the arguments of clsx(), classnames() and classNames() and [...].join(' ') compile in place. Radii follow v4 (rounded-sm is 0.25rem, rounded-full is calc(infinity * 1px)). No new build errors
  • A theme that cannot be loaded or registered (a broken devup.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
  • Refresh all dependency ranges and regenerated lockfiles with the latest dependency-check-updates CLI, including Oxc 0.154, sourcemap 9, Next, React, Panda, Playwright, ESLint, Vinext and WASM dependencies. Preserve the existing hybrid CommonJS bundler language through exact top-level declaration-goal classification without changing parser AST, diagnostics or source-type metadata; real invalid syntax, including nested ES declarations, still produces located parser errors. Keep React 18 and 19 peer support and the React 18 fixture pins. No new build errors for valid supported styling inputs or styling runtime.
  • Update dependencies to their latest releases and migrate Oxc while preserving exact JavaScript string identity, static CSS output, and React 18/19 compatibility. Final CSS text, values, keys, and required evaluation-module specifiers containing unpaired UTF-16 surrogates now fail at build time with source locations instead of becoming lossy text or dynamic styling.
  • Add shared native/WASM compiler selection, structural compiler types and exact native platform-load diagnostics for build plugins.
  • Plan single-importer collapse and atom hoisting in webpack and Rsbuild, as in Vite, over the graph of the files the shared-slot reservation discovers: the src and app directories, the closures of the bundler's real entries and the included packages, with the entries as routes. The graph is built once per build and reused by the stylesheet warm-up instead of scanning the source tree two more times; the warm-up skips the package files the transform skips. Report a failed Rsbuild warm-up with a warning instead of ignoring it. Add reservationRoutes to plugin-utils.

@devup-ui/vite-plugin@1.0.73 → 1.0.74 - packages/vite-plugin/package.json

Patch

  • Enable atomHoist by default at two boundaries in Vite, Webpack, Rsbuild and Next Webpack, with numeric zero opting out and no effect in singleCss mode. Keep Next Turbopack in per-file mode until its shared-slot reservation lands, warning once for explicit positive atomHoist requests. Allocate shared and file-local short counter names through deterministic reserved slots instead of content names; preserve frozen route plans, dynamic !important, local keyframes, first-value responsive tokens, shared CSS updates and persisted placement. Bump the naming cache generation. Stabilize Vite dev-sheet module identity with independent content-write revisions, preserving cache busting for changed CSS text and unchanged build paths. Track inherited configuration inputs, serialize refreshes and drain owned engine work before releasing shared build ownership. Reuse exact-input semantic extraction only in eligible exclusive serve sessions, registering dependencies on every request without retaining CSS snapshots or replaying writes; builds continue extracting normally. No new build errors.
  • When an optional setup step fails and the build goes on without it (Vite, webpack and Bun file numbering, the webpack and Rsbuild import graphs, the webpack stylesheet warm-up), print one warning naming the step, the cause and what the build loses instead of continuing silently. A project without a src directory stays quiet. No new build errors.
  • One-shot production builds with the Vite and webpack plugins (Next.js without Turbopack included) drop the component-selector markers no module selects. Each transform and the start-of-build scan report the markers they give and select; once every module is compiled, a marker no module selects or writes leaves the output chunks. When a module selects a component but the scan never read it (virtual module, a file compiled by another tool such as MDX, require.context / import.meta.glob / computed import(), or a file outside the scanned roots and entries), the build keeps every marker and warns with the module and the reason. The scan now also follows require.context and import.meta.glob calls whose arguments are written out. Warm webpack builds read the reports of modules restored from the persistent cache. Dev servers, watch builds, Turbopack and the Rsbuild and Bun plugins keep every marker.
  • Stylesheets without any rule are emitted empty instead of as a bare license banner, so the empty shared base sheet no longer repeats the banner in every per-file stylesheet that imports it. The banner names the version without a trailing comma (v1.0.83, not v1.0.83,). A new licenseBanner plugin option (default true) and the setLicenseBanner/isLicenseBanner engine functions turn the banner off; both engines emit identical output.
  • Class names and file numbers no longer depend on the order files are processed in. Every plugin walks the files it can extract (the project's source and the included packages) before the first transform and numbers them in path order (a file collapsed into a bucket is numbered as the bucket, and only files that mention the package, StyleX or an aliased package take numbers) through the new seedFileMap, so identical builds give identical class prefixes, CSS file names and output hashes; in development, files that appear later are numbered after the existing ones. Styles are given class names in a fixed order, not the order of a hash set. The exported class, file and canonical maps are canonical JSON (sorted keys). Stylesheet evaluation (vanilla-extract) refuses Math.random(), Date.now(), new Date() and Date(), which differ between builds, with a build error; fixed dates such as new Date(0) are unchanged. resetBuildState starts a build from its own options: the prefix, atom hoisting, routes, buckets, names, numbers and styles an earlier build in the process left are cleared, and the prefix is set on every setup even when it is absent. Engine snapshots from concurrent transforms are written one after another per file, so an older snapshot is never written last. File lists are ordered by code point rather than the locale
  • A broken devup.json is reported instead of silently loading an empty theme. New errors: <file> is not valid JSON: <cause>, <file> must hold a JSON object, and devup.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.ts is 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
  • A project whose tsconfig.json (or jsconfig.json) builds JSX with Emotion (compilerOptions.jsxImportSource of @emotion/react, through extends and project references too) now compiles the css prop on every element of every file, and its .tsx and .jsx files are built with React's JSX runtime through a /** @jsxImportSource react */ pragma, which a file's own JSX pragma overrides, so the bundler no longer imports Emotion's runtime. The plugins read the setting into a new @emotion/react/jsx-runtime alias (importAliases can turn it off with false, and it is left out when @emotion/react is not aliased); @devup-ui/react/compat/emotion-jsx-runtime declares Emotion's JSX runtimes as React's so the project type-checks without Emotion installed. plugin-utils exports readJsxImportSource, and mergeImportAliases takes the JSX import source
  • Declare the Node.js versions the build-time packages need (Node 22 for the Vite plugin, which calls Promise.withResolvers) and replace the unrestricted vite, next, @rsbuild/core and typescript-eslint peers with the oldest major each plugin is written against: Vite 5, Next.js 13, Rsbuild 1 and typescript-eslint 8.
  • include package names match only the whole package directory under the innermost node_modules: foo.bar no longer compiles fooXbar, pkg no longer compiles @scope/pkg or pkg-extra, names with regex characters such as foo+bar are compiled, and dependencies nested in an included package's own node_modules are no longer compiled with it. Vite and Rsbuild build the matcher once instead of on every transformed module. No new build errors
  • Use a Devup-specific generated CSS revision query instead of Vite's immutable dependency version query, preventing cached stylesheet responses from breaking development module imports. No new build errors.
  • Document library mode in the Vite, Webpack and Rsbuild plugin READMEs: a library built with extractCss: false is published uncompiled, and every application that uses it must list the package in include.
  • MDX documents are extracted after the MDX plugin compiles them: the engine reads an .mdx filename as the JavaScript module (with or without JSX) an MDX compiler makes of it instead of rejecting the extension, the Vite plugin extracts .mdx in a post transform, and the webpack and Rsbuild plugins in a post loader; Next.js with Turbopack and the Bun plugin still leave MDX untransformed
  • A devup.json extends entry 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.
  • Package READMEs are refreshed: the benchmark tables show the current CI run and are regenerated with the root README from benchmark-results.json, the examples show the current generated class names instead of fixed d0/d1 names, and the Korean README link points to the repository; @devup-ui/components and @devup-ui/reset-css name their own package and install line and add a short usage section; the ESLint README notes that preset rules can report the same code. Documentation only
  • Compile .mts, .cts and .cjs modules in every plugin, Turbopack and the import graph, and resolve ./a.js, ./a.mjs and ./a.cjs imports to their TypeScript sources. Resolve package exports in the package's own order with the conditions of the bundler: Vite's resolve.conditions, the ESM conditions of webpack and Rspack per environment, and the target and conditions of Bun. Atom hoisting in webpack and Rsbuild plans over the src and app directories of the working directory and of the bundler root, not src alone. 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 .js and .cjs modules. No new build errors.
  • Resolve relative plugin options (devupFile, distDir, cssDir), the tsconfig and the webpack extraction ids against the bundler's project root (Vite root, webpack context, Rsbuild rootPath, Next's project directory for webpack builds, Bun.build root) instead of process.cwd(), so builds started from a parent directory as turbo or nx do read the project's devup.json and write its df. Builds started from the project root are unchanged. When devupFile is not set and only the working directory holds a devup.json, that file is still read and a one-time warning says to move it next to the project or set devupFile. Class names may change once for webpack and Next webpack builds run from a parent directory, because files are now numbered relative to the project root.
  • Refresh dependencies, including Oxc 0.156, wasm-bindgen 0.2.130, parse5 8.1 and Rsbuild 2.3. Preserve the React 18 compatibility fixture while updating its build tooling.
  • A source file deleted or renamed in watch mode or the dev server no longer leaves its styles behind: its globalCss, its own stylesheet and the class names handed out in it are dropped, and it leaves the bucket it collapsed into. The engine gains removeFile(filename) (native and WASM), which Vite calls on a delete watch 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
  • Custom shorthand targets are constrained to supported camelCase/kebab-case CSS properties, built-in aliases and valid custom properties. All five build adapters normalize options at creation before registration or extraction, including Next.js production cache reuse. Unsupported targets fail registration atomically with the original shorthand name, target and zero-based index; previously registered shorthands remain unchanged. New devup-ui option errors expose structured logical shorthands paths without inventing source coordinates. Eighteen dead unprefixed property names are rejected.
  • Every plugin takes stylex: { styleResolution }, StyleX's babel plugin option of the same name, and the engines take it through the new setStylexStyleResolution(). 'property-specificity' stays the default. 'application-order' gives a static stylex.create() key the null resets StyleX's table lists for the longhands it covers (and reads its aliases, marginStart as margin-inline-start), so the key applied last wins in stylex.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' into padding-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 given firstThatWorks() fallbacks, all under application-order and a listStyle StyleX cannot sort under legacy-expand-shorthands; an unknown styleResolution is a configuration error (StylexConfigError). Devup UI's own APIs ignore the option
  • Tailwind classes in a className read the Tailwind CSS of the project: the file that imports tailwindcss (the tailwind.css option of devup.json, else a conventional path) gives @theme variables (colors, spacing, shadows, blurs, radii, easings, animations with their @Keyframes, default transitions, breakpoints), @Utility utilities and @custom-variant variants, and the Vite, webpack and Next.js plugins read it again when it or a CSS file it imports changes. Anything that cannot be read exactly, and the classes of namespaces the build does not read, stay as written. More of Tailwind CSS v4 compiles: ring-, inset-ring-, ring-offset-* and drop-shadow-* compose with shadows and filters, borders and outlines draw in --tw-border-style and --tw-outline-style (a border now shows its style), line-clamp, text decoration, border-spacing, logical and scroll spacing, tables, perspective, font-stretch and more; the arguments of clsx(), classnames() and classNames() and [...].join(' ') compile in place. Radii follow v4 (rounded-sm is 0.25rem, rounded-full is calc(infinity * 1px)). No new build errors
  • A theme that cannot be loaded or registered (a broken devup.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
  • Update dependencies to their latest releases and migrate Oxc while preserving exact JavaScript string identity, static CSS output, and React 18/19 compatibility. Final CSS text, values, keys, and required evaluation-module specifiers containing unpaired UTF-16 surrogates now fail at build time with source locations instead of becoming lossy text or dynamic styling.
  • Hash devup-ui CSS asset names from the finished sheet instead of Vite's load-time snapshot, so identical sources give identical CSS and JS chunk names regardless of module order, and any style change gives the sheet and its importing chunks new names.
  • Qualify the physical-order matrix against the bundle devup-ui writes, not Vite's load-time sheet snapshot
  • Build again, once every environment is built, each Vite environment whose devup-ui sheets changed since, so client CSS also holds styles only a later environment (such as ssr) extracted, whatever the build order
  • Reserve short shared class and CSS-variable slots before Vite extraction across build, serve, and shared environments. Enable atom hoisting by default at two distinct physical module boundaries plus reachable dynamic targets, with zero opting out and singleCss unchanged. Install the closed-inventory canonical and reach plan before scratch and freeze it for the build lifetime, including watch updates. Discover static physical HTML inputs with a Vite-only build-time parse5 parser, keeping it outside non-Vite plugin and loader graphs, and refresh only dirty revisions without styling runtime or new intended source build-error categories.
  • Name each devup-ui sheet in the source Vite loads during a build, so two sheets that are equal when loaded are no longer emitted as one file holding only one of them
  • Add shared native/WASM compiler selection, structural compiler types and exact native platform-load diagnostics for build plugins.

@devup-ui/webpack-plugin@1.0.71 → 1.1.0 - packages/webpack-plugin/package.json

Minor

  • Require Node.js 20 or later for the build-time packages: Node 18 is past its end of life and does not expose the globalThis.crypto the WASM engine reads. The plugins, plugin-utils, the WASM engine and the native bindings now declare engines.node >=20 (the ESLint plugin ^20.9.0 || >=21.1.0, as typescript-eslint 8 requires; the Vite plugin keeps >=22).

Patch

  • Enable atomHoist by default at two boundaries in Vite, Webpack, Rsbuild and Next Webpack, with numeric zero opting out and no effect in singleCss mode. Keep Next Turbopack in per-file mode until its shared-slot reservation lands, warning once for explicit positive atomHoist requests. Allocate shared and file-local short counter names through deterministic reserved slots instead of content names; preserve frozen route plans, dynamic !important, local keyframes, first-value responsive tokens, shared CSS updates and persisted placement. Bump the naming cache generation. Stabilize Vite dev-sheet module identity with independent content-write revisions, preserving cache busting for changed CSS text and unchanged build paths. Track inherited configuration inputs, serialize refreshes and drain owned engine work before releasing shared build ownership. Reuse exact-input semantic extraction only in eligible exclusive serve sessions, registering dependencies on every request without retaining CSS snapshots or replaying writes; builds continue extracting normally. No new build errors.
  • When an optional setup step fails and the build goes on without it (Vite, webpack and Bun file numbering, the webpack and Rsbuild import graphs, the webpack stylesheet warm-up), print one warning naming the step, the cause and what the build loses instead of continuing silently. A project without a src directory stays quiet. No new build errors.
  • webpack (and Next.js on webpack) and Rsbuild watch every config devup.json extends, as Vite does, and reload the theme when one is edited, added or deleted. Rsbuild did not reload devup.json itself in dev before; webpack only watched a devup.json that existed when the build started
  • One-shot production builds with the Vite and webpack plugins (Next.js without Turbopack included) drop the component-selector markers no module selects. Each transform and the start-of-build scan report the markers they give and select; once every module is compiled, a marker no module selects or writes leaves the output chunks. When a module selects a component but the scan never read it (virtual module, a file compiled by another tool such as MDX, require.context / import.meta.glob / computed import(), or a file outside the scanned roots and entries), the build keeps every marker and warns with the module and the reason. The scan now also follows require.context and import.meta.glob calls whose arguments are written out. Warm webpack builds read the reports of modules restored from the persistent cache. Dev servers, watch builds, Turbopack and the Rsbuild and Bun plugins keep every marker.
  • Stylesheets without any rule are emitted empty instead of as a bare license banner, so the empty shared base sheet no longer repeats the banner in every per-file stylesheet that imports it. The banner names the version without a trailing comma (v1.0.83, not v1.0.83,). A new licenseBanner plugin option (default true) and the setLicenseBanner/isLicenseBanner engine functions turn the banner off; both engines emit identical output.
  • Webpack and Rsbuild builds hold every style in their stylesheets: a stylesheet module is built on its first import, so styles extracted later (the global styles of files webpack or Rsbuild reached late, often outside src) were missing from the output. The files the entries reach under src are 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 computeReachableFiles
  • Class names and file numbers no longer depend on the order files are processed in. Every plugin walks the files it can extract (the project's source and the included packages) before the first transform and numbers them in path order (a file collapsed into a bucket is numbered as the bucket, and only files that mention the package, StyleX or an aliased package take numbers) through the new seedFileMap, so identical builds give identical class prefixes, CSS file names and output hashes; in development, files that appear later are numbered after the existing ones. Styles are given class names in a fixed order, not the order of a hash set. The exported class, file and canonical maps are canonical JSON (sorted keys). Stylesheet evaluation (vanilla-extract) refuses Math.random(), Date.now(), new Date() and Date(), which differ between builds, with a build error; fixed dates such as new Date(0) are unchanged. resetBuildState starts a build from its own options: the prefix, atom hoisting, routes, buckets, names, numbers and styles an earlier build in the process left are cleared, and the prefix is set on every setup even when it is absent. Engine snapshots from concurrent transforms are written one after another per file, so an older snapshot is never written last. File lists are ordered by code point rather than the locale
  • A broken devup.json is reported instead of silently loading an empty theme. New errors: <file> is not valid JSON: <cause>, <file> must hold a JSON object, and devup.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.ts is 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
  • A project whose tsconfig.json (or jsconfig.json) builds JSX with Emotion (compilerOptions.jsxImportSource of @emotion/react, through extends and project references too) now compiles the css prop on every element of every file, and its .tsx and .jsx files are built with React's JSX runtime through a /** @jsxImportSource react */ pragma, which a file's own JSX pragma overrides, so the bundler no longer imports Emotion's runtime. The plugins read the setting into a new @emotion/react/jsx-runtime alias (importAliases can turn it off with false, and it is left out when @emotion/react is not aliased); @devup-ui/react/compat/emotion-jsx-runtime declares Emotion's JSX runtimes as React's so the project type-checks without Emotion installed. plugin-utils exports readJsxImportSource, and mergeImportAliases takes the JSX import source
  • Declare the Node.js versions the build-time packages need (Node 22 for the Vite plugin, which calls Promise.withResolvers) and replace the unrestricted vite, next, @rsbuild/core and typescript-eslint peers with the oldest major each plugin is written against: Vite 5, Next.js 13, Rsbuild 1 and typescript-eslint 8.
  • Serialize the CSS a transform returns only when it is read: a read after later transforms or setting changes still returns the sheet as that transform left it. The Next.js loader and prewarm never read it, and the Webpack loader reads it only when it writes it, so single-CSS builds no longer serialize the whole sheet after every module. The output is byte-identical.
  • Document library mode in the Vite, Webpack and Rsbuild plugin READMEs: a library built with extractCss: false is published uncompiled, and every application that uses it must list the package in include.
  • MDX documents are extracted after the MDX plugin compiles them: the engine reads an .mdx filename as the JavaScript module (with or without JSX) an MDX compiler makes of it instead of rejecting the extension, the Vite plugin extracts .mdx in a post transform, and the webpack and Rsbuild plugins in a post loader; Next.js with Turbopack and the Bun plugin still leave MDX untransformed
  • A devup.json extends entry 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.
  • Reconstruct the complete deterministic Next webpack stylesheet after each server, edge and client compiler reset, including accepted external package dependency closures, so delivered CSS matches rendered classes in per-file and single-CSS modes. Keep production CSS request paths stable across build IDs so persistent webpack cache cannot bypass the CSS loader. Genuine production prewarm collection, read and extraction failures now fail the build instead of silently dropping styles; failed initialization releases its build session without leaking styles into unrelated builds.
  • Accept JSX in .js, .mjs and .cjs throughout extraction without changing TypeScript dialects or plain JavaScript output, and pass parsed source-map objects to webpack callbacks for Next SWC compatibility. Malformed relevant source now fails with located parser diagnostics instead of unlocated parser-panic messages or silently recovered output.
  • Reserve existing short counter class, variable, keyframe and raw-file slots in physical input order before Bun, webpack, Rsbuild and Next webpack extraction. Watch revisions append sorted slots without renumbering. No new source build errors or styling runtime; unknown virtual, generated and opaque outside-inventory inputs retain observable residual allocation.
  • Package READMEs are refreshed: the benchmark tables show the current CI run and are regenerated with the root README from benchmark-results.json, the examples show the current generated class names instead of fixed d0/d1 names, and the Korean README link points to the repository; @devup-ui/components and @devup-ui/reset-css name their own package and install line and add a short usage section; the ESLint README notes that preset rules can report the same code. Documentation only
  • Compile .mts, .cts and .cjs modules in every plugin, Turbopack and the import graph, and resolve ./a.js, ./a.mjs and ./a.cjs imports to their TypeScript sources. Resolve package exports in the package's own order with the conditions of the bundler: Vite's resolve.conditions, the ESM conditions of webpack and Rspack per environment, and the target and conditions of Bun. Atom hoisting in webpack and Rsbuild plans over the src and app directories of the working directory and of the bundler root, not src alone. 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 .js and .cjs modules. No new build errors.
  • Resolve relative plugin options (devupFile, distDir, cssDir), the tsconfig and the webpack extraction ids against the bundler's project root (Vite root, webpack context, Rsbuild rootPath, Next's project directory for webpack builds, Bun.build root) instead of process.cwd(), so builds started from a parent directory as turbo or nx do read the project's devup.json and write its df. Builds started from the project root are unchanged. When devupFile is not set and only the working directory holds a devup.json, that file is still read and a one-time warning says to move it next to the project or set devupFile. Class names may change once for webpack and Next webpack builds run from a parent directory, because files are now numbered relative to the project root.
  • Resolve the imports the extractor follows against the bundler's project root (webpack's context, the Rsbuild root, the root of Bun.build) instead of the working directory, so a build started from a parent directory, as monorepo tools do, reads that project's tsconfig.json paths and resolves the relative imports of its root-relative webpack ids under the project.
  • A production prewarm no longer fails the build on a file it cannot extract. The Next.js prewarm still extracts every source file, but a file that does not parse (for example dead source no route imports) is now skipped with a warning naming the file and the error. If Next.js or webpack compiles that file, its loader still fails the build with the same error. Output for projects without such files is unchanged.
  • A source file deleted or renamed in watch mode or the dev server no longer leaves its styles behind: its globalCss, its own stylesheet and the class names handed out in it are dropped, and it leaves the bucket it collapsed into. The engine gains removeFile(filename) (native and WASM), which Vite calls on a delete watch 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
  • Read each source file once per build in the passes that run before the bundler. The import graph, the class-slot reservation and the prewarm read the same files, and a Next production build runs them once per compiler (server, edge, client): they now share a stamp-checked source cache (withSourceCache / readSource in 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.
  • Custom shorthand targets are constrained to supported camelCase/kebab-case CSS properties, built-in aliases and valid custom properties. All five build adapters normalize options at creation before registration or extraction, including Next.js production cache reuse. Unsupported targets fail registration atomically with the original shorthand name, target and zero-based index; previously registered shorthands remain unchanged. New devup-ui option errors expose structured logical shorthands paths without inventing source coordinates. Eighteen dead unprefixed property names are rejected.
  • Every plugin takes stylex: { styleResolution }, StyleX's babel plugin option of the same name, and the engines take it through the new setStylexStyleResolution(). 'property-specificity' stays the default. 'application-order' gives a static stylex.create() key the null resets StyleX's table lists for the longhands it covers (and reads its aliases, marginStart as margin-inline-start), so the key applied last wins in stylex.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' into padding-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 given firstThatWorks() fallbacks, all under application-order and a listStyle StyleX cannot sort under legacy-expand-shorthands; an unknown styleResolution is a configuration error (StylexConfigError). Devup UI's own APIs ignore the option
  • Tailwind classes in a className read the Tailwind CSS of the project: the file that imports tailwindcss (the tailwind.css option of devup.json, else a conventional path) gives @theme variables (colors, spacing, shadows, blurs, radii, easings, animations with their @Keyframes, default transitions, breakpoints), @Utility utilities and @custom-variant variants, and the Vite, webpack and Next.js plugins read it again when it or a CSS file it imports changes. Anything that cannot be read exactly, and the classes of namespaces the build does not read, stay as written. More of Tailwind CSS v4 compiles: ring-, inset-ring-, ring-offset-* and drop-shadow-* compose with shadows and filters, borders and outlines draw in --tw-border-style and --tw-outline-style (a border now shows its style), line-clamp, text decoration, border-spacing, logical and scroll spacing, tables, perspective, font-stretch and more; the arguments of clsx(), classnames() and classNames() and [...].join(' ') compile in place. Radii follow v4 (rounded-sm is 0.25rem, rounded-full is calc(infinity * 1px)). No new build errors
  • A theme that cannot be loaded or registered (a broken devup.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
  • Refresh all dependency ranges and regenerated lockfiles with the latest dependency-check-updates CLI, including Oxc 0.154, sourcemap 9, Next, React, Panda, Playwright, ESLint, Vinext and WASM dependencies. Preserve the existing hybrid CommonJS bundler language through exact top-level declaration-goal classification without changing parser AST, diagnostics or source-type metadata; real invalid syntax, including nested ES declarations, still produces located parser errors. Keep React 18 and 19 peer support and the React 18 fixture pins. No new build errors for valid supported styling inputs or styling runtime.
  • Add shared native/WASM compiler selection, structural compiler types and exact native platform-load diagnostics for build plugins.
  • Plan single-importer collapse and atom hoisting in webpack and Rsbuild, as in Vite, over the graph of the files the shared-slot reservation discovers: the src and app directories, the closures of the bundler's real entries and the included packages, with the entries as routes. The graph is built once per build and reused by the stylesheet warm-up instead of scanning the source tree two more times; the warm-up skips the package files the transform skips. Report a failed Rsbuild warm-up with a warning instead of ignoring it. Add reservationRoutes to plugin-utils.
  • Keep packed CommonJS Webpack plugins relocatable so initialization and both loaders use the installed package and the same WASM instance. Inherited theme declarations now survive in shipped production CSS in per-file and single-CSS modes. No new build errors.

@github-actions
github-actions Bot force-pushed the changepacks/main branch 2 times, most recently from 7652386 to e97ad4e Compare October 8, 2026 06:20
@github-actions
github-actions Bot force-pushed the changepacks/main branch 18 times, most recently from 91cef8f to f92f58d Compare October 24, 2026 12:29
@github-actions
github-actions Bot force-pushed the changepacks/main branch 6 times, most recently from d7cc06b to aacd59c Compare November 2, 2026 10:59
@github-actions
github-actions Bot force-pushed the changepacks/main branch 4 times, most recently from c8f5311 to ae27cf3 Compare November 14, 2026 11:12
@github-actions
github-actions Bot force-pushed the changepacks/main branch 7 times, most recently from 53e1ed5 to f6ff7a9 Compare November 17, 2026 03:15
@github-actions
github-actions Bot force-pushed the changepacks/main branch 16 times, most recently from ca16ba9 to c9683fc Compare November 19, 2026 08:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants