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

linguify

v1.4.1

Published

Translation manager

Downloads

933

Readme

linguify

Linguify translation files manager

Getting started

Installation

Via npm

npm install linguify --save-dev

Via pnpm

pnpm add -D linguify

Via yarn

yarn add -D linguify

Usage

  1. Initiate Linguify with the init command
linguify init
  • This will create linguify.config.json file at the root of your project.
  1. Modify the following values inside linguify.config.json:
  • localesPath: Path to application locales folder.

  • locales: Supported locales by your applications.

    Note: It is better to use ISO-639 language codes.

  • defaultLocale: default locale to your application.

  • useSingleFile: determines to use one translation file for each locale or not.

  1. Start linguify.
linguify

or

linguify start
  • Linguify server port can be changed using -p or --port option following the desired port
linguify -p 3000
  • Note: Updating linguify.config.json while Linguify runs requires restarting it before affecting it.

Import & Export translations

Linguify can import from or export to Excel translations file (xlsx).

Import translations

linguify import
  • Note: the file's first row must contain locales names, and the first column must be named key. It is advised to first use export to get a translations xlsx file.

Export translations

linguify export

Both commands have an option to pass the exact path of the translations file --path <PATH>, if path not passed it will try to import from or export to translations.xlsx from localesPath

How it works?

Linguify first validated the user config, then scans the localesPath for namespaces, read this article from i18next documentation if not sure how it works.

It uses defaultLocale as the base of translations and namespaces, and copies missing translations from defaultLocale namespaces to others. then you can modify them from the ui.

the sync operation happenes everytime Linguify starts, to sync translations manually you can use sync command.

linguify sync

Please open an issue if any bugs arise. and any working pull request is welcome.

Happy Internationalization!