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

@oqf/i18n

v0.1.0

Published

Open Quest Format string extraction and injection for localization, with JSON, CSV, PO and XLIFF tables.

Downloads

117

Readme

@oqf/i18n

String extraction and injection for Open Quest Format. Pure transformations over the model, no I/O and no dependencies beyond @oqf/core and @oqf/dialogue, so it runs in browsers and in Node.

A text field holds either a literal or a key reference such as @harbormasters_ledger.trade.title. Extraction moves literals into a table and leaves key references behind, injection writes them back. Keys come from structure, never from content, so they are stable across runs.

| Field | Key | |-------|-----| | Quest title, summary | <questId>.title, <questId>.summary | | Step title, journal | <questId>.<stepId>.title, <questId>.<stepId>.journal | | Outcome title | <questId>.<stepId>.outcome.title | | Conversation title | <conversationId>.title | | Node text | <conversationId>.<nodeId>.text | | Choice text | <conversationId>.<nodeId>.<choiceIndex>.text |

import { createResolver, extractDocument, injectDocument, toCsv } from '@oqf/i18n'

const { document, table } = extractDocument(doc)
const csv = toCsv(table)
const back = injectDocument(document, table)

const resolve = createResolver({ en, fr }, { locale: 'fr', fallback: 'en' })
resolve(document.quests[0].title)

A field that already holds a key is left alone and is not added to the table. Two different literals under one key throw I18nError. Documents are never mutated, and any subtree with nothing to rewrite is returned by reference.

injectDocument, injectDialogue and injectAll take { missing: 'keep' | 'throw' | 'empty' }, defaulting to keep, which leaves an unknown key reference in place.

Table adapters are symmetric pairs of to<Format> and from<Format>: JSON (a flat pretty map), CSV (key,text, RFC 4180 quoting), PO (the key is msgctxt, the source is msgid, the translation is msgstr) and XLIFF 1.2 (one trans-unit per key, written and parsed by hand). Reading PO or XLIFF takes the translation when it is filled in and the source string otherwise.