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

i18next2ts

v1.0.0

Published

# Purpose * Are you tired of cpy-paste of translation keys? * Are you in love with TS? * You do hate a typos when providing a translation key? * Want to avoid providing a key that does not exist?

Downloads

8

Readme

Installation

Purpose

  • Are you tired of cpy-paste of translation keys?
  • Are you in love with TS?
  • You do hate a typos when providing a translation key?
  • Want to avoid providing a key that does not exist?

Perfect! I answered yes to all the above and made a simple tool for us:

instead of i18n.t('auth.password')

lets write i18n.t(typedJson.auth.password) !

Are you fancy testing it out?

Quickstart

  1. grab this json and save it to some file:
{
  "screenA": {
    "title": "Screen Title",
    "description": "Description",
    "value": "value does not matter, can be empty!"
  },
  "auth": {
    "password": "Password is required!",
    "strangeKey": "does not matter"
  },
  "deepKeys": {
    "lostInSpace": {
      "andTime": {
        "farAwayInAnother": "galaxy"
      }
    }
  }
}
  1. run npm i i18next2ts --save-dev in your project

  2. run i18next2ts translation.json LanguageKeys.ts

  3. create any .ts file to test it

import LocalizationKeys from 'LocalizationKeys'
const json = require('./translation.json');
const typedJson = json as LocalizationKeys;
  1. now try to type typedJson. - tadam! hints are working like a charm.

  2. you can now change your i18n.t('auth.passowrd)intoi18n.t(typedJson.auth.password)` instead

Dependencies:

  • no dependencies for module itself!
  • CLI uses 'fs' native module

restrictions

  • keys should be .notation acceptable (no - for example)
  • types other than string or {} are not supported - they are not present in the common translation files for i18next

//TODO GIF //TODO tests //TODO travis //TODO coveralls