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

@woofcli/woof

v0.1.0-beta.3

Published

`woof` is a simple translation code generator.

Downloads

3

Readme

Woof

woof is a simple translation code generator.

How it works

woof takes .toml files as input and generates typescript files with functions than you can call to get your translation strings.

All string interpolation is typesafe and the resulting code is tree-shakable, so you'll only ship the translations you're actually using. Lazy-loading can be taken care of by your bundler, in case you have a lot of translations.

Usage

Here's what the translation files look like:

title = "My Website"
description = "This is a description"

[about]
title = "About"
description = "More details about this website"

[about.more]
copyright = "Copyright {year:number} by {author}"

With the files locales/en.toml and locales/de.toml, running woof -o messages ./locales will generate message files that you can use like this:

import { m } from './messages'

console.log(m.about.title()) // "About"
console.log(m.about.more.copyright({ year: 2022, author: 'me' })) // "Copyright 2022 by me"

You can also directory import messages from a sub-directory:

import * as m from './messages/about/more'

console.log(m.copyright({ year: 2022, author: 'me' })) // "Copyright 2022 by me"

Setting the Locale

Instead of having a global locale variable, you define a getter that will be used by translations. By default, this is set to a function that returns the default locale.

This allows you to have a global variable, use AsyncLocalStorage, or any other mechanism you'd like:

import { setLocaleFn } from "./messages"

// Get it from local storage
setLocaleFn(() => localStorage.getItem("locale") || "en")

// Use a global variable
let locale = "en"
setLocaleFn(() => locale)

// Use async local storage in node
const localeStorage = new AsyncLocalStorage()
setLocaleFn(() => localeStorage.getStore() ?? "en")