Button

Elevate the Nordstar visual language with a shared depth and motion system, then apply it across the components.

• New design tokens shipped from @nordcom/nordstar's CSS contract:
• Elevation — shadow-raised, shadow-overlay, shadow-floating, a three-step shadow scale tuned to read on the near-black default surface.
• Easing — ease-out-soft (hard deceleration for entrances) and ease-spring (a slight overshoot for toggles and presses).
• Motion — an overlay-in keyframe / animate-overlay-in utility used by portalled surfaces, plus accordion-down/accordion-up for disclosure height transitions. The existing prefers-reduced-motion reset neutralises them for users who opt out.
• Overlay surfaces (Select, DropdownMenu, Tooltip) now lift on the new shadow-overlay, animate in from their transform origin, and round to md. The Select chevron rotates while the listbox is open.
• `Button` gains a resting elevation on the solid variant, a subtle hover lift that settles on press, and a consistent keyboard focus ring.
• `Card` solid surfaces read as raised via shadow-raised.
• `Switch` thumb slides on the springy easing with a touch of depth.
• `Kbd` picks up a recessed keycap shadow.
• `Accordion` sections now expand and collapse with a measured height animation instead of snapping open.
• Motion timings across Input, Select, and the dropdown items were aligned to the shared duration/easing language.

No public APIs changed; these are visual and motion refinements within the existing design identity.

Fix <Button/> accessibility and interaction states:

• No longer forces role="button" on every rendered element. Rendering as a link (as="a") previously hid the native link role behind a button role; native semantics are now preserved for both <button> and other elements.
• disabled is now only applied as the native attribute on a real <button>. Polymorphic elements (as="a", as="div", …) previously received an invalid disabled attribute that browsers ignore, leaving them keyboard-focusable and clickable while only appearing dimmed. They now reflect the state via aria-disabled and are removed from the tab order so they are genuinely inert.
• The outline variant gains focus-visible and active feedback so keyboard users get a visible affordance, matching the solid variant.
• Replaced transition-all with a targeted transition so layout properties are no longer animated.
• data-color/data-variant and the JSDoc now reflect the real resolved defaults (solid/primary).

Fix <Button/> applying type="button" to non-button elements. Rendering with a custom as (e.g. as="a" for a link styled as a button) produced an invalid type attribute such as <a type="button">. The type attribute is now only set when the button renders as a native <button>.

Fix publishing.

Replace ESLint and Prettier with Biome 2.x. Single root biome.jsonc covers linting and formatting; turbo no longer orchestrates lint/format; CI now runs biome ci. Source files reformatted (trailing commas, sorted Tailwind classes, organized imports). No public API changes.

Bump requirement to react 19.

Update homepage.

Migrate to Tailwind v4 consumer DX. The lib now ships a tailwind.css contract (@theme + @source) for Tailwind v4 users and a precompiled styles.css for non-Tailwind users. Consumers no longer maintain a duplicate tailwind.config.cjs — instead, @import "@nordcom/nordstar" in their main CSS does it all. Runtime CSS variables move to the --nordstar-* namespace; the <NordstarProvider/> React API is unchanged.

Upgrade typescript.

Modernize build.

Upgrade deps

• Bogus change to trigger another npm publish (the previous release failed).

• Don't engage tailwind at the component level.

• Refactor components to use tailwind and cva.

• Update domain to https://nordcominc.github.io/nordstar/

Meta: Change codegen slightly.

Fix css module inclusions.

Fix engines field.

Upgrade turbo.

Add disabled state.

Fix #446: Button should have user-select: none;.

Button: Don't animate when disabled.

Fix export.

• Improve testing setup to be more reliable and consistent.
• Substantially improve both the output from the transpiler/compiler and the built type definitions.

• Improve exports.

• Fix types.
• Improve build output.

• Substantially improve testing.

• Remove clean-package and replace it with publishConfig _(this still needs testing)_.

• Switch from "jsx": "preserve" to "jsx": "react-jsx".
• Substantially improve both the vite and typescript configurations.
• Use references instead of extends in tsconfig.jsons. This allows for better type checking and faster builds.
• Properly create entry and rollupOptions' input file lists. This fixes a bunch of issues.
• Define __dirname, we previously tried using __dirname under esm which is not supported, somehow it didn't error or break the build but it's fixed now anyway.
• Some groundwork done to eventually support `jsr.io`

Meta: Migrate to bun from npm.

Improve general styling.

Add packageManager field and missing component descriptions.

Design: Fix styling.

Fix issues with <Input /> and improve color support.

Center button content.

Refactor <Button/> to use [data-content] and [data-icon], making it way easier to style without having add a bunch of custom className props.

Improve how tsc builds the packages/apps, we now use "moduleResolution": "Bundler" and "moduleDetection": "force".

Update package description.

Add support for rendering an icon.

Fix content alignment.

Refactor tests to use their own tsconfig; this is to prevent typepollution.

• Update release tooling, this should hopefully fix the issue with wildcard (*) dependencies. I will have to push a new release to verify.

• Completely refactored how packages are built, exported and reimported. We will have to look into a better way to deal with clean-package as we'd eventually like to be able to export the scss/css modules as well.
• Fixes code duplication inside of @nordcom/nordstar.
• No longer embeds jsx-runtime into every package.

Revert class name minification.

Export css, you should probably never need nor use this; but it is now available for those who might need direct access to the styling.

Add <Button/> component for triggering actionable events on an interaction.