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

@dvhb/react-intl-messages

v2.4.6

Published

Library for parsing source files and extract react-intl messages

Downloads

39

Readme

react-intl-messages

Library for parsing source files and extract react-intl messages. Extracted messages saves to json files. Underhood it uses babe-plugin-react-intl

oclif Version Downloads/week License

Features

  • synchronize translations with translation service (lokalise.co and Locize for now)
  • custom babel config, appropriate for projects on react-native and typescript
  • prettify extracted json files
  • store parameters in config

Usage

$ npm install -g @dvhb/react-intl-messages
$ messages COMMAND
running command...
$ messages (-v|--version|version)
@dvhb/react-intl-messages/2.4.6 darwin-arm64 node-v16.13.1
$ messages --help [COMMAND]
USAGE
  $ messages COMMAND
...

Commands

messages clean

Clean lokalise for unused translation keys

USAGE
  $ messages clean

OPTIONS
  -d, --messagesDir=messagesDir  (required) [default: src/messages] Directory for extracted messages
  -h, --help                     show CLI help
  --namespace=namespace          Provider`s namespace. Required for Locize
  --projectId=projectId          Provider`s project id
  --provider=lokalise|locize     (required) Translation service provider
  --token=token                  Provider`s token
  --uploadTranslations           Upload existing translations to provider. Useful for provider migration.
  --version=version              Translations version, for example "production". Required for Locize

See code: src/commands/clean.ts

messages extract

Extract translations from source files to json

USAGE
  $ messages extract

OPTIONS
  -d, --messagesDir=messagesDir  (required) [default: src/messages] Directory for extracted messages
  -h, --help                     show CLI help
  -i, --ignore=ignore            Regex mask for ignored files
  -l, --langs=langs              (required) Comma separated languages
  -p, --pattern=pattern          (required) Regex mask for files

EXAMPLE
  $ messages extract --langs=en,fr,de,ru --pattern="src/**/*.{ts,tsx}"

See code: src/commands/extract.ts

messages help [COMMAND]

display help for messages

USAGE
  $ messages help [COMMAND]

ARGUMENTS
  COMMAND  command to show help for

OPTIONS
  --all  see all commands in CLI

See code: @oclif/plugin-help

messages sync

Synchronise extracted files with Lokalise.co

USAGE
  $ messages sync

OPTIONS
  -d, --messagesDir=messagesDir  (required) [default: src/messages] Directory for extracted messages
  -h, --help                     show CLI help
  -l, --langs=langs              (required) Comma separated languages
  --namespace=namespace          Provider`s namespace. Required for Locize
  --projectId=projectId          Provider`s project id
  --provider=lokalise|locize     (required) Translation service provider
  --token=token                  Provider`s token
  --uploadTranslations           Upload existing translations to provider. Useful for provider migration.
  --version=version              Translations version, for example "production". Required for Locize

EXAMPLE
  $ messages extract --langs=en,fr,de,ru --pattern="src/**/*.{ts,tsx}"

See code: src/commands/sync.ts

Config

  • messages property in a package.json file.
  • .messages file with JSON or YAML syntax.
  • .messages.json file.
  • .messages.yaml or .messages.yml file.
  • .messages.js or messages.config.js JS file exporting the object.

package.json example:

{
  "messages": {
    "langs": "en,fr,de,ru",
    "pattern": "src/**/*.js",
    "messagesDir": "src/messages"
  }
}

Integration

A brief instruction how to integrate react-intl in your project. For more details please check the react-intl documentation

  1. Install react-intl and @dvhb/react-intl-messages

    npm install --save-dev react-intl @dvhb/react-intl-messages
  2. Add config for @dvhb/react-intl-messages as described in Config section.

    After that you can generate messages files like that:

    npx messages extract
  3. Add polyfills for Intl.NumberFormat and Intl.DateTimeFormat if necessary (for IE11 and react-native) like described in the instruction.

  4. Wrap the app with IntlProvider. Import translations from extracted files. Then reduce translations and pass them to the provider:

    import messagesEn from '../messages/en.json'
    
    const reduceMessages = messages => Object.assign({}, ...messages.map(msg => ({ [msg.id]: msg })));
    
    const locale = 'en';
    
    const messages = {
      en: reduceMessages(messagesEn),
    }
    
    <IntlProvider messages={messages[locale]} locale={locale}>
      <App />
    </IntlProvider>;
  5. After that you can use react-intl components in your project. Like that:

    <FormattedMessage
      id="app.greeting"
      description="Greeting to welcome the user to the app"
      defaultMessage="Hello, <b>Eric</b> {icon}"
      values={{
        b: msg => <b>{msg}</b>,
        icon: <svg />,
      }}
    />
  6. Now if you extract messages again, in _default.json file should appear new item.

    [
      {
        "id": "app.greeting",
        "defaultMessage": "Greeting to welcome the user to the app",
        "message": "",
        "files": ["src/HelloWorld.js"]
      }
    ]