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

@velocut/core-ts

v0.0.2

Published

The TypeScript **reference engine** — a faithful mirror of the canonical Rust engine (`crates/velocut-core`).

Readme

@velocut/core-ts

The TypeScript reference engine — a faithful mirror of the canonical Rust engine (crates/velocut-core).

  • Role: applies @velocut/protocol commands to the document model and evaluates a time into a FrameGraph. It is the frontend's fallback when the WASM bundle is absent, and is directly runnable on Node.
  • Contract: its behavior is pinned to the Rust engine by the shared golden vectors in protocol/vectors/*.jsontest/vectors.test.ts runs them here, crates/velocut-core/tests/vectors.rs runs the same set there. A behavioral change must land as a new vector that both sides pass.
  • Depends on: @velocut/protocol.

Usage

The npm package ships ESM JavaScript and TypeScript 5.9+ declarations. JavaScript runs directly on Node: node demo.mjs; no TypeScript loader is needed.

import { TsEngine } from '@velocut/core-ts';

const engine = new TsEngine('demo', 1920, 1080, 30, 1);

engine.apply({ type: 'addAsset', kind: 'video', src: 'clip.mp4', name: 'Clip', durationUs: 5_000_000, id: 'asset-1' });
engine.apply({ type: 'addTrack', kind: 'video' });
const trackId = engine.document().tracks[0].id;
engine.apply({ type: 'addClip', trackId, assetId: 'asset-1', startUs: 0, durationUs: 2_000_000 });

const fg = engine.evaluate(1_000_000); // FrameGraph at t = 1s
console.log(fg.layers.length, fg.layers[0].sourceTimeUs); // 1 1000000

See the root README and PROTOCOL.md for the full command set.