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

@semio/utils

v0.2.0

Published

Shared typescript utilities.

Downloads

87

Readme

@semio/utils

Shared TypeScript utilities used across the Semio packages. Provides the animation player, the runtime values store, and a grab-bag of math, color, time, and React helpers. Has no other @semio/* dependencies, so it can be used on its own.

Installation

npm install @semio/utils

Runtime peers you'll likely already have: react, three, zustand.

What's inside

| Area | Exports | Notes | | --- | --- | --- | | Playback | usePlayerStore, Player, and the pure transport functions play / pause / seek / reset | usePlayerStore holds transport state under s.player (stamp, running, duration — all in milliseconds). The pure functions operate on a Player value; seek(player, stamp) is a pure stamp-set. | | Runtime values | useValuesStore, values-store helpers | Single source of truth for the current value of every animatable. Read with the hook; write via useValuesStore.getState().updateValues(map). | | Math / geometry | euler, angles, hexagon, points-to-path, overlapping-segments, closest-frame, progress | Pure functions, no React. | | Color | colors | Parsing, conversion, manipulation. | | React helpers | useDeep, useMediaQuery, context providers | | | Misc | result, json, download, regex, time, lazy, pairwise, namespace, log | |

Everything is re-exported from the package root:

import { usePlayerStore, useValuesStore, seek } from "@semio/utils";

Usage

Playback

import { usePlayerStore } from "@semio/utils";

// Read transport state in a component (state lives under `s.player`)
const stamp = usePlayerStore((s) => s.player.stamp); // milliseconds
const running = usePlayerStore((s) => s.player.running);

// Drive playback via store actions
usePlayerStore.getState().playPlayer();
usePlayerStore.getState().pausePlayer();
usePlayerStore.getState().resetPlayer(2500); // jump to t = 2500ms

The transport is also exposed as pure functions over a Player value, if you want to manage the clock yourself rather than through the store:

import { seek, play, type Player } from "@semio/utils";

let player: Player = play(current);
player = seek(player, 2500); // pure stamp-set, returns a new Player

Runtime values

import { useValuesStore } from "@semio/utils";

// Read in a component
const value = useValuesStore((s) => s.values.get("my.animatable.id"));

// Write imperatively (e.g. from a gizmo drag) — updateValues takes a Map
useValuesStore.getState().updateValues(new Map([["my.animatable.id", nextValue]]));

License

MIT