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

@verset/probe-cli

v0.0.128

Published

Verset local probe CLI

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

verset_pmverset_pm

Keywords

Readme

Verset Probe CLI

@verset/probe-cli starts a local Verset probe for authenticated remote tool sessions.

npx @verset/probe-cli --help

By default it connects to the production API at wss://api.verset.io/branch. Use --url (or VERSET_API_URL) only to target a development or test endpoint.

To pair a computer from the Verset setup guide, run its copied one-time command:

npx @verset/probe-cli --pairing-code A7C2F9D4

The default command saves the probe session and stays online after pairing. Keep its terminal running; press Ctrl+C to stop. Running again without a code reuses the saved session. --run is still accepted for compatibility, but is no longer needed.

To configure without starting the Probe:

npx @verset/probe-cli config --pairing-code A7C2F9D4

config saves the probe session and exits. It can run while another Probe instance is online; it does not stop or restart that instance. Restart an existing instance to use the new configuration.

An explicit --pairing-code is redeemed exactly once, even when a session is already saved. A failed or expired code returns an error instead of requesting another code; create a replacement at https://uni.verset.io/pairing.

The CLI bundles its application JavaScript. During installation, npm acquires the exact node-pty, node-datachannel, and fs-ext native runtimes for the host. fs-ext provides filesystem locks and requires Python and a C/C++ build toolchain (Linux build tools or macOS Command Line Tools). loader.js imports the bundle first, injects the terminal and WebRTC runtimes through the compatibility setters, then starts the CLI.

A platform is supported only after a clean npm install, CLI startup, terminal spawn, and WebRTC initialization have passed on its Node/OS/architecture combination.