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

ambientui

v0.1.15

Published

The ambient layer — an AI assistant surface that lives above a product rather than inside its component tree.

Downloads

922

Readme

ambientui

An AI assistant that lives above your product instead of inside it, built from your own design system.

Most products add AI by finding a spot for it: a chat tab, a sparkle button, a panel in the corner. This is the other approach. The assistant is a layer over your product rather than a room inside it. It takes no space, it knows what page it is on, it answers with real components instead of walls of text, and it has no colours, fonts or motion of its own. It borrows yours.

One assistant, five shapes: the orb resting at the edge of the page, the spotlight (Cmd-K, rebuilt for a product with AI in it), the panel that stays open while you work, the dock pinned full height, and the history over everything you have asked. You move between them by dragging the orb.

See it running at ambientui.ai.

Two ways to take it

As source you own (most people; restyling it is the point):

npx shadcn add https://registry.ambientui.ai/r/ambient-layer.json

This lands the components plus styles/ambient.css, the layer's material. Import it in your global stylesheet after the Tailwind import (the surfaces render transparent without it):

@import "tailwindcss";
@import "./styles/ambient.css";

As this package (you get fixes by bumping a version, and you cannot change the inside):

npm i ambientui

The trade-off between the two is written up at registry vs npm.

Mounting it

import { AssistantProvider, Assistant } from "ambientui"
import "ambientui/styles/ambient.css"

<AssistantProvider navItems={NAV} onNavigate={(id) => router.push(id)}>
  {children}
  <Assistant />
</AssistantProvider>

It needs no other providers. With none it falls back to sane defaults; supply your own design system by wrapping it in AmbientRuntimeProvider (the complete contract is ambient-runtime.tsx: seven values and two motion hooks). The orb's shader shapes ship as static files under ambientui/assets/*; serve them from your public root.

Requires React 19, Tailwind CSS v4 and the standard shadcn variables. framer-motion is a peer dependency.

The rest of the system

MIT (c) Lumenridge