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

@verbx/localize-client

v0.2.2

Published

VerbX Localize — typed HTTP client for /v1/localize (runtime) and /localize (management).

Readme

@verbx/localize-client

The typed HTTP client for the VerbX Localize backend.

You do not install this directly — the runtime, the CLI and the dashboard depend on it. It is documented here for people building their own integration.

Two surfaces, two credentials

  • Runtime API/v1/localize/*, authenticated with a vx_ API key. Batch translate, bundle fetch, language detect. This key ships inside a client bundle, so it is translate-only.
  • Management API/localize/*, authenticated with the SaaS JWT. Projects, strings, glossary, review, analytics, and the GitHub agent. Sends X-Tenant-Id (read from the token's tid claim when not passed), which the backend requires.
import { RuntimeApiClient, LocalizeManagementClient } from "@verbx/localize-client";

const runtime = new RuntimeApiClient({ apiKey: "vx_…", projectKey: "proj_…", endpoint: "https://…/v1/localize" });
const management = new LocalizeManagementClient({ token: saasJwt, baseUrl: "https://…/localize" });

Handles Idempotency-Key on mutations and selects the right auth header per surface.

Docs

localize.verbxeco.com

License

Proprietary. See LICENSE.md and the VerbX terms of service.