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

@deniscuciuc/webshare

v0.1.0

Published

Unofficial client for the Webshare proxy API: subscription, plans, proxies and capacity

Readme

@deniscuciuc/webshare

An unofficial client for the Webshare API — subscription, plans, proxy list, replacement and capacity.

Errors come back as a Result from neverthrow rather than the tagged unions the other packages in this repository use. That inconsistency is deliberate: the code was written and covered that way, and rewriting 900 working lines for the sake of uniformity would have been a bad trade (ADR-0006). You do not have to adopt neverthrow in your own code — .match() is enough.

pnpm add @deniscuciuc/webshare

Not affiliated with or endorsed by Webshare.

How to use it

import { createWebshareClient } from '@deniscuciuc/webshare'

const webshare = createWebshareClient({ apiKey })
const proxies = await webshare.listProxies()

proxies.match(
  (page) => page.results.forEach(use),
  (error) => log.warn({ error }, 'Webshare is unavailable'),
)

Capacity and pricing live in a separate client, createWebshareCapacityClient: those endpoints have their own response model and their own set of errors.

What is worth knowing

| | | | --- | --- | | Two clients | The main one covers subscription, plans, proxies and replacements. The capacity one covers available resources and price calculation | | Errors | A Result from neverthrow, not exceptions and not the tagged unions used in the other packages | | Schemas | Responses are validated with zod at the boundary; an invalid response is an error, not a partially parsed object | | Authentication | An API key, passed as an argument. The package does not read the environment | | Timestamps | Webshare returns microseconds, not milliseconds. A schema written for the familiar format passes every inline test and fails on the first live response | | WebsharePlanUsage | Traffic usage for a plan. The fields describe a Webshare response, not anyone's application domain |

More about the source in docs/vendors/webshare.md.

Licence

MIT. Part of vendor-clients-ts.