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

@layera-labs/orbit-video

v1.0.0-beta.4

Published

Headless video timeline model + server-side FFmpeg render pipeline for Orbit

Readme

@layera-labs/orbit-video

The video engine behind Orbit. A timeline document model, the maths for every effect, a DrawOp[] draw list for live preview, and an ffmpeg filtergraph builder that encodes the same project to an MP4.

It is not an editor and not a React package. There are no components here, no canvas, no DOM. It computes what a frame should look like; something else draws it.

npm i @layera-labs/orbit-video@beta

Beta. 1.0.0-beta.3, published under the beta tag. The API moves without notice until 1.0.0. Nothing in this package needs React.

The one idea

Every effect is rendered twice from one model, and the two must agree.

A filter, a transition, a Ken Burns move, a chroma key, a rounded canvas frame — each is defined once, then drawn live in the browser and encoded by ffmpeg on the server. The maths is shared rather than reimplemented, and dual-render.test.ts parses the real filtergraph out of buildFFmpegArgs and asserts it agrees with frameStateAt. A preview that lies about the export is a failing test.

Where the two genuinely cannot agree, the divergence is measured against real ffmpeg and written down. Measured against a decoded MP4: ungraded clips, alpha ramps and geometry agree to ≤2/255; colour grading to ≤6/255, reaching 10 on the vivid preset's saturated colour. It is not byte-identical and this package does not claim it is.

Three entries, and the difference matters

| Entry | Modules | Reaches | |---|---|---| | @layera-labs/orbit-video | 31 | Nothing outside itself. Browser-safe | | @layera-labs/orbit-video/browser | 31 | Identical to the default — the default is export * from './browser' | | @layera-labs/orbit-video/node | 34 | The superset. Adds renderProject, rasterizeSVG, Google font resolution, and with them @resvg/resvg-js, node:child_process, node:fs, node:os, node:path |

@layera-labs/orbit-video/types is the type module on its own, for a consumer who wants VideoProject and nothing else.

The default entry's purity is a promise, not a convention: browser-safety.test.ts walks the import graph of both the default and ./browser and fails if a node: builtin ever reaches either. Import ./node only from Node.

Build a project and render it

import { createProject } from '@layera-labs/orbit-video/browser';
import { renderProject } from '@layera-labs/orbit-video/node';

const project = createProject({
  width: 1080,
  height: 1920,
  tracks: [
    {
      id: 'main',
      kind: 'visual',
      clips: [
        { id: 'c1', type: 'image', src: '/tmp/a.jpg', start: 0, duration: 3 },
        { id: 'c2', type: 'image', src: '/tmp/b.jpg', start: 3, duration: 3,
          transitionIn: { type: 'fade', duration: 0.5 } },
      ],
    },
  ],
});

const result = await renderProject(project, {
  outputPath: '/tmp/out.mp4',
  onFraction: (f) => console.log(`${Math.round(f * 100)}%`),
  thumbnail: { path: '/tmp/out.jpg', atSec: 1 },
});
// → { path, durationSec, bytes, thumbnailPath? }

renderProject shells out to ffmpeg and ffprobe. Any build from 5.1 works; 6.1+ unlocks 8 more transition variants (Push ×4 and Reveal ×4, whose cover* and reveal* xfade tokens do not exist before it). Ask a box what it has with ffmpegXfadeTokens().

Preview a frame without rendering

import { frameStateAt } from '@layera-labs/orbit-video/browser';

const ops = frameStateAt(project, 3.25); // DrawOp[] — what is on screen at t=3.25s

frameStateAt computes everything and draws nothing. That is what lets a canvas 2D compositor, a Skia compositor and the ffmpeg export all share one answer. If you are writing a preview, this is the function you want; the drawing is yours.

What is in the box

Transitions (22 families / 52 variants, of which previewableTransitions() offers the 51 that both renderers can do), filter presets modelled on ffmpeg's YUV planes in BT.601, Ken Burns motion, blur, chroma key, masks, blend modes, per-clip speed, element fade/slide animation, audio fades and volume curves, real sfnt text metrics and wrapping, image and shape overlays, canvas frames, karaoke word timing, and SRT export.

Not built, deliberately: speed ramping (ffmpeg cannot smoothly ramp audio tempo, so there is no faithful preview) and keyframed scale/rotation (ffmpeg cannot animate scale per frame). Segment/parallel rendering is not built either — one call is one encode.

RenderResult carries path, durationSec, bytes and an optional thumbnailPath. It does not carry width, height, fps or encodeMs.

A note on SVG

overlayToSVG and backgroundToSVG build markup by hand, and a VideoProject arrives as untrusted JSON. Strings go through esc, numbers through num, and colours and font families through col/fontFamily — the last of those matters because esc is an XML transform the parser undoes, so an escaped url('/etc/passwd') decodes back into a live reference. rasterizeSVG refuses any SVG containing <image>, <use>, <script> or <foreignObject>. If you extend the builders, never interpolate a raw value into markup.

Links

MIT.