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

react-intl-rns

v0.1.6

Published

React Intl namespaced keys with fallback from specific to general

Downloads

27

Readme

react-intl-rns

React Intl namespaced keys with fallback from specific to general

Overview

When using namespaced keys for translations it would be nice to have a fallback when the exact key does not exists but a more generic one.

As seen in the following example it is possible to have specific keys for some component besides a general version for the key.

Example:

const messages = {
  "name.space.cancel": "Stop this",
  "name.cancel": "Cancel this"
  "cancel": "Cancel"
}

The nice thing with react-intl-rns is the build in fallback which means that if you request a specific key but it is not present in the messages object the nearest found parent is used instead. Requesting the key name.space.cancel will find cancel and return it as a translation.

const messages = {
  "cancel": "Cancel"
}

Usage

import { RNSMessage, rnsShorts } from 'react-intl-rns'
const { rnsM, rnsMS } = rnsShorts('very.long.name.space')

It exists two different find-versions when reducing the namespace: from left and from right where from left (REDUCE_LTR) is the default. If you want to find the key by reducing the namespace from right (REDUCE_RTL) you have to use const { rnsM, rnsMS } = rnsShorts('very.long.name.space', 'REDUCE_RTL')

<RNSMessage
  id="very.long.name.space.key"
  defaultMessage=""
  description=""
/>

{ rnsM('key') } or { rnsM`key` }

When using injectIntl and just translated string should be used

const { intl } = this.props

and then { rnsMS('key')(intl) } or { rnsMS`key`(intl) }

Inspiration

Thanks for inspiration and code bits from https://github.com/wrwrwr/react-intl-ns