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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@open-xchange/i18next-po-parser

v1.4.0

Published

Scans source code for i18next translations, and generates the contents for PO/POT files.

Downloads

946

Readme

@open-xchange/i18next-po-parser

A small utility that scans source code for calls of the i18next translation function t() and the react-i18next component <Trans>, extracts all translation keys, and generates the contents for a PO/POT file (GetText translation catalog) containing all extracted strings.

Essentially, this utility glues together the packages i18next-cli (parses source code for t function calls etc.), and gettext-converter (generates the PO file contents from i18next catalog data).

Installation

npm install @open-xchange/i18next-po-parser
# or
pnpm add @open-xchange/i18next-po-parser
# or
yarn add @open-xchange/i18next-po-parser

Usage

API

import { parsePoFile, parseSourceFiles } from '@open-xchange/i18next-po-parser'

// returns a `Record<string, string>` (i18next translation catalog)
const catalog = await parsePoFile('i18n/de-DE.po')

// returns a `Map<string, string>` (namespaces to PO catalog data)
const map = await parseSourceFiles({
  project: 'Example App',
  files: 'src/**/*.{js,ts,jsx,tsx}',
})

CLI

The command line tool generates separate PO files per namespace. The placeholder [NAMESPACE] in the option --output will be replaced with the actual namespaces.

# 'npx' or 'pnpm' or 'yarn'
npx i18next-po-parser --project "Example App" --files "src/**/*.{js,ts,jsx,tsx}" --output dist/[NAMESPACE].pot