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 🙏

© 2025 – Pkg Stats / Ryan Hefner

type-locales

v3.2.0

Published

A simple tool for typing your locales and a util for easy manage of i18n with typescript

Downloads

53

Readme

Type Locales

A simple tool for typing your locales and a util for easy manage of i18n with typescript

If you have the following structure

.
├── locales
│   ├── en.json
│   └── es.json
└── src
│   └── ...
└── package.json

Just run the tool

npx type-locales ./locales

and it will generate a locales keys that you can use on your i18n with intelisence autocomplete importing them from type-locales module like

import { localeKeys } from 'type-locales'

An example using i18n vanilla

// src/index.ts
import { localeKeys } from 'type-locales'
import i18n from 'i18n'

i18n.configure({...})

console.log(
    i18n.__mf({
        locale: 'en',
        phrase: localeKeys.say.hello
    }, {
        to: 'Jonh Doe'
    })
)

An example using type-locales utils

// src/index.ts
import { Translator, localeKeys } from 'type-locales'
import i18n from 'i18n'

i18n.configure({...})

const translate = Translator('en')
console.log(
    translate(keys.say.hello, {
        to: 'Jonh Doe'
    })
)

Why?

i18n is a wonderful tool, but it has a problem, the phrases to translate are handled in external and static files, which makes it easy to do many things except the DX when trying to remember the keys and their parameters to replace. This tool checks all your json files and generates a typed object which you can import to use the autocomplete so you don't have to remember and check the translation files.

The cli

The biggest magic of this tool is in its cli, which is where you can generate the code needed to have the wonderful type autocompletion.

You can use npx type-locals --help to see the help

Usage: type-locales [path] [options]

Arguments:
  path                   path to translate

Options:
  -V, --version          output the version number
  -w --watch             watch for changes in the input directory (default: false)
  -q, --quiet            quiet mode (default: false)
  -h, --help             display help for command

Even without using the keys you can have autocomplete if you use the module utility after running cli

// src/index.ts
import Translator from 'type-locales'
import i18n from 'i18n'

i18n.configure({...})

const translate = Translator('en')
console.log( // has autocomplete without keys
    translate('say.hello', {
        to: 'Jonh Doe'
    })
)