Pkg
Stats

npm package discovery and stats viewer.

Discover Tips

General search
[free text search, go nuts!]
Package details
pkg:[package-name]
User packages
@[username]

Sponsor

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.

Twitter
@PkgStats
GitHub
pkgstats
Twitter
@ryanhefner
GitHub
ryanhefner
Site
ryanhefner.com

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 🙏

Framework
react / react-dom
Server
next / express / next-routes
Data Store
redux / react-redux / next-redux-wrapper / redux-thunk / redux-logger
Caching
lru-cache
CSS / Styling
next-page-transitions / styled-components
Typeface
@ibm/plex
Avatars
gravatar
Data Viz
chart.js / react-sparklines
Date formatting
dayjs
Infinite scrolling
react-scroll-trigger
Markdown rendering
react-markdown
Repository url parsing
hosted-git-info
User data
npm-user
Compiling
babel-plugin-module-resolver / babel-plugin-styled-components
Types
prop-types
Odds & Ends
es6-promise / isomorphic-fetch

© 2026 – Pkg Stats / Ryan Hefner

i18n-page-texts

v1.0.3

Published

4 years ago

Generate or feed missed translated properties of each json file for each locale you provided. Besides, it will generate an interface for Typescript.

Downloads

8

0High
0Medium
0Low

i18n interface translate

Goal

As the conept depicted in this scratch,

[ Test ]

,as a developer, I hope that:

Once I add some new sentences into my App, I hope that I can embed those new sentences for all the other languages by google translate Api just by one command such as npm run i18n.
If there are some properties such as address that I don't want to be translated, I can easily achieve this goal by declaring it in the config file.
In ionic or Angular, I can use the intellisence to speed up my coding for these sentences.
If I want to embed the sentences for a new language, I just need to add a new subfolder named as its isoCode shown in node_modules/google-translate-api/languages.js and run the command npm run i18n.

Well, it can be.

Usage

i18n-page-texts --init

will generate a config file.

i18n-page-texts

or

i18n-page-texts --config [SOME FILE].json

will generate files IPageTexts.ts, pageTexts.js and a pageTexts.json for each sub-folder in i18n folder. These files' name can be redefined in the [SOME FILE].json.

i18n-page-texts --help

will show the help information.