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

multilanguagers

v1.1.8

Published

This package `multilanguagers` it is possible to display the site in different languages.

Downloads

40

Readme

localization

With this package it is possible to display the site in different languages.

The respective lankkey and locale are selected and output using the IntlMessage.

Import

Use the following command to import:

import IntlMessage from 'multilanguagers/index'

Use

Use Import the following command to paste:

return ({IntlMessage({messageId:'template.dont.found', locale:'de'})})

or as jsx element:

return (
    <IntlMessage messageId={'template.dont.found'} locale={'de'}/>
)

So that you can store the languages, you must create the Register folder in the src folder and the file there RegisterLanguage.tsx with the following content:

import de from './de_DE.json'
import en from './en_EN.json'

export const RegisterLanguageDE = {
    ...de
}

export const RegisterLanguageEN = {
    ...en
}


const deLang = {
    messages: {
        ...RegisterLanguageDE
    },
    locale: 'de',
};
const EnLang = {
    messages: {
        ...RegisterLanguageEN
    },
    locale: 'en',
};

export const AppLocale: any = {
    "de": deLang,
    "en": EnLang
};

Now you can use the tabs for DE and EN to map all Lang files here and thus merge all DE and EN files into one.

This gives the IntlMessage immediate access to it and it can be output.

You can also add new ones. As an example adding a Spanish version:

import de from './de_DE.json'
import en from './en_EN.json'
import es from './es_ES.json'

export const RegisterLanguageDE = {
    ...de
}

export const RegisterLanguageEN = {
    ...en
}

export const RegisterLanguageES = {
    ...es
}


const deLang = {
    messages: {
        ...RegisterLanguageDE
    },
    locale: 'de',
};
const EnLang = {
    messages: {
        ...RegisterLanguageEN
    },
    locale: 'en',
};

const EsLang = {
    messages: {
        ...RegisterLanguageES
    },
    locale: 'es',
};

export const AppLocale: any = {
    "de": deLang,
    "en": EnLang,
    "es": EsLang
};

You can also fill this with all existing Spanish Json files using RegisterLanguageES.

Search and Replace

You can store within the Lang Key Param and then easily exchange them. Here is an example:

IntlMessage({
    messageId: 'template.dont.found',
    locale: 'de',
    param: '[test]',
    replacement: 'ausgetauscht',
    preperator: 'replace'
})

You can also have HTML code in your key, for this you have to read the IntlMessage like this:

<p dangerouslySetInnerHTML={{__html: IntlMessage({messageId: 'template.dont.found', locale: 'de'})}}/>

But it is always better not to inject. But to build it into the right tag right away, see example:

<p>
    {IntlMessage({messageId: 'template.dont.found', locale: 'de'})}
</p>

or as jsx:

<p>
    <IntlMessage messageId={'template.dont.found'} locale={'de'}/>
</p>

You can also store [bold] and [/bold] in the LangKey, for example, which will automatically be replaced by <strong> and </strong>

Prop Types

| Prop name | Type | Description | |-------------|---------|-------------------| | messageId | string | Lankey | | locale | string | LangCode de,en | | param | string | Params | | replacement | string | Replacement | | preperator | string | Preperator use | |htmlReplace| boolean | clear HTML Code |