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

babel-plugin-extract-format-message

v6.2.4

Published

Generate a message id from the default message pattern

Downloads

12,462

Readme

babel-plugin-extract-format-message

Extract messages from formatMessage calls

npm Version JS Standard Style MIT License

Installation

$ npm install babel-plugin-extract-format-message

Usage

Via .babelrc (Recommended)

.babelrc

{
  "plugins": [ "extract-format-message", {
    "generateId": "underscored_crc32",
    "outFile": "locales/en.json"
  } ]
}

Via CLI

$ babel --plugins extract-format-message script.js

Via Node API

require("babel-core").transform("code", {
  plugins: [
    [ "extract-format-message", {
      "generateId": "underscored_crc32",
      "outFile": "locales/en-US/messages.yml",
      "locale": "en-US"
    } ]
  ]
})

Options

  • generateId is either a function string -> string, or one of "literal", "normalized", "underscored", "underscored_crc32". Defaults to "underscored_crc32"
  • outFile is a path (relative to cwd) to the output file containing extracted messages. Defaults to stdout.
  • format is a string specifying the target file format. By default the format is inferred from the file extension of outFile.
  • locale is the BCP 47 Language Tag string specifying the language of the default messages. This is only used in the yaml format, to match the Rails conventions. Defaults to "en".

Formats

json

The structure of the file matches the conventions of Chrome's i18n tools. This is also the default format used if an unrecognized format is specified.

Note that format-message apis expecting all of the translations requires a higher level object with locale keys. The value for each locale matches this format.

{
  "hello_67b127a": {
    "message": "Hello!",
    "description": "Greeting shown on the home page."
  }
}

js

Aliases: javascript, commonjs, node

Uses the same structure as json, but uses Node.js's module.exports idiom to export the messages.

module.exports = {
  "hello_67b127a": {
    "message": "Hello!",
    "description": "Greeting shown on the home page."
  }
}

es6

Uses the same structure as json, but uses ES6 module syntax to export the messages.

export default {
  "hello_67b127a": {
    "message": "Hello!",
    "description": "Greeting shown on the home page."
  }
}

yaml

Aliases: yml, rails

Follows the Ruby on Rails i18n conventions for internationalization messages. Descriptions are added as a comment above the messages they describe.

Note that unlike the other formats, yaml requires the locale to be at the top level.

en:
  # Greeting shown on the home page.
  hello_67b127a: Hello!

License

This software is free to use under the MIT license. See the LICENSE-MIT file for license text and copyright information.