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

localize-cli

v1.2.0

Published

CLI tool for translating strings and generating i18n files using the Google Translate API

Downloads

4

Readme

Localize CLI

CLI tool for translating strings and generating i18n files using the Google Translate API.

Alt text

Installation

npm install --save localize-cli

Configure Google Translate API

To use this tool you'll need a Google Cloud Platform account to access the Google Translate API. It's not entirely painful to set up – I believe in you!

  1. Create a Google Cloud Platform project
  2. Enable billing
  3. Enable the Google Cloud Translation API
  4. Configure Google Cloud authentication on your local machine
    • Set up authentication with a service account

    • Move that json credentials file to somewhere like ~/.google/credentials.json

    • Update ~/.bash_profile with export GOOGLE_APPLICATION_CREDENTIALS=~/.google/credentials.json

    • Reload bash profile with source ~/.bash_profile

    • Copy the project_id for the next step

Configure Localize CLI

Create a config file in your root directory called localize.cli.js with the following:

module.exports = {

  base_locale: 'en',
  
  locales: ['en', 'ja'],

  output: './locales.json',

  google_cloud_project_id: 'MY_GOOGLE_PROJECT_ID'
}

Usage

Typing this command in your terminal...

localize base.hello "Hello world"

... will generate a locales.json file like this:

{
  "en": {
    "base": {
      "hello": "Hello World"
    }
  },
  "ja": {
    "base": {
      "hello": "こんにちは世界"
    }
  }
}

TODO

  • [x] Publish to NPM – npm publish
  • [ ] Command for removing translations by JSON key
  • [ ] Allow config to exist in package.json or as CLI params
  • [ ] Option to break each locale into separate JSON files
  • [ ] Re-listen to Vespertine by Björk