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

localize-js

v1.1.5

Published

client-side translations

Readme

localize.js

Build Status npm version

An easy-to-use client-side javascript plugin for localizing/translating/internationalizing your website. Languages are lazy-loaded so only the required language is retrieved when it's needed. No dependencies required.

Installation

Using npm:

npm install localize-js

Or simply add the script in the dist folder at the bottom of your html page:

<script src="/path/to/localize.min.js"></script>

Basic Usage

If you are using npm to require Localize.js, pass options within the require. See Attribute Options below for possible arguments

var localize = require('localize-js')(options)

In your HTML, add a translate attribute along with an identifying key to all of the elements that need to be translated. Call the localize.translate(language) function to translate the page:

<body>
  <h1 translate="mypage.header"></h1>
  <p translate="mypage.paragraph"></p>
  <script>localize.translate('en')</script>
</body>

Translations should be in JSON format. You can specify the directory to look for translations in the Attribute Options. By default this is /translations/

JSON files should have a basic key-value structure like:

{
  "mypage.header": "Header",
  "mypage.paragraph": "This is a paragraph"
}

The translate function returns a Promise, so you can chain together functions when it is complete:

localize.translate("en")
  .then(function(){
    console.log("Done localizing!");
  });

See the example folder for a demo.

Attribute Options

Pass an optional options object when requiring the localize-js plugin

var localize = require('localize-js')({
  keyword: 't'
  path: '/my/translations/folder/',
  defaultLang: 'en',
  initLoc: false
});

or in your html

<body>
  <script src="/path/to/localize.js" keyword="t" path="/my/translations/folder/" default-lang="en" init-loc="false"></script>
</body>

keyword

This identifies the translate keyword to used in the page. The default is translate. For example:

path

This is the path in which to find the translations. The default is /translations/.

default-lang

The default language that will be displayed when a user reaches the page. By default, localize.js will use the browser language retrieved from window.navigator when default-lang is not specified.

init-loc

Boolean representing whether or not to initialize translation on page load. Defaults to true.

Locales with Country Codes

localize.js supports locales with country codes (eg. en-CA). If a locale with a country code is not found in a JSON translation file, localize.js will look for the language without country code. For example, if en-CA.json could not be found, it will check for en.json before failing.