Skip to content

CHANGELOG.md

Latest commit

 

History

History
237 lines (145 loc) · 7.21 KB

CHANGELOG.md

File metadata and controls

237 lines (145 loc) · 7.21 KB
Raw

@xds/build

0.4.6

0.4.5

0.4.4

0.4.3

0.4.2

0.4.1

0.4.0

Fixes

  • build: import node:fs statically so the Vite plugin's package discovery survives the ESM build (#4972) astryxStylex()'s config plugin discovered installed @astryxdesign/* packages with require('node:fs'). The ./vite export ships only an ESM bundle (dist/vite.mjs, esbuild format: 'esm'), where esbuild lowers require to a shim that throws Dynamic require of "node:fs" is not supported — always, since native require never exists under ESM. The surrounding try/catch swallowed the throw, so optimizeDeps.exclude silently fell back to ['@astryxdesign/core'] and every other installed Astryx package stayed eligible for Vite pre-bundling, which strips stylex.create/defineVars calls and causes runtime errors.

    The discovery now uses a static import fs from 'node:fs', which esbuild preserves as a real ESM import. A regression test compiles vite.ts with the same esbuild options as build.mjs and runs the discovery in a child node process, since in-process test runners provide a require shim that masks the bug.

Contributors

Thanks to everyone who contributed to this release:

  • @is-jain

0.3.0

0.2.0

0.1.9

Fixes

  • Scope the source resolve condition to @astryxdesign packages in withAstryx withAstryx set webpack's conditionNames to ['source', …] globally, which resolved any dependency shipping a source export to its raw TypeScript — not just Astryx packages. Third-party deps that ship a source export (e.g. lexical, pulled in by the new RichTextEditor lab component) were then fed untranspiled .ts through Next's babel and failed on syntax like declare class fields.

Contributors

Thanks to everyone who contributed to this release:

  • @potatowagon

0.1.8

0.1.7

0.1.6

0.1.5

Other Changes

  • Use node: protocol prefix for Node.js builtin imports (#3737)

Contributors

Thanks to everyone who contributed to this release:

  • @Han5991

0.1.4

0.1.3

Fixes

  • Use pnpm build in the prepack script so publishing no longer fails the devEngines package-manager check (#3564).

Contributors

Thanks to everyone who contributed to this release:

  • @cixzhang

0.1.2

Fixes

  • ship TypeScript declarations for the @astryxdesign/build/vite export

Contributors

Thanks to everyone who contributed to this release:

  • @benjipeng

0.1.1

Breaking Changes

  • Rename @xds/build exports off the xds name The Vite integration's public exports are renamed: xdsStylex -> astryxStylex, and the option types XDSVitePluginOptions / XDSVitePluginLegacyOptions -> AstryxVitePluginOptions / AstryxVitePluginLegacyOptions. Update imports from @xds/build/vite accordingly. Internal plugin names and the babel wrapper are also rebranded. Part of removing xds naming from the public API.
  • Rename Next.js helper withXDS to withAstryx The Next.js configuration wrapper is renamed withXDS -> withAstryx (exported from @astryxdesign/build/next). Update your next.config.mjs: import {withAstryx} from '@astryxdesign/build/next'. Part of removing xds naming from the public API.

Contributors

Thanks to everyone who contributed to this release:

  • @ejhammond

0.1.0

Breaking Changes

  • Default the StyleX library atomic-class prefix to astryx (was xds) @astryxdesign/build's babel/Vite integrations now emit library atomic classes as .astryx78zum5 by default instead of .xds78zum5 (the libraryPrefix / stylexPrefix option default flips xds -> astryx). This is an opaque, StyleX-generated namespace — consumers don't target these classes directly — but it completes the removal of xds naming from build output. Consumers that explicitly configured libraryPrefix/stylexPrefix are unaffected.
  • Remove the XDS-prefix compatibility layer — astryx is now the only public surface This release erases all xds naming from the public API; there is no compatibility window. Consumers must migrate (we own all consumers pre-OSS):
  • Remove the daily, brutalist, and default themes; neutral is the new baseline Three theme packages are removed from the repo and will no longer be published:

Other Changes

  • Component names: the XDS* aliases are gone — use bare names (Button not XDSButton, useTheme not useXDSTheme, ButtonProps not XDSButtonProps). The drop-xds-prefix-imports codemod automates this.

  • CSS classes: components emit only .astryx-* (the dual .xds-* class is gone). Update custom CSS selectors .xds-button -> .astryx-button (prop/state value classes like .primary/.sm are unchanged).

  • data attributes: only data-astryx-theme / data-astryx-media are written; update custom selectors and SSR root attributes off data-xds-*.

  • CSS layers: @layer xds-base / xds-theme are renamed to astryx-base / astryx-theme; update your @layer order line and any PostCSS layersBefore config. @astryxdesign/build's default library layer is now astryx-base.

  • Pre-compiled stylesheet: the @astryxdesign/core/xds.css export is removed — import @astryxdesign/core/astryx.css.

  • CSS custom properties: the --xds-* padding fallback is gone; set --astryx-*.

  • CLI config key: @astryxdesign/cli reads the package.json "astryx" field (was "xds"). Rename the block; a stale "xds" key silently drops the package from discovery.

  • @astryxdesign/theme-daily

  • @astryxdesign/theme-brutalist

  • @astryxdesign/theme-default

  • import {defaultTheme} from '@astryxdesign/theme-default/built';

    • import {neutralTheme} from '@astryxdesign/theme-neutral/built';

  • ...

    • ...

  • Rename the npm package scope from @xds/* to @astryxdesign/* All published packages move to the new @astryxdesign scope (e.g. @xds/core → @astryxdesign/core), along with the workspace lockfile, build/runtime scope-directory scans, and docsite slug derivation. Consumers must update their imports and dependency names. The internal ESLint plugin namespace (@xds/* rules) is intentionally untouched and tracked separately. Existing @xds/* codemods continue to target the old scope so projects still on @xds/* can migrate.

Contributors

Thanks to everyone who contributed to this release:

  • @cixzhang
  • @ejhammond

0.0.15

Fixes

  • Unprefix migration alignment — Build output and Vite plugin updated for the XDS-prefix migration (bare names canonical, XDS* compat aliases) so generated CSS stays in sync with @xds/core (#2941).

Contributors

Thanks to everyone who contributed to this release:

  • @cixzhang
  • @czarandy
  • @ejhammond
  • @josephfarina

0.0.14

First public release — @xds/build is now published to the npm registry.

New Features

  • Streamlined xdsStylex() Vite API — Simplified configuration for Vite projects (#2227)
  • Build step for Vite plugin — Proper dist output for the Vite integration (#2205)

Internal

  • Migrated to pnpm (#2197)
  • Bumped esbuild from 0.24.2 to 0.28.0 (#2246)