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

i18next-mf2

v0.1.1

Published

i18nFormat plugin to use mf2 format with i18next

Downloads

6

Readme

Introduction

npm version

This changes i18n format from i18next json to message format 2. See mf2 workgroup

You will need to polyfill Intl.MessageFormatusing following polyfill

Advice

When using this module, only the mf2 message format is respected, this means the i18next format interpolation will not work. So for example instead of Hi {{name}}! it is {Hi {$name}!}

Getting started

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

# npm package
$ npm install i18next-mf2
# peer dependencies
$ npm install intl-messageformat

Wiring up:

import i18next from 'i18next'
import mf2 from 'i18next-mf2'

i18next.use(mf2).init(i18nextOptions)
  • 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.i18nextMf2

Backend Options

{
  // per default mf2 functions are parsed once and cached for subsequent calls
  memoize: true,

  // memoize if not having a lookup and just using the key fallback as value
  memoizeFallback: false,

  // which events should clear the cache, can be set to false or string of events separated by " "
  bindI18n: '',

  // which events on resourceSource should clear the cache, can be set to false or string of events separated by " "
  bindI18nStore: '',

  // Will be run when parser throws an error. Can return any string, which can be used as a fallback, in case of broken translation.
  // If omitted, the default swallows the error and returns the unsubstituted string (res)
  parseErrorHandler: (err, key, res, options) => {},

  // Transform the language code prior to mf2 locale parsing, useful for supporting psuedo-locales like en-ZZ
  // If omitted, the default leaves the language code as is
  parseLngForMf2: (lng) => lng,
}

Options can be passed in by setting options.i18nFormat in i18next.init:

import i18next from 'i18next'
import mf2 from 'i18next-mf2'

i18next.use(mf2).init({
  i18nFormat: options
})

more complete sample

import i18next from 'i18next'
import mf2 from 'i18next-mf2'

i18next.use(mf2).init({
  lng: 'en',
  resources: {
    en: {
      translation: {
        key: '{Today is {$today :datetime dateStyle=medium}}'
      }
    }
  }
})

i18next.t('key', { today: new Date('2022-02-02') }) // -> 'Today is Feb 2, 2022'

hints

Using i18next-mf2 - non of the i18next specific stuff will be available. You will have to rely on what intl-messageformat provides by calling the t function with needed options.

All extra features build around i18next plurals, interpolation, context do not get applied to messageformat based keys.