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

new-video-project

v1.1.3

Published

A fast CLI for filmmakers and content creators who want a clean project structure before the first cut.

Readme

new-video-project

A fast CLI for filmmakers and content creators who want a clean project structure before the first cut.

npm version license runtime GitHub Sponsors Ko-fi Buy Me A Coffee

Why this exists

If you edit long-form videos, short-form clips, YouTube episodes, or client projects, you already know this problem:

  • footage gets dropped in random folders
  • exports get mixed with source media
  • frame grabs and overlays disappear into chaos
  • handoff to collaborators becomes painful

This CLI gives you a dependable folder system in seconds, so your timeline stays the hard part, not your file management.

Built for creators

  • YouTubers and educators
  • Documentary and indie filmmakers
  • Social editors (Reels, Shorts, TikTok)
  • Freelance video editors managing multiple clients
  • Small post teams that need consistent handoff structure

Features

  • Interactive CLI prompts
  • Smart default project name with current date
  • Customizable destination path
  • Organized creator-first directory tree
  • Separate locations for RAW media, external media, and transcoded files
  • Dedicated space for multitrack audio exports from DAWs and frame exports
  • Works great with Bun and npm workflows

Folder structure created

My Video Project - Sun Jun 21 2026/
├─ Assets/
│  ├─ Audio/
│  │  └─ Multitrack/
│  ├─ Images/
│  │  └─ Frames/
│  └─ Video/
│     ├─ External/
│     │  └─ Transcoded/
│     └─ RAW/
│        └─ Transcoded/
└─ Exports/

How creators use it

  1. Run the CLI when a new project starts.
  2. Drop camera originals into Assets/Video/RAW/.
  3. Put stock, downloads, client assets, or screen captures into Assets/Video/External/.
  4. Save proxies/transcodes inside each Transcoded/ folder.
  5. Keep stems and VO in Assets/Audio/Multitrack/.
  6. Store stills and frame grabs in Assets/Images/Frames/.
  7. Deliver final versions from Exports/.

This keeps source media separate from deliverables and makes versioned exports easier to track.

Quick start

With Bun (recommended)

bunx new-video-project

With npx

npx new-video-project

After running, the CLI asks two quick questions:

  • project name (defaults to My Video Project - <today>)
  • where to create it

Local development

Install dependencies:

bun install

Build:

bun run build

Run the built CLI:

bun run start

Scripts

  • bun run build -> builds index.ts into dist/
  • bun run start -> builds, then runs dist/index.js
  • bun run publish -> publishes package to npm

Tech stack

  • Bun
  • TypeScript
  • @clack/prompts
  • boxen
  • picocolors

Roadmap ideas

  • Optional presets (YouTube, client work, documentary, social clips)
  • Auto-create project metadata files
  • Optional proxy/transcode helper setup
  • Editor and DAW preset scaffolds

Support

If this tool saves you time on a real project, you can support it here:

GitHub Sponsors Ko-fi Buy Me A Coffee

Author

Matheson Steplock