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

@effect-motion/cli

v0.7.0

Published

Command line for effect-motion: preview scenes with hot reload (studio) and render videos from motion.config.ts (render). Scaffold new projects with `bun create effect-motion`

Readme

@effect-motion/cli

Command line for effect-motion: preview scenes in the browser and render videos — all driven by one motion.config.ts.

bun create effect-motion      # scaffold a project (npm/pnpm/yarn create work too)
motion studio                  # preview scenes with hot reload
motion render                  # render every target to MP4
motion frames <scene> --sheet  # sample frames headlessly: PNG stills, a contact sheet or JSON

Scaffolding lives in the create-effect-motion package — this CLI is installed as a devDependency of the projects it creates.

motion.config.ts

import { defineConfig } from "@effect-motion/cli";

export default defineConfig({
	targets: [
		{
			name: "hello-world",                 // unique; doubles as the output basename
			scene: "./src/scenes/hello-world.ts", // module exporting `scene`
			settings: { width: 1920, height: 1080, frameRate: 60, dpr: 1 },
			output: "./output",                  // a DIRECTORY — file name is derived
			// format: "mp4"                     // default (v1: mp4 only)
			// frames: 600                       // frame cap; required for infinite scenes
		},
	],
});

The output path is always <output>/<name>.<format> — never specified by hand. settings is the runner's settings subset plus dpr (supersampling: output pixels = scene dimensions × dpr, authored coordinates unchanged).

studio

motion studio serves the @effect-motion/react Player over your scenes with hot reload (edits full-reload; playback restarts from frame 0). The picker lists every config target plus any unregistered src/scenes/*.ts — preview never requires registration. Registered scenes preview with their target settings, so the preview aspect matches the export. --port/--host pass through to Vite; the app is generated into .motion/studio/ (gitignored by the scaffold).

Note: the studio previews through the SVG DOM renderer while render rasterizes through ThorVG — output is normally identical, but font fallback details can differ. The known upgrade path is a ThorVG-WASM preview sink.

render

motion render                          # all targets from the nearest motion.config.ts
motion render hello-world              # just this target
motion render --config ../m.config.ts  # explicit config (tsc -p style)
motion render ./src/scenes/foo.ts      # configless: one scene file, default settings
motion render --fps 30 --dpr 2 --out-dir ./out   # flags beat config beat defaults

Flags: --width --height --fps --dpr --seed --max-frames --frames --out-dir --format --config. Targets render sequentially; a failing target doesn't stop the rest (non-zero exit + per-target summary at the end). Errors print a single message naming the offender — add --verbose for the full cause chain.

Encoding uses the ffmpeg build bundled via ffmpeg-static (H.264/yuv420p MP4, no system ffmpeg needed). That binary is GPL-licensed; it is invoked over a process boundary and this package remains MIT.

frames

motion frames                              # list scene keys from ./studio.ts
motion frames intro --at 0,1s,50%,end      # PNG stills in .motion/frames/intro/
motion frames intro --count 9 --sheet      # one contact sheet, prints tile → frame/time
motion frames intro --at end --json -      # frame state as JSON on stdout (no GPU)

Samples a scene registered in studio.ts without a browser or video. Flags: --at, --count (default 6), --sheet, --json <path|->, --out, --dpr, --studio.