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

lingohub-api-simple-client

v1.1.1

Published

Client for the LingoHub REST API to upload and download translations

Downloads

2,869

Readme

Lingohub Client

We use LingoHub for translation management. LingoHub separates keys and translations strictly, therefore we also implement this behaviour in our workflows. The translation format uses the Format.js syntax.

Get current translations

Run

lingohub-client d --account LINGOHUB_ACCOUNT --project LINGOHUB_PROJECT --token LINGOHUB_TOKEN -d DIRECTORY_WITH_LANGUAGE_FILES

Pay attention; this will overwrite all local translation files with the current LingoHub version.

Upload edited translations

When changing translations, the change needs to be propagated back to LingoHub. In LingoHub a translation is added from a base translation file (e.g. en.json). A key will never be deactivated nor deleted, but only added or changed. After changing (adding, updating) the base translation file, run

lingohub-client u --account LINGOHUB_ACCOUNT --project LINGOHUB_PROJECT --token LINGOHUB_TOKEN --fileName BASE_LANGUAGE_FILE -d DIRECTORY_WITH_LANGUAGE_FILES

A typical translation workflow

You build a feature which needs additional translations. Typically you add a key to the base translation (e.g en.json) file and add meaningful content to it. Let's connect this to LingoHub:

  1. Before changing the base translation file: Get current translations (download latest translations from LingoHub)
  2. Check if your key is already there, if not continue to Step 4, else
  3. If you have anything to change, change the content of the key
  4. Add the key and add a content to the base translation file
  5. Upload edited translations
  6. Be happy. Translators will now be able to see your changes and translate whatever you added.