npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details


  • User packages



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.


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 🙏

© 2019 – Ryan Hefner




backend layer for i18next to chain backends







Travis Coveralls npm version David

This is a i18next backend to chain multiple other backends and caches. So you can define an additional caching backend or fallback backends.

Getting started

Source can be loaded via npm or downloaded from this repo.

# npm package
$ npm install i18next-chained-backend

Wiring up:

import i18next from 'i18next';
import Backend from 'i18next-chained-backend';

  • As with all modules you can either pass the constructor function (class) to the i18next.use or a concrete instance.
  • If you don't use a module loader it will be added to window.i18nextChainedBackend

Backend Options

  // array of existing i18next backends from
  backends: [],

  // array of options in order of backends above
  backendOptions: []

Options can be passed in:

preferred - by setting options.backend in i18next.init:

import i18next from 'i18next';
import Backend from 'i18next-chained-backend';

    backend: options

on construction:

  import Backend from 'i18next-chained-backend';
  const Backend = new Backend(null, options);

via calling init:

  import Backend from 'i18next-chained-backend';
  const Backend = new Backend();
  Backend.init(null, options);

more complete sample

import i18next from 'i18next';
import Backend from 'i18next-chained-backend';
import Locize from 'i18next-locize-backend'; // load from service
import XHR from 'i18next-xhr-backend'; // have a own xhr fallback

    backend: {
      backends: [
        Locize,  // primary
        XHR      // fallback
      backendOptions: [{
        projectId: 'myLocizeProjectId'
      }, {
        loadPath: '/locales/{{lng}}/{{ns}}.json' // xhr load path for my own fallback

Gold Sponsors