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-scanner

v0.2.0

Published

VerbX Localize — AST string extraction for JS/TS/JSX. Shared by the CLI and the GitHub agent.

Downloads

244

Readme

@verbx/localize-scanner

AST-based string extraction for VerbX Localize, shared by the CLI and the GitHub agent.

You do not install this directly@verbx/localize-cli depends on it. It is documented here for people building their own integration.

What it does

Parses JavaScript, TypeScript and JSX/TSX with @babel/parser and extracts the user-visible text: JSX text, translatable JSX attributes, and t(...) / <T> calls. It distinguishes copy from code — identifiers, enum values and numeric literals are skipped, with a reason — so the catalogue does not fill up with things no one should translate.

Each extracted string carries a stable context key derived with the same function the SDK uses, so the same string in two different components is two entries rather than one, and keys match across the client and the server.

import { scanSource, summarize } from "@verbx/localize-scanner";

const result = scanSource(code, { filename: "src/Cart.tsx" });
// result.strings  → [{ source, contextKey, context, file, line, column, kind }, …]
// result.skipped  → what was left out, and why
console.log(summarize([result]));

Pure: source text in, results out. No filesystem, no globbing, no network.

Docs

localize.verbxeco.com

License

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