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

base-vaul

v1.0.0

Published

Drawer component for React made with Base-UI.

Downloads

414

Readme

Note This repository is a port of the original Vaul library by Emil Kowalski, migrated from radix-ui to base-ui.

Purpose

The primary goal of this repository is to provide a base-ui equivalent of Vaul while preserving the original API and behavior as closely as possible.

This port intentionally minimizes changes in order to:

  • Reduce migration friction for existing Vaul users
  • Keep parity with the upstream project
  • Establish a stable baseline before introducing enhancements or divergence

Quick start

Installation

npm install base-vaul
# or
pnpm add base-vaul
# or
yarn add base-vaul

Basic usage

import { Drawer } from 'base-vaul';

export function Example() {
  return (
    <Drawer.Root>
      <Drawer.Trigger>Open drawer</Drawer.Trigger>

      <Drawer.Portal>
        <Drawer.Overlay />
        <Drawer.Content>
          <Drawer.Title>Drawer title</Drawer.Title>
          <Drawer.Description>Drawer description</Drawer.Description>
        </Drawer.Content>
      </Drawer.Portal>
    </Drawer.Root>
  );
}

The API mirrors the original Vaul implementation as closely as possible, with the main differences coming from the underlying base-ui primitives.

Differences from the original Vaul

render instead of asChild

Since base-ui does not support asChild, components that relied on this pattern in radix-ui now expose a render prop instead.

Original (Radix / Vaul):

<Drawer.Trigger asChild>
  <button>Open drawer</button>
</Drawer.Trigger>

This port (Base UI):

<Drawer.Trigger render={<button {...props}>Open drawer</button>} />

Roadmap

Planned next steps include:

  • Writing proper documentation (usage, API, and migration notes)
  • Solidifying the project structure with a well-defined monorepo setup
  • Upgrading development dependencies and expanding test coverage
  • Ongoing maintenance, bug fixes, and alignment with upstream changes where relevant