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

i18n-service

v0.0.4

Published

A simple node i18n service

Readme

#i18n-service Build Status Code Climate Dependency Status Coverage Status

A simple i18n service.

Usage

First you need create a json file in locales folder with the locale name, for example, en.json. The file content needs to follow the flow structure.

{
  "en" : {
    "hello" : "hello",
    "something": "Some text",
    "views" : {
      "login" : {
        "title": "Login page",
        "email": "E-mail",
        ...
      }
    }
    ...
  }
}

Your new locale will be available on http://localhost:3000/en

You can have how many locales you want. For example:

  • http://localhost:3000/en
  • http://localhost:3000/es
  • http://localhost:3000/pt
  • http://localhost:3000/pt-br

You can set the locales folder by environment variable, setting LOCALES_FOLDER=/your/locales/folder/

Translating

You can get the literals by three ways.

Getting all locale literals

To get all locale literals you just call the url http://localhost:3000/{locale}/translate

Getting a list of literals

To get a list of literals you need pass the required list by query string, for example: http://localhost:3000/en?l=hello,something

Getting a part of literals

You can get a part of your literal callin the service passing the part by query string, for example: http://localhost:3000/en?l=views.login

The result will be:

{
  "views" : {
    "login" : {
      "title": "Login page",
      "email": "E-mail",
      ...
    }
  }
}