Published
June moves Elements onto the stable 2.0 release line and broadens the APIs and starters available for production projects.
Highlights
- Prepare for the 2.0 upgrade. The stable 2.0 packages remove deprecated component and style APIs. Review the migration guide before upgrading; updated lint rules identify old tags, attributes, slots, popover settings, and CSS custom properties.
- Build consistent form controls. The Forms package adds reusable button, checkbox, select, and slider mixins that coordinate native behavior, state, validation, commands, and popover triggers.
- Start more kinds of applications. New starters cover MCP Apps, Lit libraries, and HTMX with Go. The existing Go starter also gains corrected CDN loading and a simpler server setup.
- Install the CLI across platforms. The Elements CLI adds a PowerShell installer for Windows and strengthens shell installation, version checks, build approvals, and error feedback.
- Keep controls stable through lifecycle changes. Forms improve ARIA state management, while Core restores native reset behavior, prevents duplicate observers after reconnection, and adapts scoped registries and popovers to Chromium changes.
Released packages
@nvidia-elements/cli0.3.0–0.3.1, 2.0.0–2.0.1, 2.1.0–2.1.3@nvidia-elements/code2.0.0–2.0.1@nvidia-elements/core0.2.2–0.2.4, 2.0.0–2.0.2@nvidia-elements/forms0.1.0, 2.0.0–2.0.1@nvidia-elements/lint0.4.0, 2.0.0–2.0.1@nvidia-elements/markdown2.0.0–2.0.1@nvidia-elements/monaco0.0.12, 2.0.0–2.0.1@nvidia-elements/styles0.0.10, 2.0.0–2.0.2@nvidia-elements/themes2.0.0