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

vela-agent

v0.2.0

Published

Vela dev probe — a one-line require('vela-agent').attach() in an Electron main process that exposes IPC introspection + main-process eval to the Vela test framework (dev-only).

Readme

vela-agent

Vela Agent is a lightweight dev probe for Electron main processes.

A single attach() call in your main process registers IPC introspection and a main-process eval channel, giving the vela-mcp server the ability to call vela_ipc_list, vela_ipc_invoke, and vela_main_eval tools during development and testing.

Integration

Add one line at the top of your main.js / main.ts, before any ipcMain.handle calls:

if (process.env.NODE_ENV !== 'production') require('vela-agent').attach();

That is the entire integration. The probe is:

  • Dev-only — the NODE_ENV guard means it is completely inert in production builds.
  • Environment/token-gated — the agent only activates when the Vela environment token is present, so it will not interfere with regular npm start runs unless a Vela test session is active.
  • Zero runtime dependencies — nothing extra is bundled into your production app.

What it enables

| vela-mcp tool | Requires vela-agent | |---------------|-------------------| | vela_ipc_list | Yes — lists every registered ipcMain.handle channel | | vela_ipc_invoke | Yes — calls a channel as if from a renderer | | vela_main_eval | Yes — evaluates arbitrary JS in the main process |

All other Vela tools (CDP-based renderer eval, screenshot, debugger, specs, capture) work without vela-agent.

More

See vela-mcp and the repo for the full playbook.