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

message-loader

v1.0.0

Published

i18n message loader for webpack, based on properties files

Downloads

9

Readme

i18n properties message loader for webpack

Build Status Coverage Status

When import / require i18n.properties, import all other properties files in the same directory, and output as json.

Usage

npm i message-loader -D

Add message-loader into webpack config.

{
  module: {
    rules: [
      {
        test: /i18n[a-zA-Z_]*\.properties$/,
        use: 'message-loader'
      }
    ]
  }
}

src/i18n/i18n.properties

default properties

hello = 你好
invoice.title = 发票抬头
app.name = 测试 App

src/i18n/i18n_en.properties

hello = hello
invoice.title = invoice title

src/i18n/i18n_fr.properties

fr = fr

src/index.js

import messages from './i18n/i18n.properties';

console.log(messages);

// should output following code
/*

{
  default: {
    hello: '你好',
    'invoice.title': '发票抬头',
    'app.name': '测试 App'
  },
  en: {
    hello: 'hello',
    'invoice.title': 'invoice title',
    'app.name': '测试 App'
  },
  fr: {
    hello: '你好',
    'invoice.title': '发票抬头',
    'app.name': '测试 App',
    fr: 'fr'
  }
}
*/

options

Override default options with following loader config.

{
  test: /message(?:_([a-zA-Z_]+))?\.properties$/,
  use: {
    loader: 'message-loader',
    options: {
      filePattern: /message(?:_([a-zA-Z_]+))?\.properties$/,
      locales: ['en']
    }
  }
}

options.filePattern

default to: /i18n(?:_([a-zA-Z_]+))?\.properties$/.

Means will search following files in the same directory, i18n.properties, i18n_en.properties, i18n_zh_CN.properties, and so on.

when use file name to match pattern, the result at index 1 will be the locale.

options.locales

Should be an array with locale string, e.g. ['en', 'zh_CN'].

Means only specific locale messages will be returned, Notice: default message will be return if exist.