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

@czap/scene

v0.10.0

Published

Author video timelines for LiteShip: a typed scene and track model built on the entity-component substrate in `@czap/core`.

Readme

@czap/scene

Turns a typed timeline declaration — video, audio, transition, and effect tracks — into a compiled scene that a deterministic runtime ticks frame by frame.

Install this directly when you author video timelines to render through @czap/remotion or the czap CLI. If you're starting a new project, start with the liteship package instead — it brings the whole stack.

Install

pnpm add @czap/scene [email protected]

effect v4 is a required peer and only ships as a beta — install the pin above (any >=4.0.0-beta.0 satisfies it).

30 seconds

import { Track, Beat, compileScene, type SceneContract } from '@czap/scene';

const scene: SceneContract = {
  name: 'intro',
  duration: 4000, // milliseconds
  fps: 30,
  bpm: 120,
  tracks: [
    Track.video('hero', { from: Beat(0), to: Beat(8), source: { id: 'hero' } }),
    Track.audio('bed', { from: Beat(0), to: Beat(8), source: 'intro-bed' }),
  ],
  invariants: [], // checks compileScene runs against the resolved contract
  budgets: { p95FrameMs: 16 },
  site: ['node'],
};

console.log(compileScene(scene).trackSpawns.length);

Logs 2 — one spawn per track. compileScene resolves each Beat(n) mark against the scene's bpm and fps (here Beat(8) becomes frame 120), runs every declared invariant, and reports all violations in one error. Scene.runtime(compiled) then builds a live, tickable handle.

Where it sits

A layered authoring package: it sits on the ECS (entity-component-system) world from @czap/core, and shares its timeline contracts with the rest of the stack through @czap/_spine types. Beat detection is not here — it lives in @czap/assets; bring its sample-space markers into scene.beats with resolveBeatProjectionToSceneBeats. The Node-only dev server ships at the @czap/scene/dev subpath so browser and Worker bundles never touch it. See the package surfaces map for the full layout.

If it does nothing

Beat-synced effect tracks (syncTo: syncTo.beat(...)) tick but never pulse when scene.beats is empty — the sync system queries the world for beat entities and finds none, with no warning. The fix: detect beats with @czap/assets, convert them with resolveBeatProjectionToSceneBeats, and set the result as scene.beats before compileScene.

Authored-motion adapter

MotionSampleSystem(plan, frameIndex, totalFrames) is the scene's adapter for an authored motion program (@czap/core's sampleProgram, #130): per frame it samples the ONE shared kernel and writes each typed leaf as a motion:<cssVar> component (via the same world.setComponent seam TransitionSystem uses). sampleSceneMotion(plan, t) is the pure projection.

This is additive to TransitionSystem, not a merge. TransitionSystem's _blend is a video-crossfade mix factor between two Between entities — a different concept from an authored motion program. Both coexist on one world; TransitionSystem is untouched. A differential oracle proves the scene leg renders identically to browser CSS, the browser runtime floor, stage, remotion, and worker (ADR-0040).

Docs


Part of LiteShip — powered by the CZAP engine (Content-Zoned Adaptive Projection), distributed as @czap/* packages.