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-locales-loader

v0.0.2

Published

A `webpack` loader that splits your `locales.json` file into locale-specific files (eg. `en.json`, `zh.json`) for better locale-specific translations lazy loading support.

Downloads

4

Readme

i18n-locales-loader

A webpack loader that splits your locales.json file into locale-specific files (eg. en.json, zh.json) for better locale-specific translations lazy loading support.

npm version

What it Does

  1. Splits a locales.json up into separate files for each locale.

    • locales.json
    == Before ==
    // locales.json
    {
      "en": { "common": { "hello": "Hello" } },
      "zh": { "common": { "hello": "你好" } }
    }
    
    == After ==
    // locales/en.json
    { "en": { "common": { "hello": "Hello" } } }
    
    // locales/zh.json
    { "zh": { "common": { "hello": "你好" } } }
    • Webpack Build Output
    == Before ==
     - build
       - static
         - js
           - main.a543vfds.chunk.js
    
    == After ==
     - build
       - static
         - js
           - main.a543vfds.chunk.js
         - locales
           - src
             - MyComponent
               - en.a433v.json (en locale-specific translations)
               - zh.kfd83.json (zh locale-specific translations)
  2. Modifies locales.json imported object to return URL paths for each locale.

    • MyComponent.js
     // MyComponent.js
     import locales from './locales.json'
    
     == Before ==
     // locales object
     {
       en: { common: { hello: "Hello" } },
       zh: { common: { hello: "你好" } },
     }
    
     // locale usage
     console.log(locales.en.common.hello) // prints "Hello"
    
     == After ==
     // locales object
     {
       en: "/static/locales/src/MyComponent/en.a433v.json",
       zh: "/static/locales/src/MyComponent/zh.kfd83.json",
     }
    
     // locale usage
     fetch(locales.en)
       .then(resp => resp.json())
       .then(content => console.log(content.en.common.hello)) // prints "Hello"

Folder Structure:

- <project root>
  - src
    - MyComponent
      - MyComponent.js
      - locales.json
  • MyComponent.js React component requries i18n translations
  • locales.json contains Component-specific translations

In Summary

Before:

  • Loads locales.json as Object containing translations
  • Always loads translations for all locales via JS code
  • Translations are bundled with JS code

After:

  • Loads locales.json as Object with URL mappings to locale-specific translations (eg. en.json, zh.json)
  • Option to load translations for specific locales via XHR
  • Translations are bundled separately from JS code as static JSON assets

Installation

  1. Add i18n-locales-loader dependency

    yarn add --dev i18n-locales-loader
    or
    npm install --save-dev i18n-locales-loader
  2. Use i18n-locales-loader in webpack.config.js

    // webpack.config.js
    
    module.exports = {
      module: {
        rules: [
          // other rules...
          {
            test: /locales\.json$/,
            type: "javascript/auto",
            loader: require.resolve("i18n-locales-loader"),
            options: {
              // for more details: see options documentation
              esModule: true,
              buildLocalesPath: ["static", "locales"],
            },
          },
          // other rules...
        ],
      },
    };
    
    // note: need to define 'type' to override webpack v4 default JSON-loading behavior

Loader options

  • options.esModule
    • Optional, boolean, default: true
    • Defines module output format
    • When true, Emit output as ES Module (ie. export default)
    • When false, Emit output as CommonJS Module (ie. module.exports)
  • options.buildLocalesPath
    • Optional, string[], default: ["static", "locales"]
    • Defines build directory path to emit locales files to
    • Uses path.join() to generate directory path
    • eg. In default setup, ["static", "locales"] -> /static/locales

Motivation

  1. How to load locales information?
  • ❌ Via component JS code (ie. larger component code > larger initial bundle size > more JS code to parse > slower page load)
  • ✅ Via XHR instead (to take advantage of lazy loading and HTTP caching)
  1. How to load locale-specific information? (eg. en, zh)
  • ❌ Load all locales (bad, because a site will only use a single locale (or two at best, for fallback cases))
  • ✅ Load only specific locales that are required (less overall data to transfer)