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

@primeuicom/cli

v1.1.10

Published

CLI utility for deploying PrimeUI exported projects to a local workspace.

Downloads

2,073

Readme

@primeuicom/cli

CLI utility for deploying PrimeUI exported projects to a local workspace.

Requirements

  • Node.js >=18
  • pnpm recommended for local development

Quick Start

npx @primeuicom/cli <api-key>

Skip git initialization and the initial commit:

npx @primeuicom/cli <api-key> --no-git

The command runs a fully autonomous flow:

  1. Validates API key format.
  2. Authenticates with PrimeUI API v1.
  3. Triggers project export.
  4. Downloads export ZIP archive.
  5. Extracts files into ./<project-name-slug>.
  6. Installs project dependencies with detected package manager.

Connect an existing project to PrimeUI:

npx @primeuicom/cli <api-key> connect

The command runs:

  1. Validates API key format.
  2. Authenticates with PrimeUI API v1.
  3. Detects project/monorepo root
  4. Request project info API endpoint
  5. Ensures the root .gitignore ignores .primeui/project.json and .primeui/temp/
  6. Generates config schema:
{
  "projectId": "project-id-from-primeui",
  "apiKey": "pui_xxxxxxxxxxxxxxxxxxxxxx",
  "targetProjectPath": "./"
}
  • If .primeui already exists in current directory chain, command stops and asks to remove existing config manually before reconnect.

Pull a fresh export into an already connected local project:

npx @primeuicom/cli pull

Optional API key override:

npx @primeuicom/cli <api-key> pull

The command runs:

  1. Loads .primeui/project.json from the connected project.
  2. Uses the stored API key unless you pass an explicit one.
  3. Refuses to continue when git status is not clean.
  4. Requires an explicit confirmation before rewriting files.
  5. Creates a fresh PrimeUI export and downloads the ZIP archive.
  6. Hard rewrites the configured target project path while preserving .git, .primeui, and node_modules.
  7. Reinstalls dependencies with the detected package manager.
  8. Creates a git commit with the refreshed export state when files changed.
  • Passing an explicit API key also refreshes .primeui/project.json with the current project binding.
  • If .primeui/project.json is missing in a clean exported project, npx @primeuicom/cli <api-key> pull recreates it before committing the refreshed state.
  • If the repository looks like a monorepo and PrimeUI cannot recover the saved target path, run connect explicitly first so you can choose the correct project folder before pull.
  • pull is intended for early-stage sync before heavy manual customization.
  • pull is not a merge tool. Local files outside the preserved directories can be replaced or removed.

Local development and testing

Configure these environment variables for local development:

  • PRIMEUI_API_BASE_URL: PrimeUI API base URL (for example http://localhost:3020 when testing against local Studio API).

Publish

Publish flow includes:

  1. Update the package version (usually a patch bump).
  2. Publish with the latest tag:
npm publish --tag latest

Credits

PrimeUI 2026