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

i18next-seperated-bundle-loader

v1.0.0

Published

i18next loader module for webpack

Downloads

1

Readme

npm Build Status Coverage Status

NPM

i18next loader for webpack

this is a webpack loader that can translate your code and generate bundle per each language

installation:

npm install --save-dev i18next-loader

usage with CRA:

  1. install i18next: npm install --save i18next
  2. call i18next.init({}) in the begining of your webpack.config.js:
const i18next = require('i18next');

i18next.init({
  lng: 'pl',
  fallbackLng: false,
  keySeparator: false,
  nsSeparator: false,
  saveMissing: true,
  resources: {
    'Hello World!': 'Siema Świecie!',
    'Translate me!': 'Przetłumacz mnie',
    'One plus one equals ${ 1 + 1 }': 'Jeden plus jeden jest równe ${ 1 + 1 }',
    'key_0': 'elementów',
    'key_1': 'element',
    'key_2': 'elementy',
    'key_5': 'elementów',
    'key_21': 'elementy'
  }
});
  1. Use loader in your application:
{
    test: /\.(js|jsx)$/,
    loader: 'i18next-loader'
}
  1. Then you can use translate function, e.g:

__('Translate me!')   // 'Przetłumacz mnie'
__(`One plus one equals ${ 1 + 1 }`)  // 'Jeden plus jest jest równe ${ 1 + 1 }'
__('item', {count: 0})  // 'elementów'
__('item', {count: 1})  // 'element'
__('item', {count: 99})  // 'elementów'
  1. inside your react component:

import { useTranslation } from "react-i18next";

function App() {
  const { t: __ } = useTranslation();

  return <h2>{__('Hello World!')}</h2>;
}

export default App;

query params:

  • funcName: change default function name (default is __())
  • quotes: choose how to generates translated strings in code (default is '')

problems:

  • it will not translate keys depending of variables values: it is a loader so the value of the variable is unknown in the process of loading file. (to handle it we need to use i18next directly)