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

lokalise-to-default-messages

v3.0.9

Published

Utility to update defaultMessages in source code with values from translation json file

Downloads

193

Readme

Release

Lokalise to defaultMessages

Utility to update defaultMessages in source code with values from translation json file. Can also check for duplicate keys and create a diff of keys from 2 different translations file.

Index

Installation

# Using npm, installing to local project
npm i --save lokalise-to-default-messages

# Using npm, installing globally for global cli usage
npm i -g lokalise-to-default-messages

# Using yarn
yarn add lokalise-to-default-messages

# Using pnpm
pnpm install lokalise-to-default-messages

Prerequisites

the translation files must consist of just key, value pairs:

{
  "example_translation_key": "Example",
  "exmaple_translation_key_two": "Exmaple 2"
}

the source code defaultMessages should have this structure:

const t = defineMessages({
  exampleTitle: {
    id: 'example_title',
    defaultMessage: 'Example title',
  },
  exampleTitleTwo: { id: 'example_title_two', defaultMessage: 'Example 2' },
});

IMPORTANT: lokalise-to-default-messages v2 is ESM only.

Basic usage

//Load the library and specify options
import ltdm from 'lokalise-to-default-messages';

OR

//Load the library and specify options
import { toDefaultMessages } from 'lokalise-to-default-messages';

Replace values (Not yet supported)

pass the following options to replace values:

ltdm.toDefaultMessages({
  checkDuplicates: false,
  saveLog: false,
  filesPath: '/src/**/*.{ts,tsx,js,jsx}',
  translationsPath: 'src/translations/en.json',
  oldTranslationPath: undefined,
});

The default options are filled in the example.

CLI usage

ltdm
  [--duplicate-keys] | [-dk]
  [--save-log] | [-sl]
  [--files-path=src/**/*.{ts,tsx,js,jsx}] | [-fp]
  [--translation-file=src/translations/en.json] | [-tf]
  [--old-translation-file=src/translations/old-en.json] | [-otf]

You can pass the argument --duplicate-keys or -dk if you want to check for duplicate keys. If this argument is passed the script will only look for duplicate keys and will dump errors to the terminal. if --save-log or -sl is present the will also be saved to lokalise_log.md

You can pass the argument --file-paths or -fp (default: -fp=src/**/*.{ts,tsx,js,jsx}). This path determines what files to check for defaultMessages of react-intl.

You can pass the argument --translation-file or -tf (default: -tf=src/translations/en.json). This will determine the path to the translations file that should be used to sync the defaultMessages in the js/ts files.

You can pass the argument --save-log or -sl. This will save a log file under lokalise_log.md

You can pass the argument --old-translation-file or -otf. If this argument is passed only the changed keys or values will be checked. This argument has no default value.

Version information

From version 3.0.0 onwards, lokalise to default messages requires Node 18 or higher.

From version 2.0.0 onwards, lokalise to default messages requires Node 13 or higher and is an ESM only package.

See the Changelog for more information.

License

(MIT License)

Copyright 2022, Yannick Maes, License