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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@blaiv/json-google-translate

v1.0.3

Published

Quick tool for lazy translators

Readme

Json Google Translate

Quick tool for lazy translators using i18n like json translations files.

Overview

Module based on https://github.com/Localize/node-google-translate

Intended to user when you are developing an app using i18n, where you have a folder containing all translations json files, each named as the language short code. It detects the translations missing on each language and requests it to google translate. It also detects if a key has no content and also fills it with the automatic translation. So when you are developing and continously adding new literals to a base language you run a script to automatically handle translations.

Installation

npm install @blaiv/json-google-translate --save-dev or yarn add @blaiv/json-google-translate

Usage

Enter your api key, point to the translations folder relative to the folder you execute the script and specify a base language. It will automatically translate all missing keys. If you want to add a new language, just create a short-code language named json file and run the script.

Example

├── index.js
├── translations                    # translations folder
│   ├── en.json                     # base language containing all language literals
│   ├── es.json                     # another language containing some filled language literals or empty literals.
│   └── fr.json                     # it can be an empty json file

index.js:

const jsonGoogleTranslate = require('@blaiv/json-google-translate');

const config = {
  API_KEY: "YOUR_GOOGLE_API_KEY",
  TRANSLATIONS_FOLDER: "./translations",
  BASE_LANGUAGE: "en"
}
jsonGoogleTranslate(config);

translations/en.json

{
  "hello": "hello"
}

translations/es.json

{
  "hello": ""
}

translations/fr.json

{
  
}

Run node index.js