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

@treatwell/wti

v2.1.2

Published

A WebTranslateIt command-line tool in Node.js

Downloads

131

Readme

A WebTranslateIt command-line tool in Node.js by

npm GitHub Workflow Status Commitizen friendly code style: prettier semantic-release

screenshot

Usage

Installation

$ yarn add @treatwell/wti

Configuration

Basically, wti is to be run on a project root directory, and looks for a wti-config.json file containing your project's information.

The command wti init lets you create this file.

$ wti init
What is your project's api key?: <your private key>
Initializing...... [SUCCESS] Project is initialized

You can find the API token in your project settings.

Note that if your config is in a different directory then you can pass this with --configPath to any command that needs it:

wti push --configFile ./config/wti-config.json

Usage

Execute wti help to see the usage:

USAGE
  $ wti [COMMAND]

COMMANDS
  add        create and push a new master language file
  addLocale  add a new locale to the project
  help       display help for wti
  init       configure the project to sync with
  pull       pull target language file(s)
  push       push master language file
  rm         delete a master language file from a project

See `wti help <command>` for more information on a specific command.

Sample commands

| Command | Action | | ---------------------------------- | ------------------------------------- | | wti add <path/to/master/file.json> | Upload a new master language file | | wti rm <path/to/master/file.json> | Delete a master language file | | wti push | Update a master language file | | wti pull | Download target language files | | wti addLocale fr | Add a new locale to the project | | wti rmLocale fr | Remove a locale from the project | | wti status | View project statistics |

Overview

i18next example

1. Prerequisite

  • Create a project on WebTranslateIt with a source language (such as english)
  • Bootstrap a React app

2. Install and configure i18next

$ yarn add i18next react-i18next
$ yarn add -D i18next-parser

// Extract locales
$ i18next --config i18next-parser.config.js

3. Install and configure WTI client

$ yarn add -D wti
$ wti init
$ wti add locale fr
$ ... add other languages
$ wti add locales/en/translation.json
$ wti push

4. Translate keys on WebTranslateIt, and then pull translations

$ wti pull

5. Add or remove translation keys

$ i18next --config i18next-parser.config.js
$ wti push