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

@kaizen/well

v3.2.1-canary.1943

Published

The well component

Readme


title: "Well" navTitle: "Well" summaryParagraph: Wells are used as a visual container around secondary content. tags: ["Placeholder", "Content area", "Frame", "Card", "Group", "Box", "Container"] needToKnow:

  • "For primary content, use a Card instead."
  • "Usually, wells are used in other components, such as Empty States and drag and drop file upload, instead of independently." demoStoryId: well-react--default-with-solid-border-kaizen-site-demo

import WhenToUseAndWhenNotToUse from "docs-components/WhenToUseAndWhenNotToUse" import WhenToUse from "docs-components/WhenToUse" import WhenNotToUse from "docs-components/WhenNotToUse"

UI Kit

Options

  • Mood:
    • Default
    • Positive
    • Informative
    • Cautionary
    • Negative
    • Assertive
    • Prominent
  • Border style:
    • Solid
    • Dashed
    • None

To keep in mind

  • We need boundaries to define or contextualize secondary content. Wells can provide a way to do this visually.
  • An Empty State Well defines an area that doesn’t currently have content, but could.
  • A Drag & Drop Well provides a visible target to drop content into.
  • An Internal Content Well helps to define, divide or shape content within a card.
  • An External Content Well wraps one or more cards or pieces of content into a group.

When to use and when not to use

  • Use a well for secondary content.
  • For primary content, use a Card instead.
  • Don’t use a well inside well (even if there is a card separating them).
  • Don’t use as a Notification.
  • Don’t use as a Tooltip.

External links

Here are some examples of other existing design systems: