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/cli

v1.0.0-beta.1

Published

The pdx CLI for PDX UI — build, check, analyze, scaffold .pdx components

Readme

@pdxui/cli

The pdx command for PDX UI projects. Install it as a dev dependency:

pnpm add -D @pdxui/cli

| Command | What it does | |---------|--------------| | pdx dev | Development server with HMR: .pdx files are interpreted, with no build | | pdx build | Production build, compiled with knowledge of the whole project; --ssg writes a page for every static route, which the app hydrates | | pdx check | Validates .pdx files: structured diagnostics with suggested fixes (--json, --fix), and the TypeScript check of scripts and templates with --types | | pdx explain <code> | What a PDX_* diagnostic means, and how to fix it | | pdx migrate | Rewrites the forms the beta removed or changed, and lists the ones to rewrite by hand | | pdx new component\|page\|project <name> | Scaffolding | | pdx analyze | Writes the component manifest (pdx-manifest.json) | | pdx mcp | Serves the CLI to an agent as an MCP server over stdio | | pdx theme <name> --brand <color> | Generates a theme that passes WCAG AA from a brand colour | | pdx i18n extract\|types\|validate | Translation keys: a template, typed keys, dictionary checks (pdx extract is the first, on its own) | | pdx builder | Starts the component tester and theme builder |

A pdx.config.ts at the project root configures root, routes, components, prefix, build (outDir, minify, target), plugins and ssg. A config file that exists and cannot be loaded stops the command with the error. It never falls back silently to the defaults.

Documentation

CLI and making a theme.

License

MIT.