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

i18n-components

v1.0.7

Published

I want to try make an easy to use i18n components for react, using tagged template literals.

Downloads

10

Readme

i18n-components

A very small library to help with translations in React
Please report any problems.

Tutorial

Installation

> npm i -s i18n-components

Templates

A list of translations must be created, this uses the template as the key.

const templates = {
	'Hello, World!': {
		'en-ZA': 'Howzit!',
	},
	'Hello, {0}. The number is {1}.': { 
		'en-ZA': 'The number is {1}, hey {0}.',
	},
}

Creating a context

Your main component needs to be wrapped. If culture is left off, it will try and get the culture from the browser.

	import { Translations } from 'i18n-components';

	function App()
	{
		return (
			<Translations templates={templates} culture="en-ZA" >
				<MyOtherComponents />
			</Translations>
		);
	}

Using a translation

	import { i18n } from 'i18n-components';

	function SayHi()
	{
		return (<p>{i18n`Hello, World!`}</p>);
	}

	function WithVariables()
	{
		const name = 'Jack';
		const [number, setNumber] = useState(0);
		return (
			<div>
				<p>{i18n`Hello, ${name}. The number is ${number}.`}</p>
				<button type="button" onClick={() => setNumber(number + 1)}>+</button>
			</div>
		);
	}

Should render as

Language fallback

	const templates = {
	'Hello, World!': {
		'pt': 'Olá Mundo!',
		'pt-BR': 'e aí',		
	},
}

Language and culture

<Translations templates={templates} culture="pt-BR" >
	<p>{i18n`Hello, World!`}</p>
</Translations>

will return

Just language

<Translations templates={templates} culture="pt-PT" >
	<p>{i18n`Hello, World!`}</p>
</Translations>

will fall back to the language only translation

Fall back to template

<Translations templates={templates} culture="es-ES" >
	<p>{i18n`Hello, World!`}</p>
</Translations>

will fall back to the template because no language can be found.

Using useI18n Hook

If you want to use a translation in a property you will need to use the hook.

<input value={useI18n`Hello, World!`} readOnly />

or

function HelloBox()
{
	const hello = useI18n`Hello, World!`;
	return (<input value={hello} readOnly />);
}