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

@pdxui/framework

v1.0.0-beta.1

Published

The PDX UI runtime in one install: core, design, ui, router. The pdx CLI is a separate dev dependency: @pdxui/cli.

Readme

@pdxui/framework

The PDX UI runtime in one install: @pdxui/core, @pdxui/design, @pdxui/ui and @pdxui/router.

pnpm add @pdxui/framework @pdxui/compiler
pnpm add -D @pdxui/cli

| Import | Contents | |--------|----------| | @pdxui/framework | Everything the four packages export | | @pdxui/framework/core, /ui, /router | One package at a time | | @pdxui/framework/css | Everything the design system styles — every component and all 13 themes — for a page that does not know which components it will render |

An app that knows what it renders imports @pdxui/design/base and one theme (@pdxui/design/themes/neutral applies with no pdx-theme on <html>), and each component brings its own CSS; that is what pdx new project writes.

The CLI is a separate dev dependency, and so is the compiler, which is a build-time Vite plugin. Neither ships to the browser. An application that wants to choose its packages installs them one by one instead.

Start from Getting Started.

License

MIT, as are the packages it bundles. See docs/LICENSING.md.