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 🙏

© 2024 – Pkg Stats / Ryan Hefner

preact-jsx-i18n

v1.0.0

Published

Localization for Preact using JSX components

Downloads

4

Readme

preact-jsx-i18n 🌎 npm travis FOSSA Status

Localization for Preact using JSX components

This library makes it possible to use JSX components as localization inputs. This may seem messy, but is actually very useful in practice. For simple JSON texts with variables that render to strings, preact-localization or preact-i18n are still options.

This tool is particularly interesting when used in conjunction with string-to-jsx-loader. The two tools combined provide a good compromise between simple translation files and flexibility.

Install

$ npm install -S preact-jsx-i18n

Getting Started

  1. Create a dictionary. Typically JSON files, we'll call ours fr.js:
module.exports = {
	news: {
		title: <b>Nouvelles du Monde</b>,
		totalStories: {
			none: [<i>Aucun</i>, ' article'],
			one: 'Un article',
			many: ({ count }) => [count, 'articles'],
		},
	},
}
  1. Expose the dictionary to your whole app via <IntlProvider>:
import { IntlProvider } from 'preact-jsx-i18n'
import dictionary from './fr'

render(
	<IntlProvider dictionary={dictionary}>
		<App />
	</IntlProvider>
)
  1. Use <Text /> to translate string literals:
import { Text } from 'preact-jsx-i18n'

// Assume the "stories" prop is a list of news stories.
const App = ({ stories = [] }) => (
	<div class="app">
		<h1>
			{/* Default fallback text example: */}
			<Text id="news.title">World News</Text>
		</h1>
		<footer>
			{/* Pluralization example: */}
			<Text
				id="news.totalStories"
				plural={stories.length}
				count={stories.length}
			/>
		</footer>
	</div>
)

That's it!

JSX

As seen in the examples, the dictionary can either:

  • Be a single JSX component
  • Be a single string
  • Be an array of JSX components and strings

If the text requires a variable, a function needs to be returned.

Fallback Text

Rendering our example app with an empty dictionary (or without the Provider) will attempt to use any text contained within <Text>..</Text> as fallback text.

In our example, this would mean rendering without a dictionary for news.title would produce <h1>World News</h1>.

If we provide a dictionary that has a title key inside a news object, that value will be rendered instead.

Pluralization and Templating

In our example, <footer> is using <Text> as a convenient way to do pluralization and templating. In our dictionary, news.totalStories is an Object with pluralization keys. The values in that object will be selected based on an integer plural prop passed to <Text>.

Any dictionary value (including pluralization values) can contain arbitrary JSX, or a function with variables that returns JSX. These placeholders get replaced with matched keys in an object passed as the fields prop. In our example, the "many" plural form is such a template - it will render "5 articles" when count={5}.

The available forms for specifying pluralization values are as follows:

  • "key": { "none": "no apples", "one": "apple", "many": "apples" }

Taking <Text id="news.totalStories" ..> from our example:

  • <.. plural={0}> renders Aucun article (no articles)
  • <.. plural={1}> renders Un article (one article)
  • <.. plural={2} count={2}> renders 2 articles
  • <.. plural={3} count={3}> renders 3 articles

License

FOSSA Status