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

create-promptframe-component

v0.1.32

Published

Create a PromptFrame-compatible video component project from the standard React template.

Readme

create-promptframe-component

Create a PromptFrame-compatible video component project from the standard React template.

The generated project has no Git remote by default. It is meant to be validated and uploaded through @promptframe/cli.

npx create-promptframe-component ./my-component --name my-component --display-name "My Component"

Advanced teams can scaffold an explicit multi-component workspace:

npx create-promptframe-component ./component-workspace \
  --workspace \
  --component image-particle-remotion \
  --display-name "Image Particle Remotion"
cd component-workspace
npx promptframe workspace validate . --json
npx promptframe check . --workspace-component @marketplace/image-particle-remotion --json
npx promptframe setup-ci . --provider github --workspace

The generated workspace writes promptframe-workspace.json, a root package.json, and pnpm-workspace.yaml. Use this mode only when the repository intentionally owns multiple independent components; otherwise keep one component per repository.

Running the same --workspace command against an existing workspace appends the new component and merges root files. It preserves existing component registrations and root package scripts, and CI workflows stay managed from the repository root through promptframe setup-ci . --provider github --workspace.

Use --force only when intentionally refreshing template files in an existing target directory.