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

@studio-vaai/js-debugger

v0.1.3

Published

Dev-only debugger for the studio vaai SDK — client error injection, machine state inspection, API call log

Readme

@studio-vaai/js-debugger

Development-time debugger for the studio vaai virtual try-on SDK.

It adds an on-screen panel that lets you inspect the SDK's state, watch the API call log, and inject errors and body-validation failures — so you can exercise error and edge-case paths without a real backend failure.

Intended for development only. Do not ship it to production.

Install

npm install --save-dev @studio-vaai/js-debugger

Usage

Call setupStudioVaaiDebugger() once, early in your app's startup:

import { setupStudioVaaiDebugger } from "@studio-vaai/js-debugger";

if (import.meta.env.DEV) {
  setupStudioVaaiDebugger();
}

This mounts the <studio-vaai-debugger> panel and wraps every studio vaai client so the debugger can observe and intercept calls. It returns an uninstall function for cleanup.

Error injection

Drive failure states from code or from the panel:

import { injectError, clearError, injectBodyValidationFailure } from "@studio-vaai/js-debugger";

injectError(/* method + error kind */); // next matching call fails
clearError(/* method */); // back to normal

getDebugState() / subscribeDebugState() expose the current injections and the API call log; ALL_METHOD_IDS, STANDARD_ERROR_KINDS, and BODY_VALIDATION_CODES enumerate the valid targets.

License

MIT