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/rolldown-plugin-i18next-gettext

v1.2.1

Published

Rolldown integration of i18next using gettext PO files

Downloads

823

Readme

@open-xchange/rolldown-plugin-i18next-gettext

A rolldown plugin that allows building libraries or applications using i18next in source code with gettext's .po and .pot files under the hood.

This plugin has the following responsibilities:

  • All .po files imported in source code will be converted to i18next translation catalogs.
  • The source code will be scanned for translation strings (t function calls), and .pot files containing all strings will be generated into the output directory. Supports i18next namespaces (one .pot file per namespace).

Installation

npm install -D @open-xchange/rolldown-plugin-i18next-gettext
# or
pnpm add -D @open-xchange/rolldown-plugin-i18next-gettext
# or
yarn add -D @open-xchange/rolldown-plugin-i18next-gettext

Configuration

Add the plugin to your rolldown configuration (or compatible configurations like Vite or tsdown):

// rolldown.config.ts
import { defineConfig } from 'rolldown'
import i18nextPlugin from '@open-xchange/rolldown-plugin-i18next-gettext'

export default defineConfig(() => {
  plugins: [
    i18nextPlugin({
      srcFiles: 'src/**/*.{js,jsx,ts,tsx}',
      potFile: '[NAMESPACE].pot',
      projectName: 'My Project',
    }),
  ],
})

Options

| Name | Type | Default | Description | | - | - | - | - | | poFiles | string\|string[] | **/*.po | Glob pattern(s) for all PO files to be converted when imported in source code. | | srcFiles | string\|string[] | src/**/*.{js,jsx,ts,tsx} | Glob pattern(s) for all source files to be scanned for UI strings for the POT file generator. | | potFile | string | [NAMESPACE].pot | Path to and filename of the generated POT files, relative to the build output directory. Must contain the placeholder [NAMESPACE] if the project contains translation strings in different i18next namespaces. | | projectName | string | required | The project name to be inserted into the POT file under the key 'Project-Id-Version'. May contain the placeholder [NAMESPACE] |

Usage

Register TypeScript type definitions for the PO file imports:

// tsconfig.json
{
  "types": [
    "@open-xchange/rolldown-plugin-i18next-gettext/client"
  ],
}

Load translation catalogs in source code on demand via i18next backend plugin:

import i18next from 'i18next'
import resourcesToBackend from 'i18next-resources-to-backend'

i18next.use(resourcesToBackend(async (lang: string, namespace: string) => {
  // build appropriate path to the PO files
  return await import(`../i18n/${namespace}/${lang}.po`)
}))