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

vitexec

v0.1.12

Published

Run a snippet inside a live Vite app and get browser logs back.

Readme

Give AI agents a fast way to test your apps from the inside.

Overview

vitexec is for checks that are too slow, visual, or stateful for normal agent browser control.

Use it to let an agent play through a scene, steer a camera, test game-like controls, inspect runtime state, and collect evidence without adding debug UI or temporary app code.

Install

npx skills add drawcall-ai/vitexec

Then ask your agent to use it:

Use $vitexec to move through the scene and inspect the camera position.

Problem

AI agents are slow when every action is a separate browser step.

Click, wait, inspect, press a key, wait again is expensive and often useless for interactive apps where movement, camera, physics, timing, and input all happen together.

The missing piece is a programmable control loop inside the running app.

Solution

vitexec lets the agent run a script inside the page instead of controlling the browser one action at a time.

The snippet can import real Vite modules, drive real input, wait for frames, branch on state changes, and run full multi-step flows before logging the result.

Each run gets an isolated Vite server, its own Playwright browser, streamed logs, and optional screenshots, videos, traces, profiles, HARs, or heap snapshots.

Better Than Alternatives

  • Instead of adding test functions to the app: keep checks outside production code
  • Instead of judging screenshots only: log exact runtime state
  • Instead of one slow browser action at a time: run a state-aware script in-page
  • Instead of hand-writing Playwright-style setup: give the agent one CLI tool
  • Instead of sharing one dev server: run isolated checks in parallel
  • Instead of fighting HMR during checks: use a Vite server with HMR disabled

Example

vitexec --gpu --path /scene '
  import { app } from "/src/app.ts";

  window.dispatchEvent(new KeyboardEvent("keydown", { code: "KeyW" }));
  await new Promise((resolve) => setTimeout(resolve, 1000));
  window.dispatchEvent(new KeyboardEvent("keyup", { code: "KeyW" }));

  const { object, camera } = app.getSnapshot();
  console.log("moved", JSON.stringify({ object, camera }));
'
logs:
[log] moved {"object":{"x":0,"y":0,"z":-4.2},"camera":{"yaw":0,"pitch":0}}

No debug panel. No test-only app code. No guessing from pixels alone.

Use It For

  • Camera controls, pointer lock, drag interactions, and gamepad input
  • Three.js scenes, physics simulations, canvas, WebGL, and WebXR
  • Zustand, Redux, TanStack Query, or custom runtime stores
  • Screenshots, videos, CPU profiles, HARs, traces, and heap snapshots
  • Turning vague browser failures into readable logs

Commands

vitexec --gpu --path /scene 'console.log(location.pathname)'
vitexec --gpu --path /scene ./vitexec/check-scene.ts

| Option | Use | |---|---| | --path /scene | Open a specific route | | --config ./vite.config.ts | Use a specific Vite config | | --gpu | Use generic GPU/WebGPU-friendly Chromium flags | | --browser-ws-endpoint wss://... | Connect to a Playwright browser WebSocket endpoint | | --browser-expose-network <loopback> | Expose local network routes to a remote browser | | --screenshot ./page.png | Capture a full-page screenshot | | --record ./run.webm | Record browser video | | --cpu-profile ./cpu.cpuprofile | Capture a Chrome/V8 CPU profile | | --network-trace ./network.har | Capture network requests as HAR | | --performance-trace ./performance.trace.json | Capture a Chrome performance trace | | --heap-snapshot ./heap.json | Capture a jq-friendly decoded heap snapshot | | --timeout 30 | Set the maximum wait time |

Environment Variables

CLI flags take precedence over environment variables.

| Environment variable | Equivalent option | |---|---| | VITEXEC_BROWSER_WS_ENDPOINT | --browser-ws-endpoint | | VITEXEC_BROWSER_EXPOSE_NETWORK | --browser-expose-network | | VITEXEC_CONFIG | --config | | VITEXEC_PATH | --path | | VITEXEC_GPU | --gpu | | VITEXEC_TIMEOUT | --timeout | | VITEXEC_SCREENSHOT | --screenshot | | VITEXEC_RECORD | --record | | VITEXEC_CPU_PROFILE | --cpu-profile | | VITEXEC_NETWORK_TRACE | --network-trace | | VITEXEC_PERFORMANCE_TRACE | --performance-trace | | VITEXEC_HEAP_SNAPSHOT | --heap-snapshot |

When --browser-ws-endpoint is set, vitexec only sends browser-generic GPU/WebGPU launch flags. Start the remote Playwright server with any host-specific GPU policy that matches its platform.