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

@smoove/transitions

v0.3.6

Published

Scene transitions for smoove: TransitionSeries with 18 presentations and 2 timings.

Readme

@smoove/transitions

Scene transitions for smoove. Blend one scene into the next with cross-fades, slides, wipes, and WebGL shader effects.

A transition overlaps the end of one scene with the start of the next while a presentation mixes them. You build them with TransitionSeries, which plays scenes in order and overlaps each pair where they meet; comp.add(series) expands the whole thing into one Sequence per scene.

Install

pnpm add konva @smoove/core @smoove/transitions

konva and @smoove/core are peer dependencies.

Quick example

import { Composition } from "@smoove/core";
import { fade, linearTiming, TransitionSeries } from "@smoove/transitions";

const comp = new Composition({ id: "intro", fps: 60, durationInFrames: 200, width: 1280, height: 720 });

const series = new TransitionSeries({ composition: comp });
series.scene({ durationInFrames: 80 }, (seq) => seq.add(sceneA));
series.transition({ presentation: fade(), timing: linearTiming({ durationInFrames: 20 }) });
series.scene({ durationInFrames: 80 }, (seq) => seq.add(sceneB));

comp.add(series);

Presentations

Geometric presentations run on Konva transforms, so they work everywhere the player does and render headlessly with no extra setup: fade, slide, wipe, clockWipe, iris, flip, none.

Shader presentations run on WebGL2 fragment shaders in the browser and fall back to fade() without it: dissolve, crosswarp, crossZoom, and more. To render them headlessly, import @smoove/renderer/gl before building the composition.

Two timings drive any presentation: linearTiming and springTiming.

Docs

Full documentation, including the complete presentation catalog, lives at smoove.dev.

License

MIT