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

vitetranslate

v2.0.0

Published

The vitetranslate command, installed once: runs the @sepoina/vitetranslate CLI of whatever project you are in, at that project's own version.

Readme

vitetranslate

The vitetranslate command, installed once for every project on your machine.

npm i -g vitetranslate
cd my-app
vitetranslate --status

It is a launcher and nothing more. It finds @sepoina/vitetranslate in the project you are in (./node_modules, then every folder above, the way Node does) and runs that copy's command with your options.

So the version that runs is always the project's own, newer or older than this launcher. On purpose: the command and the Vite plugin write the same translation tables, and two versions writing the same files is a debugging session nobody asked for. It also means you never update this package to get a new release of the library: you update the library in the project, as usual.

When there's nothing to launch

It tells you what to type:

| Situation | Suggestion | | :- | :- | | No package.json here or above | run it from your project's root, or create a Vite app | | In package.json, not installed | npm install | | Not a dependency at all | npm i -D @sepoina/vitetranslate | | Yarn Plug'n'Play | yarn vtranslate-cli: there is no node_modules for a global command to look into |

The package manager comes from your lockfile: pnpm, Yarn and Bun get their own commands.

Options of its own

  • --version: this launcher's version, plus which copy it would run and where that copy lives.
  • --help: the project's own help. This launcher's shows up only when there is no copy to ask.

Everything else goes straight to the project's command: see the CLI reference.

No global install?

Not required. Inside a project, npx vtranslate-cli runs the same command, and in package.json scripts the bare name is enough. npx vitetranslate works too: npx fetches this launcher for the occasion.

Works with projects on @sepoina/vitetranslate 2.0 and later.