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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@freakzlike/i18n-extract

v1.5.0

Published

Minimalistic and low dependency translation key extractor

Downloads

173

Readme

@freakzlike/i18n-extract

Latest Version License

Minimalistic and low dependency translation key extractor.

Searchs for usage of $t and writes keys to JSON files.

Input from source code

$t('some_key')

// with namespace to split into separate files
$t('common:some_key')

// nested key
$t('messages.success')

Output to translation file

{
  "some_key": "__MISSING_TRANSLATION__",
  "messages": {
    "success": "__MISSING_TRANSLATION__"
  }
}

Requirements

  • Node.js >= 18.15.0

Might as well work with lower Node.js versions. Developed and tested on 18.15.0.

Execute

Extracts translations from source files and writes translation files:

i18n-extract ./i18n-extract.config.cjs

Extract translations from source files and checks for untranslated messages. Can be used in CI and does not write the translation files.

i18n-check ./i18n-extract.config.cjs

Config

// i18n-extract.config.cjs
module.exports = {
  input: [
    'src/**/*.vue',
    'src/**/*.ts',
    // Don't extract from tests
    '!**/__tests__/**'
  ],
  // Output path with placeholders
  // Example: locales/de/common.json
  output: 'locales/{{lng}}/{{ns}}.json',
  languages: ['de', 'en-GB'],
  // Optional: Default namespace if none given in translation
  defaultNamespace: 'common',
  // Optional: Namespaces
  namespaces: ['common', 'other'],
  // Optional: Default value for new translations
  defaultValue: '__MISSING_TRANSLATION__',
  // Optional: Regex to extract transations from source code
  // The translation key must be the first match
  parseRegex: /\B\$t\s*\(\s*['"]([\w/: ._-]+)['"]/g,
  // Optional: Parser function, receives file content as string and should return list of found translation keys
  // Type: (filePath: string, content: string) => string[]
  parser: (filePath, content) =>
    [...content.matchAll(/\B\$t\s*\(\s*['"]([\w/: ._-]+)['"]/g)].map((matches) => matches[1]),
  // Optional: Keep missing translations and not delete them
  keepMissing: false,
  // Optional: Suffixes to keep
  // Example: If key `key_1` is used then `key_1_plural` will not be deleted
  // Default: []
  suffixes: ['_plural']
}