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

unified-translations

v1.1.1

Published

Unify translations in one single file for maintenance and build to separated files.

Downloads

1

Readme

Unified Translations

Unify translations in one single file for maintenance and build to separated files.

Keep all translated sentences of your project in one single JSON file and organized by scope:

{
  "home": {
    "title": {
      "pt-br": "Olá, Mundo!",
      "en": "Hello World!"
    }
  }
}

And ask to unified-translations separate in differents files for your i18n configuration.

Example of the final files:

// pt-br.json
{
  "home": {
    "title": "Olá, Mundo!"
  }
}
// en.json
{
  "home": {
    "title": "Hello World!"
  }
}

Install

npm install unified-translations --save-dev

Arguments

| Argument | Description | | - | - | | --translations-file | JSON file of all translated sentences. | | --languages | List of all languages key and output file separated by coma. Eg. "pt-br=./pt-br.json" wich pt-br is the language key, the same used in translations file to identify the language and the ./pt-br.json is the desired final output file of that language. | --mode | Mode of the script. Default is build, but it also accepts reverse mode. |

Build

To create the separated files, use the following command:

unified-translations
  --translations-file ./translations.json
  --languages pt-br=./pt-br.json,en=./en.json

Reverse Mode

To create the "translations file" from the already created output files:

unified-translations
  --translations-file ./translations.json
  --languages pt-br=./pt-br.json,en=./en.json
  --mode reverse