AuraGlass 3.2 release notes

#What 3.2 ships

This page records the 3.2 entrypoint layout for history; the current contract is 5.0. In 5.0, icons, primitives, app-shell components, data, date, AI, and media surfaces ship from focused first-party subpaths, and core app chrome — buttons, cards, menus, selects, dialogs, tabs, navigation, shells — ships from `aura-glass` and `aura-glass/app-shell`. Optional peers (three, react-hook-form, the date peers, d3-scale/d3-shape, motion) are installed only for the subpath that needs them.

The current 5.0 entrypoints are `aura-glass` (core components plus `AuraGlassProvider`), `aura-glass/icons`, `aura-glass/primitives` (Slot, Portal, FocusScope, DismissableLayer, Label, VisuallyHidden), `aura-glass/app-shell` (AppShell, Sidebar, TopBar, StatusBar, Inspector, MobileShell), `aura-glass/data`, `aura-glass/date`, `aura-glass/ai`, `aura-glass/media`, `aura-glass/theme` (AuraGlassProvider, createBrandTheme, createGlassTheme, presets), and `aura-glass/compat` for deprecated 4.x names. The `aura-glass-cli` CLI handles install audits, registry blocks, and the 4to5 codemod.

#New entrypoints

AuraGlass 5.0 publishes a tightly scoped set of package entrypoints, each with its own types. The 3.2-era alias subpaths for navigation, overlays, workflows, marketing, workspace, and the recipe registry were removed in 5.0; import the canonical exports below instead.

#Migration CLI

In 5.0 the CLI ships as the separate `aura-glass-cli` package. It audits the current project, installs registry blocks as owned source, and runs the 4.x to 5.0 codemods; `migrate 4to5 --dry-run` previews every change before writing.

npx aura-glass-cli init
npx aura-glass-cli add app-frame
npx aura-glass-cli list
npx aura-glass-cli doctor
npx aura-glass-cli migrate 4to5 --dry-run

#Flagship surfaces in 3.2

3.2 names a flagship set so the launch is easy to evaluate. Start with these components when bringing a 3.1 app up to 3.2 — they cover core surfaces, overlays, navigation, app shell, dashboards, scheduling, media, primitives, and product-ready surfaces.

#Migrating from 3.1 to 3.2

For the current release, migrate any 3.x or 4.x app directly to 5.0: (1) run `npx aura-glass-cli migrate 4to5` to rename 4.x exports to canonical 5.0 names, move subpath imports, and rename `--ag-*` tokens, (2) replace third-party icon imports with `aura-glass/icons`, (3) compose app chrome from `aura-glass/app-shell`, and (4) wrap the app in `AuraGlassProvider` and theme through `aura-glass/theme`. Names with no 5.0 successor keep working temporarily from `aura-glass/compat` with a deprecation warning.

Run `npx aura-glass-cli migrate 4to5 --dry-run` to preview the codemod, apply it, then run `npx aura-glass-cli doctor` to verify versions, peers, and CSS layers.

import { AuraGlassProvider, Button, Card, Surface } from 'aura-glass';
import { ChevronDownIcon, SparklesIcon } from 'aura-glass/icons';
import { Slot } from 'aura-glass/primitives';
import 'aura-glass/styles.css';

#Recipes ready to drop in

Registry blocks scaffold full product surfaces as source you own. Install the app frame first, then browse the registry for larger blocks.

npx aura-glass-cli init
npx aura-glass-cli add app-frame
npx aura-glass-cli list

#Verification checklist

Treat a migration as complete when every import resolves to a 5.0 export (or a deliberate, temporary `aura-glass/compat` import), `aura-glass/styles.css` is imported once at the app root, `npx aura-glass-cli doctor` passes, and optional peers are installed only for the subpaths in use.