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

gettext-simple

v0.4.3

Published

Why overcomplicate translations with libraries like `next-intl` when translating text has been a solved problem since 1995?

Readme

Gettext

Why overcomplicate translations with libraries like next-intl when translating text has been a solved problem since 1995?

When iterating on a project you should not have to worry about

  • giving an ID to a text
  • structuring a json file
  • jumping between translations and components

Exmaple

Requires 0 setup to get started.

import { useGettext, fmt } from "gettext-simple/react"

function Component() {
  const [count, setCount] = useState(0)
  const { gettext: t, ngettext: n } = useGettext()

  return (
    <main>
      <button onClick={() => setCount((c) => c + 1)}>
        {t("Add an apple")}
      </button>
      <p>
        {fmt(n("There is one apple", "Number of apples: {{count}}", count), {
          count: count,
        })}
      </p>
      {fmt(t("Click <link>here</link> for more)"), {
        link: (child) => <a>{child}</a>,
      })}
    </main>
  )
}

Adding translations

  1. To extract translatable text, use xgettext.

    xgettext **/\*.ts **/\*.tsx \
      --from-code=UTF-8 \
      --output=messages.pot \
      --language=JavaScript \
      --keyword=p:1c,2 \
      --keyword=t \
      --keyword=n:1,2
  2. Init .po files

    msginit --locale=yourlocale --input=messages.pot
  3. After filling it in, turn it into a json file.

    ./node_modules/.bin/gettext-simple yourlocale.po yourlocale.json
  4. Wrap your app in a GettextProvider

    import { GettextProvider } from "gettext-simple/react"
    import messages from "./messages.json"
    
    <GettextProvider messages={messages}>
      <App />
    <GettextProvider>

Maintaining translations

  1. Regenerate .pot file with xgettext as seen above

  2. Merge messages

    for po in po/*.po; do
      msgmerge --update --backup=off "$po" po/messages.pot
      # optionally remove obsolete messages
      msgattrib --no-obsolete --output-file="$po" "$po"
    done

Todo

  • [ ] add error logs for missing messages in dev mode when messages object is non empty in Gettext
  • [ ] add support for Astro
  • [ ] add support for Solid
  • [ ] add support for Svelte
  • [ ] add support for Vue