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

@ambientcss/components

v3.1.2

Published

React skeuomorphic components powered by Ambient CSS

Readme

@ambientcss/components

React components built with Ambient CSS.

Install

pnpm add @ambientcss/components @ambientcss/css

Usage

import "@ambientcss/css/ambient.css";
import "@ambientcss/components/styles.css";

import { AmbientButton, AmbientKnob, AmbientProvider } from "@ambientcss/components";

export function Example() {
  return (
    <AmbientProvider theme={{ keyLight: 0.45, fillLight: 0.18, lightX: -1, lightY: -1 }}>
      <AmbientButton>Play</AmbientButton>
      <AmbientKnob value={40} onChange={(next) => console.log(next)} />
    </AmbientProvider>
  );
}

Two layers

Every control is a mechanism — kinematics, value, state and ARIA — plus a skin. The named components are presets that pair one with a set of parts; underneath, the mechanism has no appearance of its own and will wear whatever you give it.

import { AmbientRotary, KnobBody, ScaleRing } from "@ambientcss/components";

<AmbientRotary
  value={gain} onChange={setGain}
  travel={{ start: -135, sweep: 270 }}
  input="drag"
  className="amb-knob"
  parts={{
    panel: <ScaleRing count={13} />,
    base: <KnobBody flush />,
    actuator: <MyPointer />,
  }}
/>

Parts drop into four frames — panel, base, actuator, fixture — painted in that order, of which only actuator moves. The control publishes its state on its own root as --ambx-percent, --ambx-angle, --ambx-size and friends, so a part can be pure CSS with no React state at all; useControlState() is the same data typed, for parts that need JS.

Mechanisms: AmbientRotary, AmbientTravel, AmbientPress, AmbientLatch, AmbientBank. Or take the hooks — useRotary, useTravel, usePress, useLatch, useBank — and render the markup yourself.

Full guide: Composing controls.