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

@se-studio/media-pipeline

v0.6.5

Published

Normalize designer media into short-lived CMS-ready packs (no Contentful writes)

Readme

@se-studio/media-pipeline

Normalize designer media into CMS-ready files for short-lived packs.

Hard rules

  • Never writes to Contentful (no CMA tokens, no asset create).
  • Host (apps/media-pipeline) stores ready files on Vercel Blob and returns public HTTPS URLs.
  • cms-edit uploads with asset upload --url <readyUrl>.

Package API

import {
  processSourceFiles,
  buildManifest,
  resolveProfileForTenant,
  createJobId,
  CASE_STUDY_V1,
} from '@se-studio/media-pipeline';

const resolved = resolveProfileForTenant('se', 'case-study-v1');
// processSourceFiles([{ sourceName, buffer }], { tenant, jobId, profile, … })
// buildManifest({ job, status, ready, gaps, urls })

Profiles

| Id | Purpose | |----|---------| | case-study-v1 | Images ≤ 3.5MB, long edge ≤ 2400; video H.264 mp4 ≤ 3.5MB, height ≤ 1080, loops strip audio |

encodeHeroLoop (hero mute loops): probe + optional 720/1080 H.264 (no audio). Rejects duration > 30s but still returns probe dimensions. Host stores {slug}-720.mp4 / {slug}-1080.mp4 / {slug}-poster.webp (slug from the source filename).

Tenants (config only — not CMS spaces)

| Id | Prefix default | |----|----------------| | se | se- | | om1 | om1- |

Host app

See apps/media-pipeline — Vercel Blob + Vercel Workflows:

  • POST /api/v1/jobs → 202 + workflow run (google_drive_folder or inline_files)
  • Per-file steps: Drive download → encode → put
  • sleep(expiresAt) then pack delete
  • GET /api/v1/jobs/:id?tenant=

Encode targets

| Limit | Value | |-------|-------| | Default max ready bytes | 3.5MB (under hosted staged 4MB) | | Hard ceiling for cms-edit --url | 10MB (we stay under 9.5MB) | | Video | H.264 + yuv420p + faststart via ffmpeg (ffmpeg-static or system) |

Development

pnpm --filter @se-studio/media-pipeline test
pnpm --filter @se-studio/media-pipeline build