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

@uplift-io/video

v1.1.3

Published

Synchronous video transforms and derived outputs for Uplift upload routes.

Readme

@uplift-io/video

Optional ffmpeg-backed video transforms and derived outputs for Uplift routes.

import { video } from "@uplift-io/uplift";
import { trim, transcode, thumbnail } from "@uplift-io/video";

export const clip = video()
  .transform(trim({ start: "00:00:01", end: "00:00:10" }), transcode({ format: "mp4", codec: "h264" }))
  .outputs(thumbnail("thumb", { at: "25%" }));

Video work runs during the upload request in v1. Production deployments should provide ffmpeg/ffprobe-capable hosts or set UPLIFT_FFMPEG_PATH and UPLIFT_FFPROBE_PATH.

For larger clips, prefer Uplift async transforms so ffmpeg work runs as a background Transform Job instead of blocking the upload request:

export const clip = video()
  .transformAsync(trim({ start: "00:00:01" }), transcode({ format: "mp4" }), { timeout: "10m" })
  .outputs(thumbnail("poster", { at: "25%" }));

The default processor shells out to the host binaries and creates real media artifacts for trim, transcode, compression, resize, crop, watermark, mute, frame-rate changes, thumbnails, posters, storyboards, and extracted audio. Tests or advanced deployments can inject a custom processor with setVideoProcessor() and restore the default with resetVideoProcessor().

Transcode defaults are chosen for the requested container instead of copying streams blindly:

| Container | Default video codec | Default audio codec | | --- | --- | --- | | MP4 | H.264 (libx264) | AAC | | MOV | H.264 (libx264) | AAC | | WebM | VP9 (libvpx-vp9) | Opus (libopus) |

If you pass an explicit codec that is not compatible with the output container, transcode() throws before starting ffmpeg. For example, WebM rejects H.264 video and AAC audio.

Compression keeps the current output container and selects compatible codecs for it. MP4 and MOV outputs use H.264/AAC, WebM outputs use VP9/Opus, and unknown video extensions fail fast instead of producing ffmpeg arguments that cannot be muxed safely.