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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@vizij/utils

v0.0.3

Published

Shared typescript utilities.

Downloads

15

Readme

@vizij/utils

Shared TypeScript utilities and value helpers for the Vizij ecosystem.

This package gathers type definitions, value helpers, and namespacing utilities that keep Vizij packages consistent. Use it to describe animated values, manage namespaced ids, and share primitive types between the renderer, rigging, and React bindings.


Table of Contents

  1. Overview
  2. Installation
  3. Usage
  4. API Highlights
  5. Development & Testing
  6. Publishing
  7. Related Packages

Overview

  • Strongly typed representations of animated values (AnimatableNumber, AnimatableColor, etc.).
  • Helpers for composing namespaced lookup keys (getLookup, getNamespace, getId).
  • Shared types referenced throughout Vizij packages, ensuring every layer agrees on value shapes.

Installation

# pnpm
pnpm add @vizij/utils

# npm
npm install @vizij/utils

# yarn
yarn add @vizij/utils

No peer dependencies are required. The package exports plain TypeScript utilities.


Usage

import { AnimatableNumber, getLookup, getNamespace } from "@vizij/utils";

const jawOpen: AnimatableNumber = {
  id: "jaw/open",
  type: "number",
  default: 0,
  constraints: { min: 0, max: 1 },
};

const lookup = getLookup("actorA", jawOpen.id); // "actorA.jaw/open"
const namespace = getNamespace(lookup); // "actorA"

Use these primitives when defining rig channels, orchestrator inputs, or animation metadata so everything aligns with the same schema.


API Highlights

  • animated-values – Full suite of Animatable* interfaces plus shared RawValue types and publishing metadata.
  • namespacegetLookup, getNamespace, getId utilities for composing/storing namespaced ids.

The package re-exports everything from src/index.ts, so importing from "@vizij/utils" is sufficient.


Development & Testing

pnpm --filter "@vizij/utils" build
pnpm --filter "@vizij/utils" test
pnpm --filter "@vizij/utils" typecheck

tsup bundles both ESM and CJS outputs and emits .d.ts. Vitest currently includes smoke tests; add coverage close to new helpers.


Publishing

Releases flow through .github/workflows/publish-npm.yml.

  1. Record a changeset and apply the version bump:
    pnpm changeset
    pnpm version:packages
  2. Validate locally:
    pnpm install
    pnpm --filter "@vizij/utils" build
    pnpm --filter "@vizij/utils" test
    pnpm --filter "@vizij/utils" typecheck
    pnpm --filter "@vizij/utils" exec npm pack --dry-run
  3. Push a tag with the npm-utils-vX.Y.Z pattern (for example, npm-utils-v0.3.0). The workflow publishes and records provenance automatically.

Related Packages

Have ideas for additional shared helpers? Open a PR and document the changes here to keep the ecosystem aligned. 🧰