AuraGlass 3.2 release notes
AuraGlass 3.2 adds first-party icons, headless primitives, an app-shell module, a workspace module, Theme Engine 2.0, and an aura-glass migration CLI.
#What 3.2 ships
AuraGlass 3.2 moves icons, primitives, app-shell components, workspace shells, and the theme engine into first-party package entrypoints. Core app chrome — buttons, cards, menus, selects, dialogs, tabs, navigation, shells — now ships directly from the `aura-glass` package. Domain peers (chart.js, three, AI services, sentry, react-hook-form) stay optional and are only installed when you import from a feature family that uses them.
The new entrypoints are `aura-glass/icons` (and per-category subpaths), `aura-glass/primitives` (Slot, Portal, FocusScope, DismissableLayer, RovingFocusGroup, Positioner), `aura-glass/app-shell` (GlassAppShell, GlassTopBar, GlassSidebarRail, GlassMain, GlassPage, GlassPageHeader, GlassBreadcrumbs, GlassStatusBar), `aura-glass/workspace`, and `aura-glass/theme` (GlassThemeProvider, useGlassTheme, createBrandGlassTheme). The `aura-glass` CLI handles install audits, recipe scaffolding, and import codemods.
#New entrypoints
AuraGlass 3.2 publishes six token formats and a tightly scoped set of new package entrypoints. Each one is tree-shakable so apps only pay for what they import.
#Migration CLI
The 3.2 release ships a `aura-glass` CLI binary that audits the current project and rewrites imports onto AuraGlass equivalents. All commands accept `--dry-run` and `--json` for safe rollouts and agent integration.
npx aura-glass list
npx aura-glass info saas-dashboard
npx aura-glass add ai-command-center
npx aura-glass audit deps --json
npx aura-glass audit imports --json
npx aura-glass migrate icons --from lucide --dry-run
npx aura-glass migrate radix --dry-run
npx aura-glass migrate mui --dry-run
npx aura-glass doctor --json#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
Most 3.1 apps are forward-compatible with 3.2. The opt-in upgrade path is: (1) replace `lucide-react` imports with the matching `aura-glass/icons/*` category, (2) replace Radix primitive imports with `aura-glass/primitives/*` equivalents, (3) move to the native app-shell / workspace components if you previously assembled the chrome yourself, and (4) adopt Theme Engine 2.0 via `aura-glass/theme` for brand themes, density, motion, and contrast modes.
Run `npx aura-glass doctor` to verify install health and `npx aura-glass audit imports --json` to surface every peer import the CLI knows how to rewrite. Then run `npx aura-glass migrate icons --from lucide --dry-run` (and the radix/mui equivalents) to preview a codemod before applying.
import { GlassButton, GlassCard, OptimizedGlass } from 'aura-glass';
import { Sparkle } from 'aura-glass/icons/ai';
import { ChevronDown } from 'aura-glass/icons/navigation';
import { Slot } from 'aura-glass/primitives/slot';
import { ThemeProvider, usePersonaTheme } from 'aura-glass';
import 'aura-glass/styles';#Recipes ready to drop in
The package registry now ships ten launch recipes that scaffold full product surfaces. They run against the published package surface and write into `src/components/auraglass/recipes` by default. Use `--out` to target a different directory and `--dry-run` to preview the write set.
npx aura-glass add saas-dashboard
npx aura-glass add ai-command-center
npx aura-glass add media-player-surface
npx aura-glass add analytics-overview
npx aura-glass add settings-billing
npx aura-glass add kanban-workspace
npx aura-glass add calendar-schedule
npx aura-glass add collaborative-workspace
npx aura-glass add admin-data-table
npx aura-glass add ecommerce-product-panel#Verification checklist
Treat the 3.2 migration as complete when the app builds with no `lucide-react`, `@radix-ui/*`, or `@mui/*` imports for core AuraGlass app chrome, the stylesheet is imported once at the app root, the `aura-glass` CLI doctor passes, and at least one recipe has been used in production to validate the registry contract. Keep optional peers installed only for the feature families that need them.