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

i18n-auto-translation

v1.4.1

Published

Auto translate i18n JSON file(s) to desired language(s).

Downloads

3,674

Readme

Description

i18n-auto-translation helps you translate your JSON internationalization files. You need to pick one of the translation API providers that are supported, pass the subscription key, language to which you want to translate, path to the file or directory, and you are good to go.

How It Works?

  • If there is no translation for the file you provided, the complete file will be translated, and the new file will be created with the same structure as the original file, keeping the keys in original language, and translating only values.
  • You can pass a file with the nested JSON objects, and everything will be translated as you expect.
  • The newly created file will be named [to].json. (e.g. sr_latn.json)
  • If the translation for the file already exists, the tool will only translate newly added lines, or delete the one that are no longer in the original file, keeping the structure same as the original file.
  • Don't worry, tool will call an API only for the newly created lines, already translated one will be skipped.
  • Translate APIs are not ideal, and that's why you will need from time to time to override some translations manually, when you manually translate some value, the tool will keep that value, and won't try to translate it again.
  • If you pass a directory, the tool will recursively find all files named [from].json (e.g. en.json), and the translations will be saved in the same directory as the original file(s). All the described above will be still applicable.
  • Words that are wrapped in {{}}, {}, <>, </> won't be translated. e.g. {{skip}} {skip} <strong> </strong> <br />

Installation

You can install package globally on your machine:

$ npm i -g i18n-auto-translation

Or save it as dev dependency in your project:

$ npm i -D i18n-auto-translation

Usage

$ i18n-auto-translation -k SUBSCRIPTION_KEY -d PROJECT_DIR -t DESIRED_LANGUAGE

Options

| Key | Alias | Description | Default | | ----------------------------------------- | ----- | ------------------------------------------------------------------------------------------------------ | --------------- | | --help | / | All available options. | / | | --version | / | Current version. | / | | --apiProvider | -a | API Provider. | google-official | | --key [required] | -k | Subscription key for the API provider. | / | | --region | -r | Key region. Used only by the Official Azure API. | global | | --filePath [filePath or dirPath required] | -p | Path to a single JSON file. | / | | --dirPath [filePath or dirPath required] | -d | Path to a directory in which you will recursively find all JSON files named [from].json (e.g. en.json) | / | | --from | -f | From which language you want to translate. | en | | --to [required] | -t | To which language you want to translate. | / | | --override | -o | Override all created i18n JSON files. | false | | --certificatePath | -c | Path to a custom certificate. | / | | --spaces | -s | Number of spaces to use when generating output JSON files. | 2 |

Demo

https://user-images.githubusercontent.com/49982438/158603886-23c9978b-56e0-4f50-a1ce-afdb03ef1291.mp4

Translate Providers

| Provider | CLI usage | | --------------------------------------------------------------------------------------------------------------------------------- | ---------------------- | | Google Translate Official | google-official | | Azure Translator Official | azure-official | | Azure Translator RapidAPI | azure-rapid | | Deep Translate RapidAPI | deep-rapid | | Lecto Translation RapidAPI | lecto-rapid | | Lingvanex Translate RapidAPI | lingvanex-rapid | | NLP Translation RapidAPI | nlp-rapid | | Deepl | deepl-pro / deepl-free |

Obtaining keys

  • Google
    • Goto https://console.cloud.google.com/ and create a new project.
    • In the search bar find “Cloud Translation API” and enable it.
    • Click on credentials -> Create credentials -> API key.
    • Copy the key and use it.
  • Azure
    • Follow the instructions here.
  • RapidAPI
    • For all RapidAPI providers, create an account here.
    • Go to desired API and switch to the pricing section. There you will find instructions on how to subscribe to the API.
    • Now you can use your key provided from RapidAPI.

Adding Provider

You don't like supported API providers? You can easily add yours. Go to src/translate/providers, create class for your provider, extend 'Translate' class, and implement 'callTranslateAPI' method. You can check in other providers for examples on how to implement this method. After you added your provider, you just need to register it in 'translate-supplier.ts' and in 'cli.ts' and you are good to go.

Credits

This software uses the following open source packages:

License