npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@optiaxiom/react

v3.6.1

Published

Readme

Axiom

A React implementation of Optimizely's Axiom Design System.

Installation

Install the package using your package manager of choice:

npm install @optiaxiom/react

AI Assistant Integration

We provide an MCP server that enables AI assistants like Claude Code and Cursor to access accurate Axiom component metadata, design tokens, and usage examples:

claude mcp add --scope project axiom -- npx -y @optiaxiom/mcp@latest

See the MCP guide for setup instructions.

Getting Started

1. Setup CSS Imports

Configure your bundler to handle CSS imports. For most modern bundlers (Vite, Next.js, Create React App), this works out of the box. For custom setups, see our CSS imports guide.

2. Add the Provider

Wrap your application with AxiomProvider:

import { AxiomProvider } from "@optiaxiom/react";

export function App() {
  return <AxiomProvider>{/* Your app code here */}</AxiomProvider>;
}

3. Use Components

Import and use components in your application:

import { Box, Button, Group, Input } from "@optiaxiom/react";

export function MyComponent() {
  return (
    <Group alignItems="start" flexDirection="column" gap="16">
      <Input placeholder="Enter text..." />
      <Button appearance="primary">Submit</Button>
    </Group>
  );
}

Examples

Basic Button

import { Button } from "@optiaxiom/react";

<Button>Click me</Button>;

Form with Validation

import { Button, Field, Group, Input } from "@optiaxiom/react";

function LoginForm() {
  return (
    <Group alignItems="start" flexDirection="column" gap="16">
      <Field label="Email">
        <Input placeholder="[email protected]" type="email" />
      </Field>
      <Field label="Password">
        <Input type="password" />
      </Field>
      <Button appearance="primary">Sign In</Button>
    </Group>
  );
}

Layout with Box and Group

import { Box, Group, Heading, Text } from "@optiaxiom/react";

function Sample() {
  return (
    <Box bg="bg.default" color="fg.default" p="16" rounded="md" shadow="sm">
      <Group flexDirection="column" gap="16">
        <Heading level="3">Sample Title</Heading>
        <Text>Sample description goes here</Text>
      </Group>
    </Box>
  );
}

Documentation

For comprehensive guides, component API reference, and more examples:

Pinned dependencies

Every @radix-ui/* dependency is pinned to an exact version. Radix packages pin each other exactly, so ranges would let an install mix release waves and duplicate internals such as the dismissable layer stack, which only works within one copy. Move them together, and only past these holds:

| Package | Held at | Why | Lift when | | ------------------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- | | @radix-ui/react-toast | 1.2.24 | 1.3.x renders no toasts on React 16/17: its startTransition fallback drops the updates (radix-ui/primitives#4228). The rest of the Radix packages stay on Toast 1.2.24's release. | The fix (#4231) ships. | | @radix-ui/react-tabs | 1.1.21 | 1.1.22 calls onValueChange twice per click (radix-ui/primitives#4266). | A release fixes the double call. | | @radix-ui/react-context | 1.1.4 | 1.2.0 and later type its hooks with interfaces it doesn't export, so our exported context hooks fail declaration emit (TS4023, radix-ui/primitives#4098). | The fix (#4204) ships in a stable release. |

Every @dnd-kit/* package is a devDependency pinned to one exact version and bundled into our dist, so consumers install none of them. @dnd-kit/react calls React 18 APIs and is patched (patches/@dnd-kit__react.patch) to fall back on React 16/17. The packages require each other at matching versions, so move them together and check the patch still applies after each bump. @preact/signals-core, which @dnd-kit/state depends on, is listed as a ranged devDependency, not imported anywhere: listing it is how the dependency update workflow keeps the bundled copy current.

CI runs the specs on React 17 as well as 18, so a bump that breaks React 17 fails there.

Contributing

See the main repository for contribution guidelines.

License

Apache-2.0